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 |
snomad
Starting Member
22 Posts |
Posted - 2009-08-19 : 08:28:33
|
db = simple recovery model but "the transaction log for database 'x' is full"am i being a total muppet? my understanding is that transactions are not logged to the log whilst the db is in simple recovery model. so how can it be full?many thanks in advance. Thank you!! |
|
YellowBug
Aged Yak Warrior
616 Posts |
Posted - 2009-08-19 : 08:46:06
|
Any open transactions? DBCC OPENTRANTransactions are still logged in SIMPLE mode, but the log is truncated periodically (up to the last committed transaction). |
 |
|
snomad
Starting Member
22 Posts |
Posted - 2009-08-19 : 09:47:35
|
Yes there is! I see, so trans are still logged and may fill the log if uncommitted. Will go tell the users to batch. Doh! Thanks YellowBug. My basic assuptions were wrong. Great, thank you!!!Thank you!! |
 |
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2009-08-19 : 10:31:02
|
you'll get that error also if log file growth is set to restricted and the file reaches the max allowed size |
 |
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2009-08-19 : 11:05:32
|
All transactions are logged in all recovery models. The main thing that the recovery models affect is when log space is marked as reusable. In simple it's when a checkpoint occurs. In full/bulk-logged, it's when a log backup occurs.--Gail ShawSQL Server MVP |
 |
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-08-19 : 11:09:59
|
Doesn't matter with recovery model, If you doing huge DML operations in Simple Recovery Model in 1 transaction, Your log will grow like crazy.Rather have batch operations. |
 |
|
|
|
|