Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SSIS and Import/Export (2005)
 Import of MSAccess limited to 64 tables

Author  Topic 

planoie
Starting Member

1 Post

Posted - 2007-03-27 : 12:23:54
I'm trying to import an Access 97 database of 75 tables. I got thru the standard Import Data wizard in SQL2005 and select all tables. During pre-execution I get an error that looks like this:

Pre-execute (Error)
Messages
Error 0xc0202009: {DBD1EAB5-7865-4B89-A7BB-DDC8507D8119}: An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft JET Database Engine" Hresult: 0x80004005 Description: "Unspecified error".
(SQL Server Import and Export Wizard)

Error 0xc020801c: Data Flow Task: The AcquireConnection method call to the connection manager "SourceConnectionOLEDB" failed with error code 0xC0202009.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Source 64 - <some table name>" (5206) failed the pre-execute phase and returned error code 0xC020801C.
(SQL Server Import and Export Wizard)


I started unchecking the table indicated in the third error detail from the import, and each time the error occurred again, indicating the NEXT table in succession as the offender. This continued until I had unselected the last 11 tables. This left 64 tables. Once I got to only 64 tables, the import worked just fine. So I did the first 64, then the rest in two passes and got the database imported.

I googled a bit but can only fine other people having the same or similar problem.

The problem is that I need to make an SSIS process to import this database on a regular basis (once a month). I think I can solve it with a split import, I'll just create two workflow steps to split apart the tables.

The real question is: Why on earth would SQL2005 limit the number of tables one could import?? I can't imagine this is a limitation within SQL server. Is the JET engine responsible for the limitation? And how does one work around this problem (aside from splitting the tables and running in multiple steps)?

Thanks,
Peter
   

- Advertisement -