Aggregates

Allow Drop Blocking Assemblies

Allow Incompatible Platform

Allow Unsafe Row Level Security Data Movement

Application Roles

Assemblies

Assembly Files

Asymmetric Keys

Audits

Backup Database Before Changes

Block On Possible Data Loss

Block When Drift Detected

Broker Priorities

Certificates

Clr User Defined Types

Column Encryption Keys

Column Master Keys

Comment Out Set Var Declarations

Compare Using Target Collation

Contracts

Create New Database

Credentials

Cryptographic Providers

Database Audit Specifications

Database Encryption Keys

Database Options

Database Roles

Database Scoped Credentials

Database Triggers

Defaults

Deploy Database In Single User Mode

This property is used by SqlClr deployment to cause any blocking assemblies to be dropped as part of the deployment plan. By default, any blocking/referencing assemblies will block an assembly update if the referencing assembly needs to be dropped.

Specifies whether to attempt the action despite incompatible SQL Server platforms.

Do not block data motion on a table which has Row Level Security if this property is set to true. Default is false.

Backups the database before deploying any changes.

Specifies that the publish episode should be terminated if there is a possibility of data loss resulting from the publish operation.

Specifies whether to block updating a database whose schema no longer matches its registration or is unregistered.

Specifies whether the declaration of SETVAR variables should be commented out in the generated publish script. You might choose to do this if you plan to specify the values on the command line when you publish by using a tool such as SQLCMD.EXE.

This setting dictates how the database's collation is handled during deployment; by default the target database's collation will be updated if it does not match the collation specified by the source. When this option is set, the target database's (or server's) collation should be used.

Specifies whether the target database should be updated or whether it should be dropped and re-created when you publish to a database.

If true, the database is set to Single User Mode before deploying.

Specifies whether Data Definition Language (DDL) triggers are disabled at the beginning of the publish process and re-enabled at the end of the publish action.

If true, Change Data Capture objects are not altered.

Specifies whether objects that are replicated are identified during verification.

Specifies whether constraints that do not exist in the database snapshot (.dacpac) file will be dropped from the target database when you publish to a database.

Specifies whether DML triggers that do not exist in the database snapshot (.dacpac) file will be dropped from the target database when you publish to a database.

Specifies whether extended properties that do not exist in the database snapshot (.dacpac) file will be dropped from the target database when you publish to a database.

Specifies whether indexes that do not exist in the database snapshot (.dacpac) file will be dropped from the target database when you publish to a database.

Specifies whether objects that do not exist in the database snapshot (.dacpac) file will be dropped from the target database when you publish to a database. This value takes precedence over DropExtendedProperties.

Specifies whether permissions that do not exist in the database snapshot (.dacpac) file will be dropped from the target database when you publish updates to a database.

Specifies whether role members that are not defined in the database snapshot (.dacpac) file will be dropped from the target database when you publish updates to a database.</

Specifies whether statistics that do not exist in the database snapshot (.dacpac) file will be dropped from the target database when you publish to a database.

Automatically provides a default value when updating a table that contains data with a column that does not allow null values.

Specifies whether differences in the ANSI NULLS setting should be ignored or updated when you publish to a database.

Specifies whether differences in the Authorizer should be ignored or updated when you publish to a database.

Specifies whether differences in the column collations should be ignored or updated when you publish to a database.

Specifies whether differences in table column order should be ignored or updated when you publish to a database.

Specifies whether differences in the comments should be ignored or updated when you publish to a database.

Specifies whether differences in the file path for the cryptographic provider should be ignored or updated when you publish to a database.

Specifies whether differences in the order of Data Definition Language (DDL) triggers should be ignored or updated when you publish to a database or server.

Specifies whether differences in the enabled or disabled state of Data Definition Language (DDL) triggers should be ignored or updated when you publish to a database.

Specifies whether differences in the default schema should be ignored or updated when you publish to a database.

Specifies whether differences in the order of Data Manipulation Language (DML) triggers should be ignored or updated when you publish to a database.

Specifies whether differences in the enabled or disabled state of DML triggers should be ignored or updated when you publish to a database.

Specifies whether extended properties should be ignored.

Specifies whether differences in the paths for files and log files should be ignored or updated when you publish to a database.

Specifies whether differences in the file sizes should be ignored or whether a warning should be issued when you publish to a database.

Specifies whether differences in the placement of objects in FILEGROUPs should be ignored or updated when you publish to a database.

