Comments
Sort by recent activity
Hi @Kendra_Little Thanks for the reply... I am aware of SQL Compare and I use it often, and I actually almost used it for this deploy. Reason I didn't is because this change was adding a new DB role, and our users in each environment are quite different. I have users excluded from SQL Source Control, but when comparing in SQL Compare the users are still here. I know there's probably a way to ignore user permissions, but I only had a small window of time to make this production change plus I didn't want to 'test' this with a Prod deploy. I will research further how to exclude user permissions from SQL Compare as this should get me good for future deployments. Take care - Sam / comments
Hi @Kendra_Little Thanks for the reply... I am aware of SQL Compare and I use it often, and I actually almost used it for this deploy. Reason I didn't is because this change was adding a new DB ro...
Same here... I posted another question with details from the error on my side. / comments
Same here... I posted another question with details from the error on my side.
I'm getting the same thing. Will hold out a day or two to see if RG has an update, else I'll need to go back to 18.4. I posted a question about this on the SQL Source Control with the error and some logs. / comments
I'm getting the same thing. Will hold out a day or two to see if RG has an update, else I'll need to go back to 18.4. I posted a question about this on the SQL Source Control with the error and so...