February 24, 2008 at 1:46 pm
Running 64-bit SQL 2005, run a Data transform to bring in all rows from an Access table and insert them into a SQL 2005 table - rows are randomly missing, never a complete rowset imported?
When I run the transform on a 32-bit SQL 2005 it imports all rows. When I design it on the 64-bit server it imports 16 out of 18 - randomly selecting which come over.
Running SQL 2005 64-bit, Service Pack 2. Using Native OLE DB Microsoft JET driver for Access DB.
:w00t:
Tried making package on 32-bit, then porting over to 64-bit, then running on WOW64 using CmdExec DTEXEC.EXE - still does not import all rows. It always runs, now errors or warnings but always missing 1-2 rows out 18.
February 24, 2008 at 6:11 pm
what da... itd be interesting to hear what microsoft say about it...
I run on 32bit. keep us posted.
M.Sc.IT, M.B.A, MCTS BI 2008, MCITP BI 2008, MCTS SQL Dev, CSM, CDVDM
February 24, 2008 at 7:56 pm
I have a two other things to try and work around it.
But if I can't get it figured out by noon tomorrow I'll open a case.
Still looking for clues - anyone???
February 26, 2008 at 12:45 pm
Definitely a driver bug.
Workaround:
To correct this open Visual Studio, then open the package that has issues as described above. Double click on the Data Flow item.
Right click on the OLE DB box for the MS Access or Excel transform and select Properties.
Look over on the Properties window look for the setting ValidateExternalMetadata and change its default setting of True to False.
Save the package.
😛
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply