Skip to content
← SQL Compare

How can we improve SQL Compare?

SQL Compare

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Ignore final semicolons when comparing stored procedures

As in title

137 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Anonymous shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Facts Rule commented  ·   ·  Report

    This is very helpful to have in the product! Surprised that after so many years this is still not implemented.

  • AM commented  ·   ·  Report

    Agree to all the comments here. Will be a good addition to the tool.

  • MG commented  ·   ·  Report

    It's a big time waster when comparing databases with large number of objects.

  • Chris commented  ·   ·  Report

    Our application uses PowerShell to rebuild our local database however Invoke-SqlCmd adds a semicolon to the end of each SP. This adds a lot of noise to SQL Compare when comparing Local to an environment.

    It would be great if we had an option to ignore the final semicolon before the GO to reduce the noise in compares!

  • Martins Lieknins commented  ·   ·  Report

    Impossible to compare 2 databases if one of them build with ending semicolon in each stored procedure. Option must have already 2 years ago!

  • Anonymous commented  ·   ·  Report

    Big fan of Redgate products and utterly shocked this is not even an option.

  • Anonymous commented  ·   ·  Report

    I really like SQL Compare but was horrified to find out this wasn't even an option. Please add ASAP.

  • Paul DB commented  ·   ·  Report

    1004 different objects between dev and test server with the only difference in each being the final extra semicolon. Argh! We need this feature!

  • Rob commented  ·   ·  Report

    Agree. New SQL t-sql standards will require semicolons at the end of each line. This change will allow us to see material changes between the old and new versions of the stored procedures.