SQL Server 2005 Auto Growth by Size

I watched the new database server that we are setting up for the client, and note that the database files are set to 1 megabyte each time the file is full and the initial size is 100 MB.

I reviewed this briefly, and it does not sound like that. I checked several sites for DB reasons, and they did not explain these values ​​properly.

I would probably only want the database files to expand once a month, let's say?

So, if I had to calculate the amount of data that I expect to be inserted per day in megabytes and just multiply by 30, should I find the right number?

i.e. I know about the size of 1 row and about as many rows will be inserted on average a week at the table. I know that these are estimates from scratch, so do you think that once a month a suitable approximation for a file extension or is it preferable to renew each hour>? or never?

We use full back so that we can restore time to the moment, and the transaction log is backed up, and the recovery procedure is apparently 100% effective. Will these types of changes affect backup and recovery altogether?

Thank.

+3
source share
7 answers

What you suggested is pretty much. You want auto-development based on what you expect to see.

, 1 , , , , , ​​ , .

, , , , ...

EDIT: http://searchsqlserver.techtarget.com/tip/0,289483,sid87_gci1330922,00.html , , , , , .

, , 1 -!

+3

, , , 100 , , , 5 . , .

, , , , , , .

, , , 1000 , 100 . , , 1100 110 . 1210, 121 . 1331, 133 . , .

2 .

, MODEL. MODEL .

+2

, , .

, , , , .

0

, , , . , .

, . . , " ";)

, . , , .

, , - , . SQL, , .

0

. , , .

, , , , .

0

SQL Server Management Studio 2008, - 1 ... , 1- ( , 2005 ).

, , , , . , 5 , , , , , 1 , , , , ( , ).

, , , , , .

0

( 5-10%), , . .

0
source

Source: https://habr.com/ru/post/1698261/


All Articles