How are you exporting the databases ?
The error will come from the destination not the source.
SQL Server will use the log to store transactions before they are committed
Do you have your log set to autogrow ? Sometimes SQL Server's expanding of
the log file cannot keep up with the demand on it and the application will
see a Transaction log full message
If you do not have it set to graow automatically, has it reached the end ?
Have you run out of disk space.?
--
----------------------------
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Andreas" <andreasy (AT) netu (DOT) com.cy> wrote
Quote:
I use a DTS package which incorporates the export of several dbs on
another
server. Some of the dbs are exported successfully, some not because the
Transaction log is full. What I do not understand is why can the logs be
full since I use Log Shipping which performs backup on all logs every 15
minutes. This should truncate the logs as well right? |