Comments
Sort by recent activity
Just to keep this thread updated. The release of SQL Change Automation 4.0 has not resolved the issue. / comments
Just to keep this thread updated. The release of SQL Change Automation 4.0 has not resolved the issue.
Russell, I am doing more testing, but it's taking time. (I forgot) we have some automation scripts that install some extensions for Visual Studio after installing VS. I'm removing these one at a time to see if any of them are interfering. The problem I have is that these same extensions install on VS 2017, and I don't have the issue. Also, when you open the properties page, it "looks" like the properties try to load (it flashes), and then get blocked. I just don't get what that could be. Thanks, Greg / comments
Russell,I am doing more testing, but it's taking time. (I forgot) we have some automation scripts that install some extensions for Visual Studio after installing VS. I'm removing these one at a t...
Pete, Thank you. I'm glad you are finally able to reproduce. I can't find any way to prevent it. I even went so far as trying to install Visual Studio 2019 Enterprise on a clean machine (even though I don't have a license for it) to see if that had anything to do with it, but of course, it did not. Thanks Greg / comments
Pete,Thank you. I'm glad you are finally able to reproduce. I can't find any way to prevent it. I even went so far as trying to install Visual Studio 2019 Enterprise on a clean machine (even th...
Russell, I went through the hassle of re-installing Visual Studio 2017. Oddly enough, the settings appear properly in this version (using the same test project)... [image] / comments
Russell,I went through the hassle of re-installing Visual Studio 2017. Oddly enough, the settings appear properly in this version (using the same test project)...
Russell, To make sure that my system is not somehow the issue, I did a clean install of Visual Studio 16.2.2 and the Toolbox (SQL Change Automation only) on two other systems. Using the test project, the same issue occurs. Thanks, Greg / comments
Russell,To make sure that my system is not somehow the issue, I did a clean install of Visual Studio 16.2.2 and the Toolbox (SQL Change Automation only) on two other systems. Using the test projec...
Russell, Here is a nice big screen shot showing the issue and confirming the Visual Studio version is 16.2.2... [image] Thanks, Greg / comments
Russell,Here is a nice big screen shot showing the issue and confirming the Visual Studio version is 16.2.2...Thanks, Greg
Russell, I've attached a brand new project, and it has the same problem... no settings. I think this might be a problem in Visual Studio 2019. This is the first time I've needed to manipulate the settings since upgrading to VS 2019. I'm not entirely sure because I no longer have VS 2017 installed. I'm currently on VS 2019 16.2.1. On a side note, I'm getting REALLY tired of being prompted to update "SQL Change Automate Core". I read on your site (though I can't currently find it) that we should ignore these updates for "Core". I wish you guys would fix this. Thanks, Greg / comments
Russell,I've attached a brand new project, and it has the same problem... no settings. I think this might be a problem in Visual Studio 2019. This is the first time I've needed to manipulate the ...
Hi Sergio, It appears to be activated. It doesn't actually say "activated", but... [image] Here is the properties page of one of my projects. When you open it, it looks like the properties actually begin to load, but then don't, like something is blocking them. (Changing the Target platform makes no difference either). [image] Any suggestions would be appreciated. Thanks, Greg / comments
Hi Sergio,It appears to be activated. It doesn't actually say "activated", but...Here is the properties page of one of my projects. When you open it, it looks like the properties actually begin t...
Sergio, Yes, I am referring to <DeployChangesExecutionOrder> in the project file. Are we supposed to now manually edit the project file to manipulate this? Because I've tried that and it didn't work, probably because of the unique id associated to files in that list. To be clear, The project properties page has had all of its settings removed and replaced with the following message: "We recommend building and deploying SQL Change Automation projects using the SQL Change Automation PowerShell components. Please note that this is not available in SQL Change Automation Core Edition." Note, I do NOT have the core edition of the plugin installed. Thanks, Greg / comments
Sergio,Yes, I am referring to <DeployChangesExecutionOrder> in the project file. Are we supposed to now manually edit the project file to manipulate this? Because I've tried that and it didn't wo...
Kendra, Thank you for the answer... and for putting he answer at the beginning of your response! :upside down: I use snapshot isolation for queries that populate a ui grid from table(s) that get records added/edited at an extremely high rate. Without snapshot isolation, deadlocks are a frequent companion. I don't need to wait for that uncommitted data. I realize the impact to TempDb, and in fact, TempDb has it's own drive array, partitioned on SSD's. (However, I haven't quite figured out the best approach for an Azure database, in terms of configuration and cost). Anyway, it has saved my bacon before, and probably will again. I am a fan too. Thanks, Greg / comments
Kendra,Thank you for the answer... and for putting he answer at the beginning of your response! :upside down: I use snapshot isolation for queries that populate a ui grid from table(s) that get re...