Log was generated by the VB app that was having issues because default val
was not being inserted into a not null field. Had to read tons of log file
to find it. A developer issue, obviously.
Is this a bug? Been trying to document for downtime report and 'I dunno'
tics off the boss. I should have validated the Table instead of the Data.
Nothing on knowledge base that I can find. Will definetly take your advice
for future 'recovery's'.

Thanks

-----Original Message-----
From: Sherman, Bill [mailto:[Email Address Removed] Thursday, September 04, 2003 11:02 AM
To: Chip Smith
Subject: RE: sql server import/export successful but incomplete


Whats was the name of this obscure log and why did the insert fail.
We used to use DTS to copy DB's under 7 but gave up on it when we went to
sqlsvr 2k because
its flat out failed for no apparent reason.
Use BCp to dump/load individual tables.
Heres a script to sump all tables.
Change the "out" to "in" to import.
Tables go to the c:temp directory.
? represents the tablename returned by msforeachtable.

sp_MSforeachtable
@command1="master..xp_cmdshell 'bcp SURVEY.? out c:\TEMP\? /U sa /P sa /S
PSNT /c'"
go
^^^^^^ db name
^^^ SQL SVR INSTANCE

-----Original Message-----

From: Chip Smith [mailto:[Email Address Removed] Thursday, September 04, 2003 9:22 AM
To: LazyDBA.com Discussion
Subject: sql server import/export successful but incomplete


Hi list,
SQL2K on SP1 with cluster.
WIN2K SP3
Did an import of a table from one server to another , ie; used dts to create
and copy the table.
Worked fine, however it did not bring the column default settings along with
it. Those had to be done by hand.
Question is , is this normal behavior?
Caused a lot of problems until we discovered a failed insert in an obscure
log file.

TIA

-- Chip
OCP DBA
MS Sql Server LazyDBA home page