blogs.conchango.com

welcome to the conchango blogging site
Welcome to blogs.conchango.com Sign in | Join | Help
in Search
Blogs

SSIS Junkie

I'm loving datadude

I want to take the opportunity give a little bit of love out to the datadude team.

Just now I wanted to move one of my tables into a different schema. This table is referenced in countless pieces of code so I used Refactor-->Move Schema to make the change. All of my code that references the table is auto checked-out of source control and updated accordingly. I checked the stuff in and with a little wave of my 'schema comparison' magic wand everything gets pushed out to my development database.

This took me all of about 20 seconds. I dread to think how long this would have taken me to do by hand especially after correcting all the human errors that I would have undoubtedly made.

Love it. Absolutely love it.

That is all. Cheers.

-Jamie

Published 23 November 2007 08:13 by jamie.thomson

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

Blogging Business Live, everything about markets! » I’m loving datadude said:

PingBack from http://www.blogging-business-live.info/?p=15291

November 23, 2007 10:44
 

blindman said:

I'm hating datadude.  Between 25 and 50% of the hours on our current project have been eaten up trying to get this tool to work.  I have yet to see any benefit come out of it that we did not have before.  Now, weeks after production release, I find that dozens of critical code and schema changes never got rolled out to testing and production.

I just spent two hours debugging a production issue only to find out that the production trigger is missing a critical code change I implemented months ago.  So I tried comparing the production schema to my development schema to find any other missing changes, and EVERY SINGLE OBJECT GETS FLAGGED, because the comparison does not ignore whitespace.  I am forced to script out 1000 objects from each database into text files so I can manually compare them.

This Database Professional thinks that Visual Studio Database Professional sucks.

December 7, 2007 21:38
 

BIGuru said:

Jaime - I agree that VSTE4DB's refactoring option is a great time saver and helps eliminate human error.  What did you do to modify your SSIS packages to point to the new schema?  

When I've been faced with a similar issue, I've gone low tech and opened the .dtsx files in a text editor and performed a Find->Replace being very careful only to "replace" in the appropriate places. Do you have a more elegant solution for this?

December 13, 2007 03:14
 

jamie.thomson said:

Hi BIGuru,

In this scenario I haven't been using SSIS so didn't have that problem. Unfortunately the only mechanism that I know is a manual replace or the method that you opted for.

cheers

Jamie

December 13, 2007 09:39
 

DBAFlash said:

As far as I know the schema compare does ignore whitespace - when you configure it to do so in Tools\Options\Database Tools\Schema Compare - "ignore whitespace".

An interesting 'feature' of the schema comparison that I have observed is that whitespace differences are still treated as 'skip' update actions. I can't seem to get the SC to mark them for update - which is a good thing as far as I am concerned, as I don't care about whitespace or formatting when doing a schema comparison.

July 29, 2008 10:54

Leave a Comment

(required) 
(optional)
(required) 
Submit

This Blog

Syndication

News
© 2008 - Any comments or statements made herein do not necessarily reflect those of Conchango.
Powered by Community Server (Personal Edition), by Telligent Systems