Options
Initial DB Commit Shows Drop Statements For Security Object
jkennedy
Posts: 18
I'm having issues on a couple of databases. Recreating the issue: I click Setup and map to a new folder. Go to commit changes tab. "Drop" changes are shown for multiple schemas. I try to check them in, and get the following warning. Then the checkin errors on:
CheckIn returned with ChangeSet ID=0, nothing to Check in?
Warnings:
Didn't expect 0 actual 0
Severity: Low
Object: db_accessadmin
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the db_accessadmin schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: db_backupoperator
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the db_backupoperator schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: db_datareader
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the db_datareader schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: db_datawriter
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the db_datawriter schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: db_ddladmin
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the db_ddladmin schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: db_denydatareader
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the db_denydatareader schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: db_denydatawriter
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the db_denydatawriter schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: db_owner
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the db_owner schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: db_securityadmin
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the db_securityadmin schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
I tried deleting and recreating mapping the DB. Didn't work. This is happening on 2 dbs.
CheckIn returned with ChangeSet ID=0, nothing to Check in?
Warnings:
Didn't expect 0 actual 0
Severity: Low
Object: db_accessadmin
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the db_accessadmin schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: db_backupoperator
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the db_backupoperator schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: db_datareader
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the db_datareader schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: db_datawriter
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the db_datawriter schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: db_ddladmin
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the db_ddladmin schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: db_denydatareader
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the db_denydatareader schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: db_denydatawriter
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the db_denydatawriter schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: db_owner
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the db_owner schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
Severity: Low
Object: db_securityadmin
Title: Dropping a schema is a potentially dangerous operation. Dependencies for the db_securityadmin schema are not selected automatically. If you are sure you want to drop this schema please select the objects that belong to this schema manually.
I tried deleting and recreating mapping the DB. Didn't work. This is happening on 2 dbs.
Comments
I have followed up with you via email to get some more information on this issue.
I believe that updating to the latest version may eliminate the error.
Warm Regards,
Andrew
Technical Sales Engineer
Redgate Software
I'm also having a similar issue to this, although only with the db_datareader schema rather than with several.
Again, this is when linking a database to source control and doing the first commit.
I only downloaded SQL Source Control yesterday (version 4.1.15.118), so I don't think it's a download the latest version fix!
Is this an error or is this an expected scenario? As the schema has been dropped before the Db was linked and the first commit was made it feels odd that SQL Source Control shows this error.
I am running SQL Source Control version 7.0.11.8918.