Hi All,

Just read this article at http://aspnet.4guysfromrolla.com/articles/071305-1.aspx regarding creating db projects in vs.net to better manage scripts, sp, etc. rather than using Enterprise manager. Just wondering does anyone have any experience with this? Is this recommended. Any thoughts.

Eric

I do it on smaller projects. On bigger jobs, I prefer ERWin. RedGate has some really killer tools out for managing and deploying sql dbs and schema.

I find the "database project" quite useful, but it doesn't go the full mile for me. I wanted an "always synchronised" view of the database, rather than having to import tables all the time. And some sort of integrated Database diff would have been excellent.

What does ERWin do here - I thought it was just an ER modelling tool?

I wonder if VS2005 is going to improve on database integration....

Hi Eric,

we are using a tool called DbGhost (www.innovartis.co.uk) to manage our databases build and change process. It's probably the best development product that I ever bought. Super highly recommended.

For logical and physical database design work we typically use Visio and then generate the initial DDL script from there. Works fairly nice and is included with VS Enterprise.

For our legacy stored procedures we either use the SQL Server Tools or database projects in VS (or the fancy Server Explore in VS2005).

Stefan