Hi,

I don't know if it's really on topic but I thought it's best to ask here (since i assume it's a very common problem): Suppose we have a situation where a product built with LLBLGen is "in the field" with several customers, and you want to deploy a new version of the product to your customers. The new product requires some changes to the DB (assuming SQL2005), and ships with a new compiled datalayer. Ofcourse we cannot just put a new empty MDF file at the client site, we have to "upgrade" their database to the new version, so no data gets lost. What is the best approach to do this ..are their comercial solutions that can "compare" 2 database-schema's and fill in the missing stuff ? If using "custom scripts", what if the clients old DB is not 1 version old, but 2 versions old (e.g. they skipped an upgrade)... I bet at least some of you guys have been presented this problem before and would very much appreciate some hints/solutions because i will be in this situation too, soon

Hi,

Try Red Gate SQL Compare. The last version works with SQL 2005

When it comes to schema comparing, you might want to have a look at SQL Delta

It also generate scripts to update different databases to match each other

Anyone have any experience with both the Red Gate tools AND Innovartis DB Ghost? We're evaluating these for purchase...

Jeff...

jeffreygg wrote:

Anyone have any experience with both the Red Gate tools AND Innovartis DB Ghost? We're evaluating these for purchase...

Jeff...

Hi Jeff,

we have licences for both DBGhost and SQLCompare so I guess I have experience with both of them ...

DBGhost is a tool for managing your database development and deployment process. You will need to change your process (for the better in my opinion) to make DBGhost work. But afterwards you will never, ever go back. You will not only save loads of time but you will also gain a new piece of mind because you know you database deployment WILL work. All the time, every time..

Best development support tool I ever used. Download a trial, allocate one day for setting up a test environment and I am almost 100% sure you'll buy it.

We still use SQLCompare sometimes when we want to get a detailed diff between two existing databases. SQLCompare is better at showing the differences. But for deploying to a customer site, I am not interested in the diffs, I am interested that the databases are in sync after deployment.

So we use DBGhost every day and SQLCompare once a year.

Last time I was so excited with a product was with LLBLGen ... ;-)

Stefan