Schema created when new role is created

When a new role is detected in the source database and the synchronization script is created, a new schema is also created. What is the reason for this?

Thanks,
Carissa

Comments

  • Thanks for your post.

    It's probably because the role has a dependency on the schema, and the project option 'include dependencies' is being used. This option is always selected by default, to help avoid leaving your database in an inconsistent state after a synchronization.

    If you're using the GUI, you can uncheck the option on step 2 of the sync' wizard.

    I hope this helps.
    Chris
Sign In or Register to comment.