June 15, 2007 at 9:57 am
We have our larger databases set with a maxsize property, but our smaller ones are set to unlimited. I'm just wanting to get people's opinion on the advantages / drawbacks of using a maxsize value versus unlimited file growth.
Thanks
Jim
Regards, Jim C
June 15, 2007 at 1:37 pm
Just my 2ct
- you have to followup size and actual usage anyway.
- if you set maxsize, you have controle and can build a "critical disk reserve" so when the db reaches its maxsize, you can give it that little bit more to take serious actions. Applications will get errors when the file is full !
- By setting the maxsize of every db on a server(instance), you know the critical disk volume you have to provide.
- if you set it unlimited, you'll have to followup the growth. If e.g. a bug gets into an application, it may be able to write that mutch of info your disk(s) get full and also other databases will nolonger be able to extend !!
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply