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 |
|
astralis
Yak Posting Veteran
62 Posts |
 Posted - 2015-03-14 : 19:22:39
|
| I'm adding a .bak file to a new SQL Server where the auto-growth of the log size is set to unlimited, but while I add it, the log size changes and then I receive an aerror that says:The transaction log for database 'mydbname' is full due to 'NOTHING'.I think if I can keep the transaction log to unlimited autogrowth that I will be able to insert the .bak file into the new server. |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
|
|
astralis
Yak Posting Veteran
62 Posts |
Posted - 2015-03-15 : 19:24:29
|
| I appreciate the link but I have a full disk and the log file is not that large. So space is not an issue.When I set it to autogrowth, the settings change automatically back to restricted growth. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2015-03-16 : 12:29:22
|
| Ignore the GUI when it switches it back to restricted growth. It's still unlimited, but it'll report a very high number for restricted growth.I don't understand how a bak file is related to the tlog being full. What do you mean you are adding a bak file to a new SQL Server? Are you doing a restore?What does sys.databases show for the log_reuse_wait_desc column for the respective database?Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
|
|
|
|
|
|
While .bak file is added, log size growth changes