• Slide
    ConvertU2 Technologies are the developers of the only 'Silver Bullet' technology for migrating Microsoft Access data and/or applications to Microsoft SQL 2008/2012
  • Slide
  • Slide
  • Slide
  • Slide
1 2 3 4 5

Empirical Case Studies – Using 2SQL Detective

Some Technical Issues

There is a high degree of correlation between the amount of data in the Access database Tables and the degree of complexity of the software required to manage it. The more complex databases will require a server-side solution i.e. driven from SQL Server, while for the more simple databases a client-side approach i.e. driven from Access might be more appropriate. But the choice is not black and white, and subjective judgements will have to be made.

The following three Case Studies depict standard 2SQL Detective screen shots which serve to very clearly illustrate just how challenging conversion of Access to SQL Server can be, even with medium-complex conversions. The real problem in a manual conversion program is, of course, to not just fix the issues, but to find them in the first place.

Empirical case studies (all single databases)

  1. Our approach to estimating manual hours is quite conservative in the examples. The formula is Conversion Issue multiplied by a Rating factor for degree of manual completion difficulty to derive Conversion Units, then multiplied by a default value of 10 minutes per Conversion Unit. For example, converting Jet syntax is estimated to each take 20 minutes to convert i.e. Issues multiplied by rating of 2, multiplied by 10 minutes. Users can enter their own Minutes factors to suit their own circumstances when using the 2SQL Detective to estimate manual hours.

Complex database conversion key statistics

  1. 50+ Tables, 600+ SQL Statements, 7,000+ Conversion Issues.

  2. 1,700+ manual hours projected to convert manually, including approximately 170 hours to clean up i.e. around 43 weeks to complete. Testing time excluded, but in a manual conversion it will be very significant.

  3. Approximately 2 hours to convert using 2SQL, with only the 170 hours to complete the cleanup i.e. around 4.3 weeks to complete the conversion. The time saving is therefore 90% over manual conversion. Because 2SQL produces accurate and very comprehensive results, testing time will not be significant.

Medium-Complex database conversion key statistics

  1. 40+ Tables, 220+ SQL Statements and 2,600+ Conversion Issues.

  2. Around 450 hours projected to convert manually, including approximately 45 hours to clean up i.e. around 11 weeks to complete. Testing time excluded, but in a manual conversion can also be quite significant.

  3. Approximately 10 minutes to convert using 2SQL, with only 45 manual hours to clean up i.e. around 1 week to complete the conversion. Again, the time saving is around 90% (or more) over manual conversion. Testing time will not be significant.

Simple database conversion key statistics

  1. 15+ Tables, 35+ SQL Statements and 400+ Conversion Issues.

  2. Around 50 hours projected to convert manually, including approximately 5 hours to clean up i.e. around 7 days to complete. Testing time will not be significant.

  3. Around 2 minutes to convert using 2SQL, with only 5 manual hours to clean up and complete the conversion. Time saving is again 90% (or greater) over manual conversion. Testing time will be minimal.

The above empirical case studies have only worked with hours and not attempted to calculate project costs because the rates per hour will vary dramatically between in-house and outsourced conversion projects.