Size estimations

  • Could someone please help me with the size estimations of a database??

    I need to do size estimations on a database which is currently residing on a server. We send the trace data to a table which exists in this database.

    This database is very small as the table has following columns:

    dbatraceID, StartTime, EventClass, EventSubClass, DatabaseId, DatabaseName,SPID ,LoginName , DBUserName, ServerName, ObjectType, ObjectID, ObjectName

    But the new requirement is that I need to add TextData column to this table. I'm expecting the database to grow rapidly.

    How can I estimate the growth of this database?

  • Looks like you are storing a trace information in that table..

    It is you who has more information than any one..

    By that what I would say is, try doing a test run (for few mins) and see how large that table grew (with the Text Data column) and then calculate the expected size depending on how many users were there when you did the test and if the users might grow in the near future, then keep that in mind when doing the size calculations..

    If you are doing this in off peak hours, then keep in mind, you might not be having the expected amount of data captured, so your table size would be lower than what it is during peak hours..

    Hope this will help you getting started..


    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • Thanks Bru.

    I found a way of doing it but not sure if it's correct:

    Using Idera diagnostic manager tool, I found out that the table with textdata has 158 transactions and its size is 0.9MB(Data is 0.05MB, Index is 0.02MB and Text is 0.84MB)

    --158 transactions with textdata is 0.9MB

    --In a single day, approximately 15000 transactions hit the database

    select (15000*0.9)/158

    --So per day, the size of the table could grow to 85MB

    select 85*30

    --Per month, it could grow to 2550MB

    select 2550*12

    --Per year, it could grow to 30600MB

  • Also consider if you are going to have new indexes on one or more columns (may be startdatetime or login name etc)..


    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • As far as I know, we aren't going to add any indexes.

    Is my math correct?

  • This is a good place to start looking:

    http://msdn.microsoft.com/en-us/library/ms187445.aspx

    -- Gianluca Sartori

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply