Comments
Sort by recent activity
robrich said:
Just saying, I've been playing with this, and it is incredibly cool.
Thanks for your feedback Robrich! I'll be sure to let the Development Teams know. Is there anything in particular that you are finding works really well? Or anything that could be improved? / comments
robrich said:
Just saying, I've been playing with this, and it is incredibly cool.
Thanks for your feedback Robrich!I'll be sure to let the Development Teams know. Is there anything in parti...
Hey @bernieconway We now recommend customers try our Pre/Post scripts approach for managing migrations which we recently released - its available on our frequent updates channel of source control ( you just need to opt in to frequent updates) Take a look here for more info: - https://documentation.red-gate.com/soc6/common-tasks/working-with-pre-post-deployment-scripts Thanks / comments
Hey @bernieconway We now recommend customers try our Pre/Post scripts approach for managing migrations which we recently released - its available on our frequent updates channel of source control (...
Hi @AlexYates I and the development teams would love to hear how you get on with using Pre/Post scripts. If you have any feedback, get in touch with me so we can review how well this has been received. Thank You! / comments
Hi @AlexYates I and the development teams would love to hear how you get on with using Pre/Post scripts. If you have any feedback, get in touch with me so we can review how well this has been recei...
Hi Sean, With regards to the issue around the manually modified script and trying to deploy but seeing the message:- "**These migrations have not yet been deployed. Start your solution to execute these database changes (or alternately click the Deploy button in the ReadyRoll tool-window)." This issue was resolved by upgrading the ReadyRoll.MSBuild package to 3.0+ by following these steps in the documentation. / comments
Hi Sean,With regards to the issue around the manually modified script and trying to deploy but seeing the message:-"**These migrations have not yet been deployed. Start your solution to execute the...
Hi berkshireseany, Firstly, thank you for upgrading to SQL Change Automation so quickly! Looking at the issue you've detailed the behaivour you've mentioned isn't the normal experience a user upgrading to SQL Change Automation should encounter. VS 2015 users will not be forced to upgrade. VS 2017 users do have auto update enabled by default so would get SQL Change Automation automatically unless this is disabled in their options. I understand our support team are in contact with you on this issue and my colleagues are looking at the problem as a priority. Please rest assured that as soon as a fix is available we will get back to you immediately. Thanks once again for upgrading and apologies you've suffered this issue. / comments
Hi berkshireseany,Firstly, thank you for upgrading to SQL Change Automation so quickly!Looking at the issue you've detailed the behaivour you've mentioned isn't the normal experience a user upgradi...
Hi berkshireseany, Firstly, thank you for upgrading to SQL Change Automation so quickly! Looking at the issue you've detailed the behaivour you've mentioned isn't the normal experience a user upgrading to SQL Change Automation should encounter. VS 2015 users will not be forced to upgrade. VS 2017 users do have auto update enabled by default so would get SQL Change Automation automatically unless this is disabled in their options. I understand our support team are in contact with you on this issue and my colleagues are looking at the problem as a priority. Please rest assured that as soon as a fix is available we will get back to you immediately. Thanks once again for upgrading and apologies you've suffered this issue. / comments
Hi berkshireseany,Firstly, thank you for upgrading to SQL Change Automation so quickly!Looking at the issue you've detailed the behaivour you've mentioned isn't the normal experience a user upgradi...
Hi Chris,
You'll need to make sure you have EXEC permission for the following:-
the function SQLSourceControl.GetLockedObjects, to retrieve locked objects
the function SQLSourceControl.IsObjectLocked, to check if objects are locked
the stored procedure SQLSourceControl.LockObject, to lock objects
the stored procedure SQLSourceControl.UnlockObject, to unlock objects
If you don't then ask your DBA to set this up for you and it should resolve the problem.
Thanks / comments
Hi Chris,
You'll need to make sure you have EXEC permission for the following:-
the function SQLSourceControl.GetLockedObjects, to retrieve locked objects
the function SQLSourceControl.IsObjectLoc...
Hi Chris,
Thanks for getting in touch. If you are trying to figure out what permissions are required these are shown below:- (These permissions are for running the actual script)
To run the setup script, you need these database privileges:
CREATE USER
CREATE ROLE
GRANT ANY PRIVILEGE
CREATE ANY TABLE
CREATE ANY PROCEDURE
You don't need the privileges to lock and unlock objects.
If the DBA is still seeing the info about setting up locking can you check that he has run the script successfully first. Please let me know if this isn't successful.
Thanks / comments
Hi Chris,
Thanks for getting in touch. If you are trying to figure out what permissions are required these are shown below:- (These permissions are for running the actual script)
To run the setup s...
Thanks Pete!
Pete H wrote: »
Looking good Ben! I removed the _ from your name for you [image]
/ comments
Thanks Pete!
Pete H wrote: »
Looking good Ben! I removed the _ from your name for you
Test / comments
Test