Activity overview
Latest activity by dannett
The SQL package script is handed off to our own package/deploy process which uncomments the :setvar lines and set the values for a client. Obviously, at the moments it all falls down as there is no DatabaseName variable. I can add it back into the script myself so customers can run it themselves in Management Studio but I just wondered if it was an oversight or not. You may want to update your documentation as well e.g. https://documentation.red-gate.com/display/SCA3/Deploy+using+SQL+Server+Management+Studio to mention that once uncommented, the user needs to add the missing variable back in Thanks / comments
The SQL package script is handed off to our own package/deploy process which uncomments the :setvar lines and set the values for a client. Obviously, at the moments it all falls down as there is no...
The SQL package script is handed off to our own package/deploy process which uncomments the :setvar lines and set the values for a client. Obviously, at the moments it all falls down as there is no DatabaseName variable. I can add it back into the script myself so customers can run it themselves in Management Studio but I just wondered if it was an oversight or not. You may want to update your documentation as well e.g. https://documentation.red-gate.com/display/SCA3/Deploy+using+SQL+Server+Management+Studio to mention that once uncommented, the user needs to add the missing variable back in Thanks / comments
The SQL package script is handed off to our own package/deploy process which uncomments the :setvar lines and set the values for a client. Obviously, at the moments it all falls down as there is no...
The SQL package script is handed off to our own package/deploy process which uncomments the :setvar lines and set the values for a client. Obviously, at the moments it all falls down as there is no DatabaseName variable. I can add it back into the script myself so customers can run it themselves in Management Studio but I just wondered if it was an oversight or not. You may want to update your documentation as well e.g. https://documentation.red-gate.com/display/SCA3/Deploy+using+SQL+Server+Management+Studio to mention that once uncommented, the user has to add the missing variable back in. Many thanks / comments
The SQL package script is handed off to our own package/deploy process which uncomments the :setvar lines and set the values for a client. Obviously, at the moments it all falls down as there is no...
SQL Change Automation version: 3.3.19211.9712 issues
I was running version 3.3.19204.9562 and the generated SQL file was ok and had the following builtin variables set:----==============================================================================...
Also, the project in question was originally created in ReadyRoll and we have noticed in previous updates of SCA it would try to remove obsolete project properties. I wonder if it is still trying to do something like this / comments
Also, the project in question was originally created in ReadyRoll and we have noticed in previous updates of SCA it would try to remove obsolete project properties. I wonder if it is still trying t...
It is as soon as I load the solution - I'm running 15.9.7 / comments
It is as soon as I load the solution - I'm running 15.9.7
SCA always checks out project file from TFS
Having updated SQL Change Automation from 3.0.18341 to 3.0.19059, every time I load up the solution, the .sqlproj file is checked out from TFS but no changes are made to the file. Can this behaviou...