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 |
|
Sarat
Constraint Violating Yak Guru
265 Posts |
 Posted - 2002-12-13 : 16:19:41
|
| Hi, I performed index maintenance (rebuilt all indexes for about 8000 tables) yesterday, I backed up logs very frequently, the log file grew from 3.8 GB to 16 GB. I had to shrink it to 3.8 gb to have enough disk space (total 17 GB) . The log file all of sudden has decreased to 2.5 GB today and now all users are complaining about extreme slowness. What is the first thing i need to do to improve performance? I do rebuilding indexes and defrag once in a month. Can I increase log file size to speed up performace, if so how?Thanks.Sarat. |
|
|
Sarat
Constraint Violating Yak Guru
265 Posts |
Posted - 2002-12-13 : 16:31:01
|
| Ok, as I couldn't wait and users are bombarding me with phone calls, I went into EM and increased the T-Log size to 4500 from 3800 MB. The users will be running some queries now, do you think this will work? if not what should i do?thanks,sarat. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2002-12-13 : 17:20:43
|
| When you shrink a transaction log, you have to be careful because if the transaction log needs to be expanded, it will do so on the fly and will affect performance. Instead of shrinking the file, I would suggest backing up the log every 15 minutes or so, so that the log gets cleared of its transactions. I would bet that someone is running some large queries or maybe even runnings batch jobs which is causing the log to increase so drastically. |
|
|
|
m_mussu
Starting Member
4 Posts |
Posted - 2002-12-17 : 03:51:32
|
quote:
When you shrink a transaction log, you have to be careful because if the transaction log needs to be expanded, it will do so on the fly and will affect performance. Instead of shrinking the file, I would suggest backing up the log every 15 minutes or so, so that the log gets cleared of its transactions. I would bet that someone is running some large queries or maybe even runnings batch jobs which is causing the log to increase so drastically.
MOhammed A.Musaddique |
|
|
|
|
|
|
|
|
Poor Performance, Log file Size