1

I have several SSIS packages jobs running, and some months ago my disk got full because the size of the SSISDB database.

I noticed that the cleanup_server_retention_window was set to 365 days, and I changed it to one day. (It is a development server, and at this point I really dont care about the history).

The (big) problem, obviously, is now that the transaction log grows a lot and fast.

To prevent this, I start performing a full backup every week and a transaction log backup every day, and the size of the database is now controlled.

However, some more experienced guys are telling me that this is not the best aproach to this issue, but I cant see any problem with it..

I would like to know if there is a better solution for this.

1
  • 1
    Its funny that the person who is telling you this is not the best approach hasn't told you what the best approach is... Can you set the recovery model to Simple? Then the tlog won't grow. Note that you won't be able to recover this db to a point in time, but I'm not sure if that's necessary. – paulbarbin Sep 13 '16 at 19:09
3

Change the recovery model to SIMPLE and be done with it since this is a Development server and you mentioned you don't care about the history.

For more information on recovery models and transaction logs, see this excellent post from Gail Shaw.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.