Specifies whether differences in the fill factor for index storage should be ignored or whether a warning should be issued when you publish to a database.

Specifies whether differences in the file path for the full-text catalog should be ignored or whether a warning should be issued when you publish to a database.

Specifies whether differences in the seed for an identity column should be ignored or updated when you publish updates to a database.

Specifies whether differences in the increment for an identity column should be ignored or updated when you publish to a database.

Specifies whether differences in the index options should be ignored or updated when you publish to a database.

Specifies whether differences in the index padding should be ignored or updated when you publish to a database.

Specifies whether differences in the casing of keywords should be ignored or updated when you publish to a database.

Specifies whether differences in the lock hints on indexes should be ignored or updated when you publish to a database.

Specifies whether differences in the security identification number (SID) should be ignored or updated when you publish to a database.

Specifies whether the not for replication settings should be ignored or updated when you publish to a database.

Specifies whether an object's placement on a partition scheme should be ignored or updated when you publish to a database.

Specifies whether differences in partition schemes and functions should be ignored or updated when you publish to a database.

Specifies whether permissions should be ignored.

Specifies whether differences in the quoted identifiers setting should be ignored or updated when you publish to a database.

Specifies whether differences in the role membership of logins should be ignored or updated when you publish to a database.

Specifies whether differences in the amount of time that SQL Server retains the route in the routing table should be ignored or updated when you publish to a database.

Specifies whether differences in the semi-colons between T-SQL statements will be ignored or updated when you publish to a database.

Specifies whether differences in the table options will be ignored or updated when you publish to a database.

Specifies whether differences in the user settings objects will be ignored or updated when you publish to a database.

Specifies whether differences in white space will be ignored or updated when you publish to a database.

Specifies whether differences in the value of the WITH NOCHECK clause for check constraints will be ignored or updated when you publish to a database.

Specifies whether differences in the value of the WITH NOCHECK clause for foreign keys will be ignored or updated when you publish to a database.

Include all composite elements as part of a single publish operation.

Specifies whether transactional statements should be used where possible when you publish to a database.

Specifies that publish should always drop and re-create an assembly if there is a difference instead of issuing an ALTER ASSEMBLY statement

Specifies whether a new file is also created when a new FileGroup is created in the target database.

Specifies whether the schema is registered with the database server.

Specifies whether DeploymentPlanExecutor contributors should be run when other operations are executed.

Specifies whether differences in the database collation should be ignored or updated when you publish to a database.

Specifies whether differences in the database compatibility should be ignored or updated when you publish to a database.

Specifies whether target database properties should be set or updated as part of the publish action.

Specifies whether statements are generated in the publish script to verify that the database name and server name match the names specified in the database project.

Controls whether size is specified when adding a file to a filegroup.

At the end of publish all of the constraints will be verified as one set, avoiding data errors caused by a check or foreign key constraint in the middle of publish. If set to False, your constraints will be published without checking the corresponding data.

Include refresh statements at the end of the publish script.

Specifies whether errors encountered during publish verification should be treated as warnings. The check is performed against the generated deployment plan before the plan is executed against your target database. Plan verification detects problems such as the loss of target-only objects (such as indexes) that must be dropped to make a change. Verification will also detect situations where dependencies (such as a table or view) exist because of a reference to a composite project, but do not exist in the target database. You might choose to do this to get a complete list of all issues, instead of having the publish action stop on the first error.

Specifies whether warnings should be generated when differences are found in objects that cannot be modified, for example, if the file size or file paths were different for a file.

Specifies whether collation compatibility is verified.

Specifies whether checks should be performed before publishing that will stop the publish action if issues are present that might block successful publishing. For example, your publish action might stop if you have foreign keys on the target database that do not exist in the database project, and that will cause errors when you publish.

Disable And Reenable Ddl Triggers

Do Not Alter Change Data Capture Objects

Do Not Alter Replicated Objects

Drop Constraints Not In Source

Drop Dml Triggers Not In Source

Drop Extended Properties Not In Source

Drop Indexes Not In Source

Drop Objects Not In Source

Drop Permissions Not In Source

Drop Role Members Not In Source

Drop Statistics Not In Source

Endpoints

Error Messages

Event Notifications

Event Sessions

Extended Properties

External Data Sources

External File Formats

External Streaming Jobs

External Streams

External Tables

File Tables

Filegroups

Files

Full Text Catalogs

Full Text Stoplists

General Options

Generate SmartDefaults

