The speed of the system or the size of the log could be the issue. Does
it need backing up at this point or can you truncate it and back it up.
Surely your records have been committed by now.

-----Original Message-----
From: Maskevich, Tony [mailto:Tony.[Email Address Removed]
Sent: Wednesday, September 11, 2002 8:38 AM
To: LazyDBA.com Discussion
Subject: RE: Timeout Issues

It is a straight forward T log, I set it up using the maintenance plan
wizard, on the integrity tab I unchecked the run before backing up.

-----Original Message-----
From: Ken Nickels [mailto:[Email Address Removed] Wednesday, September 11, 2002 8:23 AM
To: LazyDBA.com Discussion
Subject: FW: Timeout Issues


You need to post some more details, like is this job involved in log
shipping to another server? If so, you may need to adjust the remote
query
timeout value.



-----Original Message-----
From: Maskevich, Tony [mailto:Tony.[Email Address Removed] Wednesday, September 11, 2002 9:24 AM
To: LazyDBA.com Discussion
Subject: Timeout Issues


I am getting the following errors randomly. They are occurring on my
Transaction Log backups. There seems to be no rhyme or reason. Here it
is
any help would be appreciated as to why this might be happening.


Microsoft (R) SQLMaint Utility (Unicode),
Version [Microsoft SQL-DMO (ODBC SQLState: HYT00)]
Error 0: [Microsoft][ODBC SQL Server Driver]Timeout expired




---------------------------------------------------------------------
To unsubscribe, e-mail: mssqldba-[Email Address Removed] additional commands, e-mail: mssqldba-[Email Address Removed] unsubscribe, e-mail: mssqldba-[Email Address Removed] additional commands, e-mail: mssqldba-[Email Address Removed] unsubscribe, e-mail: mssqldba-[Email Address Removed] additional commands, e-mail: mssqldba-[Email Address Removed]MS Sql Server LazyDBA home page