I have a SQL Server 2019 database that we use for collection of logs from our software from machines on our network. We are required to hold these logs for a about a year. With the logging from our collection scripts, it loads up one of our databases which is currently around 500,000MB. This is for our current network of 5 computers and servers. WE plan on adding many more computers and servers. As the network grows, I have a few questions.
1. As we grow our network what should we set our database Maximum file size to since best practice should not be autogrowth unlimited?
2. Currently autogrowth is set to 10% to unlimited size, should I change it?
3. If I set a maximum size with autogrowth to a maximum size will it not input data into the database once filled?
4. Should I turn on Instant File Initialization to help limit the size and is it worth the security risk?
I am trying to get a head of my network growing and figure out what I will need to do to manage the growth.
Asked by JukEboX
(131 rep)
Feb 27, 2024, 08:16 PM