Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
scullee
Posting Yak Master
103 Posts |
 Posted - 2003-11-30 : 21:38:14
|
| We are currently log shipping with scripts from http://www.sql-server-performance.com/sql_server_log_shipping.asp . Every night we are running a full database copy across to the other server then calling the restore script on the other server. The database has grown in size and is now taking over 10 minutes to do the restore and the connection to the linked server is timing out. We tried setting this timeout to be 0 (or infinate) but this doesnt seem to help. Does anyone have a better way to get around this problem? |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2003-12-01 : 02:31:22
|
| Haven't seen the scripts but whenever I implement log shipping I do the backups from a scheduled task on the source server then have another scheduled task on the destination to do the copy and restore.In this way you don't get failed tasks on the source server when the destination is not available and everything is controlled by the server which is being updated.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
|
|
|
Problem with timeouts on linked server