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 |
viplas
Starting Member
3 Posts |
Posted - 2008-03-04 : 12:00:18
|
We are trying to upgrade our application from version a.b.c.1500 to a.b.c.3500. During this upgrade, transaction log size increases from 25MB to 1975MB and it errors out saying "The log file for database is full. Back up the transactionlog for the database to free up some log space." In Database properties File growth is set to 'restricted' to max 2000 MB.So in order to not get this error, should I simply increass the File Growth Restriction to > 2000, is it safe? How can it adversly affect other things?Before starting upgrade we do truncate the log, and Preallocate space and after upgrade we Shrink DB. It's just that during upgrade Log is growing that big. Please advise. |
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-03-04 : 13:14:04
|
No you shouldn't do that. You should start backing up the transaction log on a regular basis if you require point in time recovery or switch the recovery model to SIMPLE.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
viplas
Starting Member
3 Posts |
Posted - 2008-03-04 : 15:24:13
|
Thanks for your response.Usually, what factor should decide that one should grow the Transaction Log only upto this much space (2000 MB in my case). and under what situations we should increase that? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-03-04 : 15:32:28
|
I don't ever restrict the growth of my database files. If you do restrict them and the database needs to grow beyond that limit then the application will get an error and continue getting an error until the restriction is increased. What you should do is figure out how much space the tlog needs in between each tlog backup, set that size and then leave it alone. Don't shrink the files ever in a production environment unless you know it no longer needs the space. Otherwise, you are creating a performance problem.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
viplas
Starting Member
3 Posts |
Posted - 2008-03-04 : 17:48:22
|
Thank you, this helps! |
|
|
|
|
|