Developement Design

  • I am kind of out of the box on this new job that I have. Currently This has been a mostly offshore project that has now come full circle and is back.

    This is a completely development and testing process. We are not going live till next year. Right now the process goes like this:

    We have an install for the database scripts. This folder has a bunch of scripts. The commands are separated between object creation, PKs, FKs, SPs, data scripts. Then there are versioned scripts for people that do not want to blow away there db while testing. So it catches them up with the current changes we have done.

    this process works but when we make big changes it takes a lot of time. Any advise how to design this more proficiently?

  • Personally, I'd suggest using a tool that works well with scripts and source control. The three that come to mind are DBGhost, in which I have no experience, Red Gate SQL Compare, great tool for comparisons & deployments, and Microsofts Visual Studio Team System Database Edition, incredibly expense but worth every penny.

    "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

  • I thought the same thing. I can use SQL compare and have a bit. That still does not take care of the real issue. What is the best practice approach to R&D when it comes to developing a new application from the DB end. It feels like we are trying to keep everyone happy with versioning while still trying to maintain architecture. Between documentation, and versioning it makes it hard to do anything else of value. Really what I am asking is how someone would handle this environment differently.

  • Well, I'd say you have to reign it in. First, you need to get the core code into source control. After that, you can start working to label builds so that you can recreate databases or upgrade databases based on the version that they're on. You need to manage the database more or less like code. If you manage it all through source control, then you shouldn't have to manage a ton of change scripts, but instead work through some method that allows you to update databases as needed. We're using Visual Studio Database Edition for this now. It's a lot of work, but not as much as what you're going through.

    "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

  • We are currently using TFS also for source control. When I look at the SQL2K5 templates I see all the stuff I am used to seeing for check in's but I have only used this when we are dealing with one server where you create it here, check it in, and then deploy it. The way they have it working now is they made a program that they run on there local machine that allows them to create there own DB, add test data and that is about it. So it is not really a promotion as much as test and deploy to individuals. That install is in a folder with all the .dat files and the .sql files which the program launches. Is there a way I could make VS db work like this or something similar on there local machines

  • Not really unless you get the Team System Database Edition.

    "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

  • Grant Fritchey (9/30/2008)


    Not really unless you get the Team System Database Edition.

    Which is now available to any software assurance customers who have Team System for developers (and vis versa)

    http://www.microsoft.com/presspass/press/2008/sep08/09-29VS10PR.mspx

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • That's great news. Thanks for sharing.

    "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 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply