Comments
Sort by recent activity
So, if I understand correctly, you are saying that since SQL Compare does not properly compare trigger SQL, I should tell it to not synchronize the very SQL that I'm trying to reconcile--because it compares the trigger SQL incorrectly in the first place?
Why does the app even try to compare triggers if it cannot do it properly?
Perhaps the product name should be changed to "All But Trigger SQL Compare" / comments
So, if I understand correctly, you are saying that since SQL Compare does not properly compare trigger SQL, I should tell it to not synchronize the very SQL that I'm trying to reconcile--because it...
Thanks for the clarification, David. I was not understanding that before now. It does lessen the impact in cases where index order is the only "difference", but it still makes for work to factor it out in cases where there are other actual differences.
Cordially,
Lee / comments
Thanks for the clarification, David. I was not understanding that before now. It does lessen the impact in cases where index order is the only "difference", but it still makes for work to factor ...
I appreciate the reply, David, but I do not see any logic in calling it "expected functionality" in a tool that has the primary purpose of comparing databases.
I expect to only be shown differences--true difference, not false differences that result from so-called developer-expected functionality.
Bugs are not features, even if the developers expect them. This bug will result in two identical databases (with indexes established in varying orders) being deemed different, when they are not different in the real world.
Sincerely,
Lee / comments
I appreciate the reply, David, but I do not see any logic in calling it "expected functionality" in a tool that has the primary purpose of comparing databases.
I expect to only be shown differences...
Thanks, David. I keep running into this issue. It causes a lot of false positives for me. I look forward to a solution. [image]
, Lee / comments
Thanks, David. I keep running into this issue. It causes a lot of false positives for me. I look forward to a solution.
, Lee
It's been a month now. I took the time to prove the issue. The courtesy of a reply would be appreciated. / comments
It's been a month now. I took the time to prove the issue. The courtesy of a reply would be appreciated.
In the linked image, there is a constraint line that appears identically in both sides:
CREATE UNIQUE NONCLUSTERED INDEX [UX_BuildingName] ON [dbo].[ServiceLocations] ([LocationName]) [image] / comments
In the linked image, there is a constraint line that appears identically in both sides:
CREATE UNIQUE NONCLUSTERED INDEX [UX_BuildingName] ON [dbo].[ServiceLocations] ([LocationName])