November 16, 2010 at 6:18 am
It's MS Access 2003
this is the Error msg I got
"TITLE: Connection Manager
------------------------------
Test connection failed because of an error in initializing provider. Cannot open the Microsoft Jet engine workgroup information file.
------------------------------
BUTTONS:
OK
------------------------------
"
November 16, 2010 at 6:26 am
hmmm...struggling to spot it
you could see if there is an ldb on connection...
and the db or the workgroup file may be corrupted...so a compact/repair wouldn't hurt
(but i'm guessing!)
January 24, 2011 at 2:36 pm
When setting the path in the "Jet OLEDB:System Database" section, it does not work when the file is not called the default "System.mdw" name. I found a simple copy and rename of the file to the default "Security.mdw" and include the filename as part of the "Jet OLEDB:System Database" value.
January 25, 2011 at 7:28 am
I'm not sure why anyone would mess with SSIS to migrate an Access db into SQL Server, as Microsoft has a FREE tool to do it called SQL Server Migration Assistant (or SSMA). It gives you everything you need to migrate data, and comes in various versions based on which version of Access and which version of SQL Server you are using. I don't have a link handy, but I'm quite sure a Google search would quickly identify where to get it from. You do have to register it with an e-mail address and then receive a license key, but that's a real nit, given the extraordinary utility it has. Check it out, folks...
Steve
(aka sgmunson)
:-):-):-)
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
January 25, 2011 at 7:39 am
Steve,
I'm sure that will be a very valuable tool for migration and probably doesn't get the exposure it should have. However, when using Access as a SSIS datasource for BI applications, it is probably a better option to include the Access source as part of a package dataflow.
January 25, 2011 at 9:27 am
My response was based on the following text from the original post:
"I need to use an MS Access database as my datasource to do some work on it to migrate it to SQL Server."
.... which clearly uses the word MIGRATE. One time events such as migrations are FAR better handled by SSMA than by using SSIS. Had the OP indicated this was to be a regular event, I never would have posted, as clearly, SSIS would need to be the methodology.
Steve
(aka sgmunson)
:-):-):-)
Simon.Enion (1/25/2011)
Steve,I'm sure that will be a very valuable tool for migration and probably doesn't get the exposure it should have. However, when using Access as a SSIS datasource for BI applications, it is probably a better option to include the Access source as part of a package dataflow.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply