When working with SQL Source Control Projects, SQL Change Automation PowerShell requires the same permissions as SQL Compare:
Permissions required to use SQL Compare
Build step specific:
Besides the permissions listed above please note that the following permissions might be required when doing the schema validation:
- sysadmin if using the Temporary Server option (because when it creates the Database it sets TRUSTWORTHY ON).
- db_owner if using the Temporary Database option.
3
3
Was this article helpful?
3 out of 3 found this helpful
Articles in this section
- Method not found: 'System.Security.CodeAccessPermission'
- Couldn't connect to the database specified by the Target parameter: A connection was successfully established with the server, but then an error occurred during the login process
- Could not install SqlChangeAutomation from any registered PSRepository
- System.Exception: No match was found for the specified search criteria and module name 'SQLChangeAutomation'. Try Get-PSRepository to see all available registered module repositories
- No match was found for the specified search criteria and module name 'SqlChangeAutomation'.
- Online index operations can only be performed in Enterprise edition of SQL Server
- Unable to resolve package source
- error 5(Access is denied.) while attempting to open or create the physical file
- SQL Change Automation Installation freezes at 99%
- SQL Change Automation Powershell permissions
Add comment
Please sign in to leave a comment.