September 3, 2008 at 11:06 am
Generally speaking, I have always used SSMS (or the equivalent in some other version) for development. The integration of SourceSafe was a real boon to me, and most of our production databases have become SSMS solutions.
Recently we inherited an application, with database, where the database development was done in Studio Pro, resulting in .dbp projects. As far as I can tell, they are incompatible with SSMS solutions. Am I missing something in that?
For the bigger question, where SHOULD the development take place?
------------
Buy the ticket, take the ride. -- Hunter S. Thompson
September 3, 2008 at 11:53 am
Those files are not compatible with Management Studio.
As to where... it really depends on your shop and the processes there. For example, we use Visual Studio Team System Database Edition for our database design, development and deployments. It integrates very well with source control, validates database scripts in a sandbox as you develop them, provides mechanisms for deployment to multiple servers... Except for some shortcomings in incremental deployment automation, it does just about everything we need. Unfortunately, it's pretty expensive, so some shops might not be able to take advantage of it.
I know others that are using a combination of Management Studio and Red Gate SQL Compare. I used to do it that way myself. It really depends on your processes, how much money you're spending on tools, how much automation you need, etc., to decide on where precisely to do development. I wouldn't say any answer is wrong outright (unless it doesn't include some kind of integration with source control because that's just foolish).
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply