[SA 9.0.176] Upgrade broke target preferences

[SA 9.0.176] Upgrade broke target preferences

This is for SSMS, it was NEVER set to Azure, it was set to SQL Server 2008, and I had a custom formatting style it reset to the default style. The only thing it didn't change was my snippet preference.

Likewise for the SQL Editor target (and many others).

The setup saved a backup copy of your previous configuration file in %APPDATA%\Roaming\SQL Assistant\9.0 folder. The file should have today's date suffix in its name. Would you please email that file to support so that we can retrace your upgrade steps and check why it changed?

Thank you very much for the file. This configuration file already has Azure and the rest saved in it before the upgrade. I was told that this kind of issue could have occurred when upgrading from the beta version. Is that possible that the actual change occurred earlier, I mean when you upgraded from the beta version, and not when you installed 9.0.176 build?

	SysOp wrote:
	Thank you very much for the file. This configuration file already has Azure and the rest saved in it before the upgrade. I was told that this kind of issue could have occurred when upgrading from the beta version. Is that possible that the actual change occurred earlier, I mean when you upgraded from the beta version, and not when you installed 9.0.176 build?

I'm pretty sure it was set to SQL server 2008. If you see my discussion on not allowing unavailable functions thread I discuss what my assistance properties were set to. Also it reset my snippet collection selection to the default as well. I KNOW that for sure was set right because I had that header disabled in my formatting rules that is enabled in the default rules. (The one that adds a comment to the top of your editor window when you format your code)

Left = Sqlassist.sas (from today) and Right = the one I emailed.

This little wedge is for the SQL Editor.

I am unsure what the SQLRef actually references, but the assist code was set to SQL Server, not Azure? Unless the SQLRef has something to do with that?

Either way it's super weird, because I have zero reason to have any of that set as Azure. No Azure instances to play with.

Then this is from my upgrade at 10-17 (right) to 10-27 (left)

So yeah. It looks like a previous upgrade boinked it?

Thank you very much for the details. Developers say that the changes or corruption occurred before the upgrade, because the file you provided was backed up by the setup before installing new version. It's just that apparently after the SQL Assistant restart after upgrade the issue became visible. What we don't know at this time and that 's is the critical piece, is how to reproduce it. If you or anyone else know how to reproduce that on demand, please describe the steps. We 're eager to develop a fix to resolve it, and we will treat it as a high priority issue.

Interesting. That's something I've met a few times in the past but it never hit the threshold to get it reported. I'm frequently git-ting the .sas file, making it compulsorily right before and after applying updates, and fixed small scale issues like this one with a simple compare and merge. I don't recall seeing it during the beta and since, though.