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 |
|
bpollitt
Starting Member
4 Posts |
 Posted - 2006-01-10 : 16:14:54
|
| Hello everyone, I am a novice adminstrator for a server that is currently hosting an application and warm standby database for the main primary production server. The model database virtual log seems to continually increase in size, and is setting off alerts that the client beleive is causing some performance problems. Of course the immediate solution is the increase the size of the log so it is never fully utilized, but is there another way to determine why the model t-log would increase in size without the problem occuring currently?Are there are thoughts or scenarios where the transaction log for the model database would grow in the first place? To my understanding, the model db is simply there to server as a template for new databases and should not really have a log that is active.Thanks in advance for any assistance.B |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2006-01-10 : 16:32:16
|
| I always set model to simple recovery model so that if anyone creates a new database it would have that recovery model. That would cure your problem probably but you should use the profiler to see what is causing the tr log to grow - something must be updating the model database.==========================================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. |
 |
|
|
druer
Constraint Violating Yak Guru
314 Posts |
Posted - 2006-01-10 : 16:54:46
|
| Can you turn on the profiler against the MODEL dbid and see if some user is actually using it or something by mistake? (I have the same thought process you as ... nothing should be occuring in the MODEL db that would cause any transaction log activity.) |
|
|
|
|
|
|
Transaction log