November 3, 2004 at 10:06 am
I am using the import wizard to move stored procedures between two servers. On some databases when I move an object it will truncate the log of the database I am moving to. Othere database moves do not truncate the log. What is causing the destination database log to be truncated?
Thanks
November 4, 2004 at 9:41 am
What recovery model is used for the destination database(s)?
What are the details of your import? Are you only moving stored procedures? Are you dropping and recreating the objects in the destination database?
Greg
Greg
November 4, 2004 at 10:20 am
Moving stored procedures would not truncate the log. How are you noticing that the log is getting truncated?
Francis
-----------------
SQLRanger.com
November 4, 2004 at 10:45 am
Recovery model of the database is set to full.
I am using the copy objects between sql server databases option
I am using the create destination objects option
I am using the drop destination first option
I was only moving one stored procedure from a test environment to a production environment
I noticed the transaction log was being truncated by checking the SQL Server logs.
This only happens on certain databases, not for all databases.
November 4, 2004 at 12:05 pm
Do you have log backups scheduled on the destination database? I agree with Francis in that dropping and creating a stored procedure won't truncate the log. It may be a coincidence that you're copying stored procedures at about the same time as a log backup occurs. In full recovery mode, a log backup truncates the log after the backup completes.
Greg
Greg
November 4, 2004 at 12:14 pm
No log backups are scheduled. I receive the truncate message in the sql logs everytime a procedure is moved.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply