How can I tell why the size of the database grew?

  • We implements Great Plains earlier this year. Everything has been running fine and smooth as it relates to SQL. The DB isn't that big, about 2gb. All of a sudden in the last couple of days, it has grown to 15gb. The developers say that nothing has changed, but something is going on. Right now I am going through each table looking for something abnormally large. Aside from that, is there anything else I can look at? I've never had this problem before where the file size shot up like that.

    Thanks

  • I assume your have determined it is the data file that has grown and not the transaction log file?

    ______________________________________________________________________________________________
    Forum posting etiquette.[/url] Get your answers faster.

  • Yes, it was the data file. I found the table that grew by 11gb by going through each table one at a time using Toad. It was a stored procedure that Microsoft gave me to run to check our GP data for an add-on module. It writes the findings to a table in GP. Now that I am looking at the SP, I do not see the data being cleared out, so it has just been adding and adding and adding.

    But I would still like know if there is a way to see any major changes, other than what I did.

  • adams.squared (7/15/2011)


    But I would still like know if there is a way to see any major changes, other than what I did.

    What about Change Data Capture?

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Viewing 4 posts - 1 through 3 (of 3 total)

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