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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-02-04 : 00:39:39
|
| Tim writes "I am trying to backup my Txn log regularly on a heavy transaction system (stores up to 500 transactions per second). When I perform the backup every 5 mins the system experiences a freeze for between 1 and 2 seconds. That is, our throughput goes down to 0 for this time period. 5 mins of transactions amount to 100 MBWhen the backup is taken every 15 mins the same freeze occurs for 10 secs.The live DB, Txn logs and backup locations are all separate physical disks. Is there anything I can do to stop (or minimize) this freeze? Does any one know why it is happening? I thought the idea of Txn log backups was to only backup completed transactions, thus having no effect on new or active transactions.Any help would be very much appreciated.Thanks" |
|
|
izaltsman
A custom title
1139 Posts |
Posted - 2002-02-04 : 11:32:05
|
| You didn't really provide a whole lot of information, but here is a couple ideas.Are you backing up to a network share? If so, then try backing up to a local disk, appending a timestamp to the name of the dump device file, and then moving the renamed file to a network share via a DOS command instead. The idea is to minimize the time it takes for SQL Server to complete the actual backup. If you are making your backup to a single device, consider introducing additional devices into the media set (especially if you can place each device on a separate physical disk). Edited by - izaltsman on 02/04/2002 11:34:09 |
 |
|
|
|
|
|
Transaction Log backup performance problem