Mike Shammas
2010-03-30 14:41:01 UTC
My customer is on a path to moving away from Access databases to SQL Server
(an iterim measure to allow them to use an IBM tool (InfoSphere?) to do a
fuller analysis of their data.
They need to get 100's to 1000's of user-built Access databases migrated to
SQL Server in a controlled way, with minimal intervention. Ignoring the
fact that data migration can't be dealt with properly this way, what is the
MS recommended route for carrying out such an operation? Is there a standard
tool for doing this, or is a 3rd party tool available (that won't go down
well), or should be craft some control code around a simpler tool?
Any advice would be welcome.
(an iterim measure to allow them to use an IBM tool (InfoSphere?) to do a
fuller analysis of their data.
They need to get 100's to 1000's of user-built Access databases migrated to
SQL Server in a controlled way, with minimal intervention. Ignoring the
fact that data migration can't be dealt with properly this way, what is the
MS recommended route for carrying out such an operation? Is there a standard
tool for doing this, or is a 3rd party tool available (that won't go down
well), or should be craft some control code around a simpler tool?
Any advice would be welcome.