July 31, 2007 at 5:41 am
So I'm going over the Microsoft SQL Server 2005 Implementation and Maintenance book for exam 70-731 (published by Microsoft Press itself) and find the following line on page 504:
"All maintenance plans are now implemented as monolithic SSIS pacakages, and each package can have only one schedule attached to it."
Okay, now you know a component has issues when even your writers call something "monolithic". @=)
I just find this line incredibly hilarious for some reason. @=)
August 2, 2007 at 8:05 am
So - is it the diseased implication (SSIS has mono), is it the rocky road aspect (..lithic), or is it just that SSIS is enforcing a layer of simplicity within the code which could, in theory, increase the management effort - you actually have to split out your hourly, daily, weekly, monthly, month-end, and year-end jobs just like in the 'old days'? Next thing you know, someone will be, again, advocating meaningless names to describe these different jobs (e.g., job1, job2....)
August 2, 2007 at 8:18 am
I think the author's point was that maintenance used to be simple. Then Microsoft re-wrote the whole thing and made it ten times more difficult in an effort to improve the SQL Engine.
Of course, I concede that the DBMP in SQL 2000 does have its issues... Then again, 2005's DBMP has a lot of bugs. Enough bugs that still I'm forced to do things the old fashioned T-SQL way.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply