*** An error occurred during deployment plan generation. Deployment cannot continue.
Error SQL72018: Permission could not be imported but one or more of these objects exist in your source
Loading
*** An error occurred during deployment plan generation. Deployment cannot continue.
Error SQL72018: Permission could not be imported but one or more of these objects exist in your source
Know the answer? Post it — somebody with the same question will find it here.
Sign in to answer this question
It is the same account you read, post and publish with — and you will come straight back to this page.
Naimish MakwanaPosted Apr 13, 2023, 1:01 PM
The error message indicates that there is a permission that cannot be imported during deployment because one or more of the objects that the permission is associated with already exists in the target database. This means that there may be a conflict between the permissions defined in the source and those already present in the target.
To resolve this issue, you can try one of the following approaches:
You may also want to review the deployment plan to identify the specific permission and object that are causing the error and determine the best course of action.
Tuhin PaulPosted Apr 16, 2023, 1:00 AM
You can perform a schema comparison between the source and target databases to identify any differences and reconcile them before attempting the deployment.
Amit MohantyPosted Apr 14, 2023, 4:42 AM
The error message you're seeing indicates that there was an issue with the deployment plan generation process, and specifically that a permission could not be imported. This could be happening for a number of reasons, but the most likely cause is that the deployment process is encountering an object in your source that it does not have the appropriate permissions to access.
When deploying a SQL Server database, the deployment process needs to ensure that all the necessary permissions are in place to allow the database to function properly. If a required permission cannot be imported during the deployment plan generation process, the deployment will fail and you will see the error message you've described.