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 |
|
bendertez
Yak Posting Veteran
94 Posts |
 Posted - 2007-11-09 : 06:09:06
|
| HelloWe have recently cloned a live server for use as a test server. The cloning seemed to have gone ok, we have changed the name, IP etc and it is now running completely independantly with just one issue.The transaction log size keeps increasing (by a large ammount) for some unknown reason even though there is hardly any activity going on.I can successfully shrink it but within a couple of days there it goes from about 10Mb to 3Gb with no or little activity on it.Can anyone think why it could be doing this?Is there an way of viewing the transactions so I could maybe fathom out what is causing this?I thought it might still be talking to the live server but the live transaction file is still quite small in size.As it is a clone I can't see how settings could have been changed for it to behave like this. I've checked them against live and they all seem the same....!!Can anybody shed any light on this?Thanks |
|
|
Kristen
Test
22859 Posts |
Posted - 2007-11-09 : 07:12:08
|
| "Can anyone think why it could be doing this?"Scheduled Index rebuild maintenance? That can be set up for "all databases" on the server, which will include newly created ones.Kristen |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-11-10 : 00:38:02
|
| What's db recovery model? Do you backup log in schedule? |
|
|
|
|
|
|
Transaction log increasing too quickly