Ignore AnsiNulls

Ignore Authorizer

Ignore Column Collation

Ignore Column Order

Ignore Comments

Ignore Cryptographic Provider FilePath

Ignore Ddl Trigger Order

Ignore Ddl Trigger State

Ignore Default Schema

Ignore Dml Trigger Order

Ignore Dml Trigger State

Ignore Extended Properties

Ignore File And Log File Path

Ignore File Size

Ignore Filegroup Placement

Ignore Fill Factor

Ignore Full Text Catalog FilePath

Ignore Identity Seed

Ignore Increment

Ignore Index Options

Ignore Index Padding

Ignore Keyword Casing

Ignore Lock Hints On Indexes

Ignore Login Sids

Ignore Not For Replication

Ignore Object Placement On Partition Scheme

Ignore Partition Schemes

Ignore Permissions

Ignore Quoted Identifiers

Ignore Role Membership

Ignore Route Lifetime

Ignore Semicolon Between Statements

Ignore Table Options

Ignore User Settings Objects

Ignore Whitespace

Ignore With No check On Check Constraints

Ignore With Nocheck On ForeignKeys

Include Composite Objects

Include Transactional Scripts

Linked Server Logins

Linked Servers

Logins

Master Keys

Message Types

No Alter Statements To Change Clr Types

Include Object Types

Partition Functions

Partition Schemes

Permissions

Populate Files On File Groups

Queues

Remote Service Bindings

Role Membership

Routes

Rules

Run Deployment Plan Executors

Scalar Valued Functions

Schema Compare Options

Script Database Collation

Script Database Compatibility

Script Database Options

Script Deploy StateChecks

Script File Size

Script New Constraint Validation

Script Refresh Module

Search Property Lists

Security Policies

Sequences

Server Audit Specifications

Server Role Membership

Server Roles

Server Triggers

Services

Signatures

Stored Procedures

Symmetric Keys

Synonyms

Table Valued Functions

Tables

Treat Verification Errors As Warnings

Unmodifiable Object Warnings

User Defined Data Types

User Defined Table Types

Users

Verify Collation Compatibility

Verify Deployment

Views

Xml Schema Collections

Reset

File

Flat

Object Type

Schema

Are you sure you want to update the target?

Compare Details

Do you want to connect to {0}?

Press Compare to refresh the comparison.

Action

Add

Apply is enabled when the target is a database or database project

Apply changes to target

There was an error updating the project

No changes to apply

Project was successfully updated

Stop

Cancel schema compare failed: '{0}'

Cannot exclude {0}. Included dependents exist

Cannot exclude {0}. Included dependents exist, such as {1}

Cannot include {0}. Excluded dependents exist

Cannot include {0}. Excluded dependents exist, such as {1}

Change

Compare

Schema Compare failed: {0}

Data-tier Application File (.dacpac)

Database

Delete

Schema Compare

Comparison between Source and Target

Generate script

Generate script is enabled when the target is a database

Generate script to deploy changes to target

Generate script failed: '{0}'

No changes to script

Include

Please note that include/exclude operations can take a moment to calculate affected dependencies

No schema differences were found.

Open

Open .scmp file

Load source, target, and options saved in an .scmp file

Open scmp failed: '{0}'

Options

Database Project

Type

Save

Save .scmp file

Save source and target, options, and excluded elements

Save scmp failed: '{0}'

Select connection

Select source file

Select target file

Select Source

Source Name

To compare two schemas, first select a source schema and target schema, then press Compare.

Switch source and target

Switch direction

Select Target

Target Name

Type

Apply

Schema Compare Apply failed '{0}'

Initializing Comparison. This might take a moment.

Source

Target

Yes

Cancel

Database

default

A different source schema has been selected. Compare to see the comparison?

Different source and target schemas have been selected. Compare to see the comparison?

A different target schema has been selected. Compare to see the comparison?

The source .sqlproj file does not specify a database schema component

The target .sqlproj file does not specify a database schema component

File

The sql-database-projects extension is required to perform schema comparison with database projects

The sql-database-projects extension is required to apply changes to a project

Server

Source Database

Source Server

Source file

Folder Structure

Target Database

Target Server

Target file

Options have changed. Recompare to see the comparison?

Schema/Object Type

Target Folder Structure

SQL Server Schema Compare for Azure Data Studio supports comparing the schemas of databases and dacpacs.

SQL Server Schema Compare

Run Schema Comparison

Schema Compare