Comments
3 comments
-
Hi @DaveFirth ,
Sorry to hear you're experiencing this issue!
Please correct me if I'm wrong, but as you mentioned you're using SQL Change Automation as well, could you look inside the .sqlproj file and check if there's an extra reference to the sql file creating that user?
If that's not the case let me know and we will troubleshoot further! -
Thanks for you're response DanYes there was a sqlproj file - which included a reference to to a schema object for the user. However when I deleted these (its on my local machine and this is a test setup) I still saw the same errorDo you think I would be best getting started with SQL Source Control without the change automation? Or is there away to ensure scripts generated by these two programs don't cause conflicts?
-
Hi @DaveFirth
That's odd, what I can do is follow up with you via a support ticket to see if we can find where this issue stems from!
Generally speaking you shouldn't come across too many issues using both tools as it's common for SQL Change Automation projects to be SQL Source Control projects using the scripts folder.
Add comment
Please sign in to leave a comment.
Ensure that case sensitivity options are set correctly and all object creation scripts are valid.If the problem persists, contact Redgate support.