Post reply

SHRINKFILE

  • September 21, 2006 at 5:35 pm

    #172766

    I have a SQL=based application that brings in 200,000 transactions a day, does all kind of analysis against the data, retains some summary data, then truncates the data.

    I just noticed during the development phase (about a month), the log has grown to 20 gigs.  I used this to shrink it.

    Backup LOG MyPigData WITH NO_LOG

    DBCC SHRINKFILE ('MyPigData_log',5,TRUNCATEONLY)

    QUESTION:  If I run this every week, am I going to create any problems/issues?  What else should I be concerned with?

  • September 21, 2006 at 7:26 pm

    #661894

    What is the currrent setting on your database?

    If there is no need to restore the database (in the event of database corruption) to a point in time, then ideally the database should be set to SIMPLE recovery mode, since you are importing considerable amount of records daily, hence the logging and the growth of the log file. In this case, your approach to backup the log with NO_LOG is appropriate. Hopefully, you also have a full database backup plan in place.

Viewing 2 posts - 1 through 1 (of 1 total)

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