April 8, 2008 at 11:01 pm
Good article. I've always as a matter of habit scripted drop & create commands because of the potential problems they may cause but, over time, had forgotten exactly why I started doing it 🙂 Good article! I'm not really well versed in SSIS but have occasionally used the copy tasks with mixed results - at least I can keep this in mind when using it.
Also, you cannot really disable sp_rename because it's used by SQL Server diagram schema saving code generation (I'm sure it has a better name than that!) extensively. If you change the schema of a table it creates a table with a similar name and the new schema, transfers the data, drops the old table, renames the new table and recreates referential integrity, etc. If sp_rename was crippled then you'd run into interesting issues 🙂
June 4, 2008 at 1:18 am
🙂 Many Thanks.
July 4, 2008 at 4:11 am
🙂 At last! the answer to Transfer Server Objects
Set CopySchema to True!
Many thanks I've been looking for this for a while.
October 29, 2008 at 3:59 pm
Steve, Well done!!!
I am not a SQL developer at all but have been forced into this because I have 3GL background LOL and appearently overly ambitious. So I have a new 2005 database going live in two months and have to create a monthly migration package. I am learning SSIS on my own because my Company cannot afford training. Enough of my sad story. I have some questions on your diagram because I need to do the same thing and I got the same errors and I want to make it dynamic like yours. I have questions on the Looping and passing the list of objects from the storage to the DROP FOR LOOP.
I hate beg but if you have a moment you might be able to get me on the right track.
My name is Steve Cogan
My email is scogan@zoomtown.com if you are intested in answering some questions send me an email and I will email back.
Sincerely,
Steve Cogan
January 5, 2009 at 11:07 am
Microsoft took an intuitive, easy-to-use tool (DTS), and turned into a needlessly complicated, buggy disaster called SSIS. I believe Microsoft has completely lost touch with who their customers really are. Most SQL Server users are people like me, who work on multiple projects with tight budgets and timelines. I need a tool that solves the most common problems quickly, reliably, and intuitively. SSIS is not intuitive, is not easy to use, and is buggy and unreliable.
Granted, there are a handful of SQL Server uber-studs (and studettes) who need obscure programming features and capabilities that I could probably not even dream up. However, that is a small percentage of the SQL Server user community. The rest of us need to accomplish the most common tasks quickly.
I sincerely hope that Microsoft would get re-focused on the real users of SQL Server, and make SSIS usable for for the broad community of users.
January 21, 2009 at 4:51 am
It is a real bug-bear how MS rely on users to do their debugging for them and as somebody pointed out, for free!
Actually, its at a cost to us having to pay for support and be able to log a call, for which they then accept as a bug!
October 11, 2010 at 12:31 pm
Excellent article...the communication is very clear. I have a similar problem with my database and have implemented a solution without using vb.net in which such procedures with changed names are found and filtered rather than being changed and compiled again in the destination database. I wonder if we can create a DDL trigger that can prevent users from changing names of Stored Procs from Object Explorer.
Viewing 7 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply