July 11, 2016 at 4:41 pm
I have a sql server with a ssis database that is 80 gigs with a retention period of 365 days. This Server is very slow in performance in and super slow deploying packages.
1.) I have been given the task to change the retention to 30 days. During the job, how will this affect the sql server in regards to Performance and sequel jobs?
2.) Since the database is this large would it be smart for us to go with such a dramatic change and retention period?
3.) What exactly is removed from the database?
July 11, 2016 at 4:52 pm
3) Mostly logs about performance, execution, ...
We cut it to 90 days after the catalog grew to half a terabyte. It will also save time when you have to patch sql server.
July 11, 2016 at 5:40 pm
Logging information is what gets removed.
While the job is running, your other SSIS jobs will not. Do not change from 365 to 30 in one hit, it will run for days. Instead, I suggest you progressively change the retention period downwards, 10 days at a time. It's not difficult to script this as a separate daily SQL Agent job.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply