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 - 2001-11-12 : 09:30:37
|
| Deborah writes "We are working with a SQL 7.0 server. Every day a database backup is scheduled for 22:00. Once a week the transactionlog is truncated and backed-up. The application is built in VB and runs on thin clients with loadbalancing Citrix servers.Yesterday the application using the database experienced performance problems. The transactionlog was so full it started extending itself. This happened 1,5 days after the backup of the transactionlog was done. SQL says that the job was succesful but the log was so full that it couldn't be the case. (a regular week takes +/- 200 Mb a busy week +/- 400 Mb) the log showed 420 Mb after 1,5 days.backing up the log and database:Normal backup times: transaction log - 3 minutesNormal backup times: database - 20 minutesAt the moment: transaction log - 60 minutes (and growing)At the moment: database log - jumped to 4,5 hrs and last night 10 hrs.Please could jou tell us where to look for the reason.ThanksDeborah" |
|
|
|
|
|
Back-up perfomance