I am using DTS in SQL2K to pull data and tables (copy tables and views from
source database selection) from a remote MSDE2000 installation. Things
appear to run OK, but I eventually get an error on a particular row everytime
for one table in particular.

The error varies between the Transaction Log file being full and "Error at
destination for row 3,869,407. Violation of PRIMARY KEY constraint
'IDX_EVENTS_ID'. Cannot insert duplicate key in object 'EVENTS' ".

The transaction log file was defaulted to 1GB hard stop. I increased that
to 2GB, 4GB and then 8GB and got similar messages, even after I ran a
database backup of just the Transaction Log file.

What appears to be the problem?

Robert

Hi,

Did you do a FILE backup of Transaction log file or did you make a
transaction log backup?
Did space used in transaction log dropped after backup?
If you did the first then you did not clear the transaction log. You should
do a second (transaction log backup) to clear some space in transaction log.

--
Danijel Novak



"Robert Gandrud" <RobertGandrud (AT) discussions (DOT) microsoft.com> wrote

I did a backup within SQL Ent. Mgr. Database Maint. and chose only the
Transaction Log for that particular database.

My understanding, is that it clears committed entries in the Tran Log file,
but doesn't actually change the size (make it smaller). Is this true?? And
if so, how can I make the log file smaller, after ensuring that all
transactions are committed?

thanks,
Robert
"Danijel Novak" wrote: