January 3, 2008 at 11:37 pm
Hi Friends,
We encountered a bug with restricted file growth on our MSSQL 2005 infrastructure. We're not able to configure the transaction log files for unrestricted growth after we configured restricted file growth. In other words, we cannot get rid of the restricted transaction log configuration once we have it. Do anyone knows why this happens
Please give your valubale informations
January 4, 2008 at 3:03 am
Hi,
If any one know the reason the please let us know as after reading this post I tried it on on of our testing server and once I change it to restricted growth from unrestricted, I'm not able to revert it, and now its showing as "By 10 percent, restricted growth to 2097152 MB". My Server Details are as follows.
Product Version: Microsoft SQL Server Standard Edition
OS: Microsoft Windows NT 5.0 (2195)
Version: 9.00.1399.06
Thanks,
Rohit
January 7, 2008 at 1:51 am
Hi
do you mean that after changing to unrestricted file growth
it still shows restricted file growth to "2,097,152" MB ?
maximum log file size is 2 TB i.e "2,097,152" MB.
"Keep Trying"
December 4, 2008 at 8:31 am
Hi,
I have the same problem with all my DBs in the production server. My @@version is 9.00.1399 standard edition. All databases appears like:
Check Enable Autogrowth
File Growth
Check In Percent 10
Maximum File Size
Check Restricted File Growth (MB) 2.097.152
I can't change the Maximum File Size to Unrestricted File Growth, it returns to:
Restricted File Growth (MB) 2.097.152
I can change the value 2.097.152 for any, but i need to change to Unrestricted
Thanks for any help.
December 4, 2008 at 9:12 am
hi,
I found this page
http://www.exactsoftware.com/Docs/DocView.aspx?DocumentID=%7B2b24915c-66b5-4cec-a70b-e3cb414b8821%7D
Microsoft says is not a bug?
December 4, 2008 at 1:25 pm
It is not a bug in "behavior" but (in my opinion) it is, in terms of what the UI shows 😀
* Noel
December 4, 2008 at 2:57 pm
Don Marlini (12/4/2008)
Microsoft says is not a bug?
...reminds me of the old joke: How many Microsoft programmers does it take to change a lightbulb? 0, they declare darkness the default! 😀
Anyway, if you're properly maintaining your database, have transaction log backups scheduled at an appropriate frequency for your system's environment, and use minnimal logging for bulk loads when possible then you'll probably never get anywhere near that 2 terabyte limit. If you are processing that much data that you need 2 terabyte transaction logs then you probably need a more robust relational database than SQL Server anyway.
December 5, 2008 at 8:03 pm
LOL, thanks for your help!
March 28, 2011 at 9:23 am
Chris Harshman (12/4/2008)
Don Marlini (12/4/2008)
Microsoft says is not a bug?...reminds me of the old joke: How many Microsoft programmers does it take to change a lightbulb? 0, they declare darkness the default! 😀
Anyway, if you're properly maintaining your database, have transaction log backups scheduled at an appropriate frequency for your system's environment, and use minnimal logging for bulk loads when possible then you'll probably never get anywhere near that 2 terabyte limit. If you are processing that much data that you need 2 terabyte transaction logs then you probably need a more robust relational database than SQL Server anyway.
Hello Chris, Just for my info, what kind of RDBMS is more robust that SQL Server? Please forgive my ignorance on this one, but I was under the impression that SQL Server was just as robust as Oracle, DB2, MySQL or anything else out there in the market place, even better than those.
Regards,
Dale
March 28, 2011 at 9:40 am
Please note: 3 year old thread.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 10, 2012 at 10:41 am
For the restricted growth & all, one of my test boxes is holding a single LDF on sql 2005 sp4 (x64) which is currently @ 2.57 TB.
Believe the 2 TB limit is for MBR partitions & no holds bar for GPT.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply