![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
This is a wierd problem and I am clueless on what caused it. Using SQL Server 2000 Enterprise on Windows 2000 my client is XP Pro with Developer Edition. I have a collection of backedup databases which I am combining into one massive database(only certain tables), as they come in. I was doing it by restoring them to my local computer then using DTS to export them to the enterprise data, never had any error message or indications of stuff being wrong. Everything looked good when we did a few of them and tested, so I started doing bunch more as they came in. After a few weeks we discovered a problem of columns having nulled out data and even some imports missing a few rows. Anyone have any clue on what would cause this or additional places to look for errors? PS When this was discovered I went and wrote up a script to do a bunch of insert...intos and have not had any problems with that. Just curious about the DTS dropping stuff. PPS after I had imported using my script upto the point where it was equal with DTS imported data, and was missing 1.16% of the rows. |
#3
| |||
| |||
|
|
DTS shouldn't drop any rows at all. SQL Server to SQL Server ? Sp levels and versions the same? Collations the same? Do you check the count of rows that qualify to be inserted first before inserting? Stange but it shouldn't be happening. -- ---------------------------- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.allisonmitchell.com - Expert SQL Server Consultancy. www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org |
#4
| |||
| |||
|
|
Both machines are upto date with the latest patches as of last week, collations are the same. The only database differences is that the non-enterprise tables have had all thier indexes stripped. I am just doing a straight table to table copy so all rows should of copied. I am just chalking it up to cosmic rays or to the terrible network between me and the server, but figured I would ask if thier were some known but not offically documented problems. "Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote DTS shouldn't drop any rows at all. SQL Server to SQL Server ? Sp levels and versions the same? Collations the same? Do you check the count of rows that qualify to be inserted first before inserting? Stange but it shouldn't be happening. -- ---------------------------- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.allisonmitchell.com - Expert SQL Server Consultancy. www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org |
![]() |
| Thread Tools | |
| Display Modes | |
| |