csv?

regards,

Mark Baekdal

http://www.dbghost.com

http://www.innovartis.co.uk

+44 (0)208 241 1762

Build, Comparison and Synchronization from Source Control = Database change management for SQL...

You make your life so hard!

To me everything starts and ends with source control. The developers develop it, I audit it and deliver it. Continuous code builds ensure that...

I'm with you on this one Steve, I also think it will bring more head-aches than happy customers as developers (in general) love technology not business so they tend to use...

Sometimes it's just not worth upsetting the business analysts and supply them with a database which could be updated daily that they can do virtually what they want to and...

I would only say that you should avoid using system tables in your code as these are not supported and in SQL 2005 this code will fail. Kind of funny though that...

check out DB Ghost, it has a scripter component so you can script both schema and data and put into your source control, a build component so you can build...

If you had a database change management pratice in place these questions would always be answered. Ever thought about getting one?

Yes DB Ghost does a 30 day evaluation although it is very different from Redgates SQL Compare and Data Compare. This is a summary of the differences: http://www.innovartis.co.uk/FAQ_DB_Ghost_vs_Diff_Tools.asp

to summarize...

check out this article/white paper (it was also published on this site) http://www.innovartis.co.uk/pdf/Innovartis_An_Automated_Approach_To_Do_Change_Mgt.pdf . DB Ghost (http://www.dbghost.com) has been built using this document.

regards,

Mark Baekdal

I loved the article! I don't completely agree with it as I think XML has it's place although I think it is very limited. Like all tools if they are...

Try importing the data into a varchar column and use isdate and where is not a valid date - do what you need to do.

IE:

select * from table where isdate(date_column)=0

Hopefully I've understood...

Sounds to me like you need some sort of database change management. Here's an article/white paper on the subject - http://www.innovartis.co.uk/pdf/Innovartis_An_Automated_Approach_To_Do_Change_Mgt.pdf

this white paper is the foundation for the software called...

I guess what we are coming to is a matter of opinion, the goal is always to have a release that can be reversed out if necessary and there's more...

check out 'transactions, SQL statements not allowed' in books online

I also don't like all my DDL for a release inside a transaction as this would bloat the transaction log...

not all DDL can be put into a transaction. This is why I don't bother as the only fail safe method to rollback the changes made when running many DDL...