Post reply

A way for the team to keep track of changes made

  • April 30, 2025 at 2:01 pm

    #4586006

    Is there a best practice way for the team to keep track of changes made to views, procs, and tables in SQL?

    Currently, there are 5 of us on the team making changes. I want to look at a board, spreadsheet, or something to know that TeamPerson1 made a change to a View I created, or TeamPerson2 added indexes to a table, or changed a stored procedure. I keep an Excel spreadsheet of all my changes, but wondered if there is something any of you have used to help team members to keep us from stepping on each other's code.

    Any ideas? What do you use?

    Thanks,

    JP

  • April 30, 2025 at 2:06 pm

    #4586017

    There certainly is, and it's called Source Control. You may have heard of 'Git' – that is one of the most popular source control tools in use right now.

    Take a read here for an intro:

    https://www.sqlservercentral.com/steps/stairway-to-database-source-control-level-1-setting-up-for-database-source-control

  • April 30, 2025 at 3:04 pm

    #4586044

    Thanks Phil. This is great information.

    JP

  • May 1, 2025 at 12:38 pm

    #4586538

    Do a search for "Database DevOps" because you're going to want more than just source control, although, as Phil points out, that's the starting point for all of it. I've got a bunch of presentations on this topic posted in Youtube in various channels. Some are specific to my company, Redgate Software, and our tools, but most of them are relatively generic and focused on how-to & why of this kind of management.

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

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