data import settings - security objects

• ericjlawson

  Mr or Mrs. 500

  Points: 581

  More actions

  December 14, 2018 at 8:06 am

  #416554

  Hi,

  Importing

  I am importing existing production databases into VSPro SQL Server projects to version control what we have and make changes.

  I have tried every import database combination I can find, but no matter what, Users, Roles and Schemas are always imported.

  I want the schemas only. I get several Server base logins and users that cause problems for example.

  So question 1, is import of these things preventable. What I read in blogs and instructions it should be but it keeps happening. 

  Schema Compare / generate script

  So I have a project that contains several CREATE USER and CREATE ROLE files / DDL statements and a RoleMemberships file due to the issues above.

  Question 2 - should I exclude or delete these from the project before attempting to schema compare / publish the database changes I really want?

  Currently I have retained them, but despite selecting the recommended options to NOT compare these elements, the schema compare and generated script still includes code to delete, add or modify these users and roles. 

  Software versions
  
  Thanks in advance
  Eric