How can we help you today? How can we help you today?
james.strath
Hi Christian,  Thanks for your response. Because of the danger of the behaviour i descibed, - I have to be vigilant when first loading a new compare and manually unselect everything from the top. Therefore my question was why can't I set it to default like this all the time. But I suppose it would be difficult for the software to properly distinguish between a new compare and a repeated compare against a different target? The dangerous behavour I am witnessing from time to time however, is that reloading the compare (either refresh or switching one of the source or target) is auto-selecting items. So lets say I am promoting a local change to my dev environment and immediately want to promote that to test and then UAT in quick succession. I might hope to select the 1 single item in my first compare local|dev and promote and then when I reload my compare to either local|test or dev|test it should either, in my view, reset to all unselected for safety or try and reload the equivalent last selection. What it should not do is reload the equivalent last selection and then decide to load some other items. Which if not noticing means that a press of deploy results in deploying more than 1 item (in the above example). Your reply suggests that the behaviour I encounter is not by design then? In your example you refreshed the same database - what happens if you create/amend objects between the refreshes - do new/amended objects get loaded auto-selected? Or when you switch your target to the same database but on a different server does it select only the same named objects as your original selection? As you can probably imagine if I encounter this again I will only be able to screenshot the second snapshot and you would have to take my word for it doing it automatically. Otherwise, i will try and find some free time out of working hours to see if i can engineer example steps to replicate the issue. regards, James   / comments
Hi Christian, Thanks for your response.Because of the danger of the behaviour i descibed, - I have to be vigilant when first loading a new compare and manually unselect everything from the top. The...
0 votes
I should have mentioned i'd already tried that option but turning that option off means you get countless differences that i do want to ignore and renders that option pointless. regards, James / comments
I should have mentioned i'd already tried that option but turning that option off means you get countless differences that i do want to ignore and renders that option pointless.regards,James
0 votes
  RedGate.SQLCompare.UI.exe C:\Program Files (x86)\Red Gate\SQL Compare 15 15.4.10.27977+6a233340b701adde9321bff7be3c47314fc3b733 4.0.30319.0 False Thanks Christian- apologies, I should know by now that it would be useful to include these each time on a ticket! - Also that would prompt me to do what i normally do when i encounter a possible issue and update the software to see if it's been resolved already.  I will probably update later today   i have a simple proc on both databases [image] i make a trivial change to force a difference [image] I go to deploy and the script include my intended change but as a consequence changes the first line [image] so following the deployment it shows as no difference between the two databases  [image] but an unintended change has occurred - which means i have to correct it manually afterwards (which is tedious when it surprises you and amends multiple items) and it shows up as every object different when using a different compare tool (Eg devops)   [image] script for the simple proc to be precisely like mine - but it happens on any proc, object you write CREATE OR ALTER PROC [dbo].[proc] AS ;BEGIN ;SET NOCOUNT ON ;BEGIN TRY ;DECLARE @this_proc_name sysname = (CONCAT((QUOTENAME(OBJECT_SCHEMA_NAME(@@PROCID))), (CHAR(46)), (QUOTENAME(OBJECT_NAME(@@PROCID)))))     ;DECLARE @RC INT = (0)     ;RAISERROR(@this_proc_name, 10, 0)WITH NOWAIT ;END_OF_QUERY:     ;RETURN(@RC) END TRY BEGIN CATCH     ;DECLARE @ErrorMessage NVARCHAR(MAX) = (ERROR_MESSAGE())     ;RAISERROR(@ErrorMessage, 16, -1)     ;RETURN(ERROR_NUMBER()) END CATCH END --of sp GO   / comments
 RedGate.SQLCompare.UI.exeC:\Program Files (x86)\Red Gate\SQL Compare 1515.4.10.27977+6a233340b701adde9321bff7be3c47314fc3b7334.0.30319.0FalseThanks Christian- apologies, I should know by now that ...
Edited 0 votes