Skip to content
← SQL Compare

How can we improve SQL Compare?

SQL Compare

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Make SQL Compare Three-part identifiers aware and filterable

Not always a deployed database has the same name of the source database due to customers' naming conventions. So it'd be great if SQL Compare will be three-part identifiers aware, so that if you compare the same table from different named databases as following:

SELECT *
FROM MyDatabaseA.MyTable

SELECT *
FROM MyDatabaseB.MyTable

SQL Compare will not show them as different if you want a three-part identifiers insensitive comparison.

18 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…)
Luca Zavarella 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
  • Evan King commented  ·   ·  Report

    As others have stated, this would be extremely useful when comparing dev with production versions of queries. We also have many that use fully qualified names for tables and they are constantly coming up as differences.

  • William Strachan commented  ·   ·  Report

    The issue I have is when we have multiple environments on the same SQL instance so we then have an environment suffix on each database name. This in itself isn't an issue as long as you only have one database per environment but this is rarely the case.
    With multiple databases per environment we will have cross-database queries and its this scenario that causes us issues as this is when we need 3-part names.