question

GrahamElder10 avatar image
GrahamElder10 asked

Database and Transaction Logs - Initial Sizing

I'm general IT Support, and one of the many hats I am currently wearing is being involved in project involving uploads of a large number of documents to a new application running Sharepoint Document Libraries stored on a new SQL Server 2014. My SQL background is very basic.

I'm getting bogged down in trying to pre-size the Database and Log files. I have a pretty good handle on the sizes of upload to each of the 99 databases, so I ran a test upload.

I calculated the total file size for Database01 at 7.2Gb from Windows so presized it to 8.00Gb in SQL. The total size of Database01 increased to 8.5Gb following the upload - meaning 585 autogrowths of 1Mb each.

I did not pre-size the Transaction Log and it increased from 424.75Mb to 8.90Gb - with around 32 autogrowths of 10%.

So my question is - am I being too picky in trying to presize these files? I understand that the autogrowths will add time to the upload, but are there long term effects to database or log performance from having so many?

Our application vendor was ready just to upload the whole lot without any changes to initial size or autogrowth figures.

Many thanks in advance

Graham

sqlsql server 2014data-importdatabase sizedatabase growth
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

0 Answers

· Write an Answer

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.