July 16, 2012 at 7:10 am
I am working on an SQL Server 2008 R2 database.
Most of our maintenance is held in maintenance plans.
But I was wondering, how do you decide to put any to be scheduled work in:
- ssis package
- maintenance plan
- specific job
Are there any guidelines or reason why you would put something in SSIS package (made in BIDS) if you can write it as well directly in a T-SQL job?
Kr,
Sven
July 16, 2012 at 1:49 pm
I think it comes down to skill level and personal preference.
Maintenance plans are great for those shops that might not have a full-time DBA. They're easy to set up and don't require a lot of upkeep. The downside of maintenance plans, though, is that the tasks themselves are very basic and don't lend themselves to customization (i.e. specifying a BUFFERCOUNT on a backup, or a fragmentation level where an index will be rebuilt vs. reorganized, etc).
As long as the DBA has the skills to write the stored procedures and schedule them in jobs manually, or implement a solution like Ola Hallengren's[/url], I can't think of any reason to use a maintenance plan. Unless that DBA simply prefers to work with SSIS/Maintenance Plans.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply