How can we help you today? How can we help you today?
james.strath
Activity overview Badges (0) Posts (3) Comments (9)

Comments

Sort by recent activity
As an example on a tangent, when i'm creating a script for a database install i will compare my source database to the empty model database and compare auto-selects in general all of the items. But as i go thru each of my source databases i will move to one where it neglects to select all of the items. When i reorder the list to bring the unselected items to the top to view them i'm left wondering what's so [un]special about these that they have not been auto-selected? [image] and on this database it seems to know that i will want to exclude these 2 synonyms whereas on the above example i don't want to exclude that list it has decided not to select [image]     / comments
  1. Community
  2. SQL Compare
  3. What is the auto check logic and how do i turn it off?
As an example on a tangent, when i'm creating a script for a database install i will compare my source database to the empty model database and compare auto-selects in general all of the items. But...
Edited 0 votes
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
  1. Community
  2. SQL Compare
  3. What is the auto check logic and how do i turn it off?
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
Sorry Christian , no i don't recall when this behaviour started occurring. / comments
  1. Community
  2. SQL Compare
  3. Deploy making undesired change to code where there wasn't a difference
Sorry Christian , no i don't recall when this behaviour started occurring.
0 votes
Looking at views at the moment and it appears that when you right-click and script out an existing view (CREATE, ALTER, DROP AND CREATE, CREATE OR ALTER) where the object has been created with the object type (VIEW) on a new line then the scripting inserts extra white space that's not needed and therefore adjusts the exact script of what it was before: [image] The whitespace inserted is inconsistent between the script methods: [image] [image] Any reason why they can't all just have no or one whitespace in each - or is this an SSMS issue rather than redgate scripting?   / comments
  1. Community
  2. SQL Compare
  3. Deploy making undesired change to code where there wasn't a difference
Looking at views at the moment and it appears that when you right-click and script out an existing view (CREATE, ALTER, DROP AND CREATE, CREATE OR ALTER) where the object has been created with the ...
Edited 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
  1. Community
  2. SQL Compare
  3. Deploy making undesired change to code where there wasn't a difference
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
Though i just had it happen on a normal ALTER so I have noticed this One whitespace after my ALTER keyword (renders as CREATE in redgate comparison) things are ok in the generated script [image] No whitespace after the opening keyword things are ok in the generated script [image]   But two whitespaces after the opening keyword then the generated script outputs on one line [image] Three whitespaces after the opening keyword then the generated script outputs on one line [image]   Tab after the opening keyword and things are ok [image]   Even though i've now determined the workaround it will be a bit tedious to police myself and others in code-review to prevent it corrupting the environments. the reason I make this change is that i have litany of code that has ended up similar to this; [image]   where there are varying big gaps between the keywords - i don't know exactly where these have come from (SSMS modifications or redgate compare deployments) but in order to stop them from creeping in - i try and enforce a consistent syntax - which the redgate whitespace bug is therefore undermining. Hope above helps resolve. James     / comments
  1. Community
  2. SQL Compare
  3. Deploy making undesired change to code where there wasn't a difference
Though i just had it happen on a normal ALTER so I have noticed thisOne whitespace after my ALTER keyword (renders as CREATE in redgate comparison) things are ok in the generated scriptNo whitespac...
Edited 0 votes
Hi Christian,  In your own test, did you take my proc script as is? Because i think the issue is when the script has CREATE OR ALTER PROC in it, whereas if the script is a CREATE PROC or an ALTER PROC it works Regards, James / comments
  1. Community
  2. SQL Compare
  3. Deploy making undesired change to code where there wasn't a difference
Hi Christian, In your own test, did you take my proc script as is? Because i think the issue is when the script has CREATE OR ALTER PROC in it, whereas if the script is a CREATE PROC or an ALTER PR...
0 votes
the software is saying there aren't any updates to apply as i'm on latest version. [image] RedGate.SQLCompare.UI.exe C:\Program Files (x86)\Red Gate\SQL Compare 15 15.4.13.28096+ebd604dab73334a415f1205f61fa1334ccdf8910 4.0.30319.0 False my current depoloyment showing below where in the screen behind it shows the comparison with PROC keyword on second line but the script window then shows the PROC on first line [image] if i scroll down the script all other procedures have PROC keyword as first word of second line -  but this first entry shows it differently for some reason     / comments
  1. Community
  2. SQL Compare
  3. Deploy making undesired change to code where there wasn't a difference
the software is saying there aren't any updates to apply as i'm on latest version.RedGate.SQLCompare.UI.exeC:\Program Files (x86)\Red Gate\SQL Compare 1515.4.13.28096+ebd604dab73334a415f1205f61fa13...
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
  1. Community
  2. SQL Compare
  3. Deploy making undesired change to code where there wasn't a difference
 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
Total activity
15
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
3