User profile for kalo

Thanks for the response. Is the below the kind of test you did? 1. Comparison shows some objects 2. I select synonym only 3. Dialog tells me i ought to commit the schema 4. I un-check the commit box but decide to cancel out to select other items 5. I select another item (not the schema) and commit again 6. The Dialog pops up again to warn about schema but reverts back to being checked : which means you have to be vigilant and observe this revert back as to hit continue would commit an unintended item*. [image] I'm pretty sure it didn't use to do this but remembered your last selection (checked/unchecked) as your preference (as the behaviour is in SQL Compare where the commit checkbox defaults to what you last had it as). I could be talking out of my hat if you went through similar steps on your older version and it has always defaulted back to checked. But when i get chance i will install my original sql toolbelt version and give it a test. * in this example the schema ought to be checked in, but had to come up with example on an existing db i had access to / comments

Thanks for the response.Is the below the kind of test you did? 1. Comparison shows some objects2. I select synonym only3. Dialog tells me i ought to commit the schema4. I un-check the commit box bu...

0 votes

Hi, I am on 6.2.1 at the moment (unable to update to 6.2.2 whilst i wait on some clarification on one of the release notes[SC-10177]) regards. / comments

Hi, I am on 6.2.1 at the moment (unable to update to 6.2.2 whilst i wait on some clarification on one of the release notes[SC-10177]) regards.

0 votes

Indeed, this is just source control not deployment so why does it care that much. Once acknowledged can't it remember? But yeah, i've just 'got used to it' really. / comments

Indeed, this is just source control not deployment so why does it care that much. Once acknowledged can't it remember? But yeah, i've just 'got used to it' really.

0 votes

Hi Sergio, it's not just when I switch databases that an auto-refresh happens : that refresh i understand because you have changed the context . What thwarts me is that if i switch query windows even within the same database i'm looking at in source-control that it still makes an unnecessary auto-refresh. i have however found that if i move the source-control query out into it's own tab-group or out into it's own window then i can navigate the database objects in a different tab-group without provoking the source-control results to refresh. Thanks, i will post a suggestion when i get chance. / comments

Hi Sergio,it's not just when I switch databases that an auto-refresh happens : that refresh i understand because you have changed the context . What thwarts me is that if i switch query windows eve...

0 votes

Thanks for response Sergio. I maybe mis-remembering but i thought it did use to behave this way on a previous version and only auto-refreshed if you switched databases (so refresh necessary), and that's why there is an explicit 'Refresh' hyperlink under the Commit button. Either way is there no demand for this behaviour to be in source-control application? (ie, can i vote somewhere?) / comments

Thanks for response Sergio.I maybe mis-remembering but i thought it did use to behave this way on a previous version and only auto-refreshed if you switched databases (so refresh necessary), and th...

0 votes

Thanks for getting back to me on that - I will run the update when i get chance. / comments

Thanks for getting back to me on that - I will run the update when i get chance.

0 votes

Thanks Rob, Yes, as writing my response I thought you might point out the recompare setting but that's a case of remembering to keep toggling it on and off between the different scenarios i'm using the compare tool for, so it's easier to copy and paste, but what i do know is just open up the wizard to the point of showing the script and copy and paste from there so if the diff viewer has to stay as it is going forward then i can still do what i want (just with an extra couple of clicks) Yes, i would say the single change for me that could happen in SQL Compare - which would have me going out for drinks to celebrate - would be making that dependencies step on the wizard much more sophisticated. At the very least being able to individually select. it is useful though that you can do a comparison of those objects and decide if you need to include, so at the moment i use that to review copy and paste the object names i want to include into notepad, then cancel out of the wizard and individually paste in the object names back into the search box (having to remove the schema and squared brackets unfortunately) and select them one by one manually. So feels that process could be done for me by the tool. Thanks for taking the time to respond and if you confirm whether the source-control behaviour has changed that would be great. / comments

Thanks Rob,Yes, as writing my response I thought you might point out the recompare setting but that's a case of remembering to keep toggling it on and off between the different scenarios i'm using ...

0 votes

Hi Rob, I do use it a lot which is why it feels like one of the recent updates has accidentally changed how it behaves : I might be entirely wrong on that, maybe it's always behaved like that. However the diff pane in SQL Source Control doesn't copy the skipped lines so what gets pasted is the actual source code. My immediate concern is that the release notes for the 6.2.2 update Source Control is telling me is available references SC-10177: Copying text from the diff viewer now preserves empty lines when the "Ignore whitespace" option is selected : as SC-10177 is the fix that went into SQL Compare to fix that issue, i'm worried that if i update then the Source Control behaviour will change from what it does now. I could update to find out i guess, but then I lose the behavour i want. Now why do I copy from the diff pane so much? I manage a number of 'mirror' databases which different versions of our dotnet code are pointing at - so i am frequently syncing these, now when i am only having to deploy one object (or want to deploy me objects one by one) then rather than having to go through the few steps of the deployment wizard and then wait for the application to follow up with the recalculation (Which can take a while on my big database), it is easier for me to just copy the diff pane script (from compare or source control) and change the CREATE to an ALTER Secondly, if i do decide to do a deployment through SQL Compare, i find that the Commit dependencies will pop up and detect various objects that i don't want to deploy in the batch, like dependencies up the chain rather than down or objects which are of one type but perhaps a synonym on my mirror database (some i might want to deploy, but the wizard allows you only to select all or nothing, so i have to cancel out and go back to the differences screen to individually select the ones i want) / comments

Hi Rob,I do use it a lot which is why it feels like one of the recent updates has accidentally changed how it behaves : I might be entirely wrong on that, maybe it's always behaved like that.Howeve...

0 votes

Nice - thanks, that's working for me. / comments

Nice - thanks, that's working for me.

0 votes

Hi Rob, It does seem to be the case now that it not only copies the blank lines which are in the object but also the 'blank' lines where it is comparing against the other source so that when you paste the code from the window you don't actually paste the original code but the compared code It used to be the case (i think) that if you select all and copy from the comparison window it just copied the code from whichever source you had chosen (so the same code as what would be deployed if you selected just that single object and stepped through the deployment wizard). Or indeed behaves the same way the comparison panes work in SQL Source Control - where the copy paste just picks up the source code : if i update Source Control to the new frequent update that includes SC-10177 will it break this behaviour in this app too? / comments

Hi Rob, It does seem to be the case now that it not only copies the blank lines which are in the object but also the 'blank' lines where it is comparing against the other source so that when you pa...

0 votes

How can we help you today?

kalo

Comments