changing stored procedures

arzewskiarzewski Posts: 2
edited September 14, 2010 12:24PM in SQL Source Control Previous Versions
is there a problem in source control for stored procedures if the developers in a team-based environment use DROP PROC and then CREATE PROC to make their changes in a stored procedure instead of using ALTER PROC ?

I am wondering if the source control service is smart enough to do a text difference and detect exactly which part of a procedure text was changed, and display that to the developer when he is ready to commit the changes and write a comment in the comment textfield.
· Share on Twitter

Comments

  • David AtkinsonDavid Atkinson Posts: 1,462 Rose Gold 2
    SQL Source Control will do a textual comparison of the stored procedure as it is stored in the database. This stores all the text (including comments) in the batch that contained the stored procedure when it was created or altered, and will therefore exclude the DROP from consideration.

    So SQL Source Control should behave as you expect.

    Why not try it out for youself?

    David Atkinson
    Product Manager
    Red Gate Software
    David Atkinson
    Product Manager
    Redgate Software
    · Share on Twitter
Sign In or Register to comment.