November 19, 2007 at 4:11 am
I have a database on which the SSIS packages are dependent on. My question is how do I make SSIS design to make it resilient to source database schema changes ? Since the database that SSIS depends upon is constanly changing; and for the matter of fact, the SSIS embedes metadata information into package.
I hope I got through to you gurus. This might seems to be a very trivial thing to you gurus. 🙂
Thanks.
FP
November 19, 2007 at 9:44 am
First off, guru or not this is an ongoing quest.
Design vs. business need. There is no way to prepare or develop for 100% of the changing scenarios.
On that matter though, to prepare for ongoing changes you must do so by the architecture you use. Preparing just at the database level doesn't help you too much. Things I have found is using dynamically compiled SQL and other things like that handled by a secure application level tier. This abstraction layer prevents coders from writing directly to the database, but also makes changes much easily to develop to than the traditional stored procedure/non-ORM based architecture.
I felt I rambled, to sum up. Prepare for that via the architecture, not with a single piece of technology.
November 19, 2007 at 10:24 pm
I might sounds a bit clinge ... well b/c upto some extend i am acting like one; when I ask do you have any guidelines / strategies or your personal design that you might want to share. I need a starting point to start my "quest" for light 🙂
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply