Comments
Sort by recent activity
My work around is to Shift+Click the selection boxes of the items that you wish to work with. The rows turn yellow. This will deselect the none yellow rows. The limitation is that the selected rows have to be continuous. Ctrl+Click doesn't seem to work like other grids. / comments
My work around is to Shift+Click the selection boxes of the items that you wish to work with. The rows turn yellow. This will deselect the none yellow rows. The limitation is that the selected rows...
Any resolution to this? I am having the same issue since upgrading to 3.1.3.26? / comments
Any resolution to this? I am having the same issue since upgrading to 3.1.3.26?
We currently put production definition of the synonyms in SVN source control and have a separate script that we run on dev and test machines after updating the dev and test databases from SVN. This way we do not accidentally promote dev or test synonym definitions into production. This process can cause issues if a developer by accident checks in the development version of the synonym by accident if the checkmark is not deselected during the checkin process to SVN. This will not get caught in test environment since the test environment uses the same definition as the dev environment. Only when the script is promoted to production will the problems appear. So we have to double check our synonyms on production servers and in SVN to make sure nobody checked in the wrong definition into SVN. This also forces us to continue to put together update script files to give to our DBA's to update the prod database. DBAs do not conern themselves with what is in the script. They just apply them. If the script breaks, then the test process is improved to make sure that does not happen again. In this case the test process must include the check of synonym definitions in source control. Which is not what the test team should be doing.
So, I was hoping for the SQL Source Control to provide mechanism where different synonym definitions can be assigned to the same object and extract the appropriate one depending on the target environment. Maybe there is a better solution. Possibly through CI (continuous integration). We currently do not have CI setup for our database changes, but it is on the wish list [image] . / comments
We currently put production definition of the synonyms in SVN source control and have a separate script that we run on dev and test machines after updating the dev and test databases from SVN. This...
Thanks for your input David.
I added the suggestion to the uservoice forum. http://redgate.uservoice.com/forums/390 ... ?ref=title
My thinking was to have the source control plug-in somehow provide a mechanism to select a different object script based on target server, and manage the underlying source code for each defintion seamlessly. Maybe this is better addressed in a CI type of environment where other tools provide this functionality. I am not sure at this time.
In the meantime I will look at the new Migration Scripts feature of Source Control and see if that provides a satisfactory solution. / comments
Thanks for your input David.
I added the suggestion to the uservoice forum.http://redgate.uservoice.com/forums/390 ... ?ref=title
My thinking was to have the source control plug-in somehow provide ...
I am not clear on the variable substitution part. Does Source Control have a variable substitution feature? Or are you suggeting to assign the four part synonym definition to a variable inside a stored procedure? A working example would help. Thank you. / comments
I am not clear on the variable substitution part. Does Source Control have a variable substitution feature? Or are you suggeting to assign the four part synonym definition to a variable inside a st...