Post reply

Any good process for source code control in SQL Server 2000

  • February 6, 2007 at 1:11 am

    #92964

    1. Good day. I have a problem of source control my SP/Triggers & function in sql server 2000.

    2. My company often have problem updating our development database to our client due to the

    following problem. As expert in this area, we seek your advise/guidance on this issue.

     

    a. A few of the developer might just send some scripts or udates to our client without updating our source control repository (Perforce)

     

    b. If any of us are at our client side, they might just fix or patch some stored procedures. They forget to update our main office source control repository.

     

    c. Some of the bugs that client reported, we need to have the exact data in the database to simulate.

     

    From the above issues. We often have problem deploying our new update to our client. Our central source control repository

    might be outdated and there is no way to know which script are new or outdated.

     

    Is there any good process or method that you can recommand to solve my company database source control issues

  • February 6, 2007 at 9:36 am

    #688088

    http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops2.mspx

    2a. You must make them use Perforce, otherwise, fire them.  But really,  a responsible dba or senior developer should be putting changes in.  They should check update/rollback scripts into Perforce and the DBA/Senior Dev should run them. 

    2b.  See 2a.

    2c.  Have them send you a backup of their database and restore a test machine at your building.  Perhaps I am misunderstanding your issue here?  The answer seems too simple .

     

Viewing 2 posts - 1 through 1 (of 1 total)

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