Options

DBA xPress ›› Features ›› Schema Inspector ››
Parent Previous Next

Options


Comparison Options

The comparison options apply to each comparison performed and specify how the two data sources will be compared and matched.

Setting

Description

Ignore ANSI NULLS

Ignores the state of SET ANSI NULLS during comparison for SQL programmable objects.

Ignore Collation

Ignores collation differences

Ignore WITH NOCHECK

Ignores WITH NOCHECK on check and foreign key constraints

Ignore Data Space Assignments

Ignores the data spaces that objects are assigned to

Ignore IDENTITY Property

Ignores columns whereby one is an IDENTITY column and the other is not

Ignore IDENTITY Seed & Increment

Ignores columns whereby both are IDENTITY columns but the seed and/or increment differ

Ignore Nullability

Ignores nullability on columns and types

Ignore QUOTED IDENTIFIER

Ignores the state of SET QUOTED IDENTIFIER during comparison for SQL programmable objects.

Ignore Referential Actions

Ignores ON UPDATE and ON DELETE clause differences for foreign keys

Ignore Object Principals

Ignores differences in object owning principals

Ignore EXECUTE AS Principals

Ignores EXECUTE AS clauses

Ignore Partitioning

Ignores differences in partition ordinals on indexes

Ignore SQL Comments

Ignores comments in SQL programmable objects

Ignore SQL White Space

Ignores white space in SQL programmable objects

Ignore SQL Case

Ignores differences in case in SQL programmable objects

Ignore Target Key Indexes

Ignores indexes that are used by foreign keys on the referenced table

Use Case Sensitive Matching

Causes object name matching to be case sensitive

Ignore Column Length

Ignore the specified length of columns

Ignore NOT FOR REPLICATION

Causes differences in specification of NOT FOR REPLICATION to be ignored

Ignore Precision & Scale

Ignore the precision and scale of columns

Ignore SCHEMABINDING

Ignore the WITH SCHEMABINDING property

Ignore IGNORE DUPLICATE KEY

Ignore use of IGNORE DUPLICATE KEY

Ignore Fill Factor

Ignore index fill factors

Ignore Index Padding

Ignore index padding

Ignore Computed Column Persistence

Ignore computed columns marked as PERSISTED

Ignore Page/Row Lock Allowances

Ignore ‘allow page lock’ and ‘allow row lock’ settings on indexes

Ignore Schema Collection Properties

Ignore XML Schema Collection assignments

Ignore Key Ascendancy

Ignore key sort orders on indexes

Ignore INCLUDE Columns

Ignore INCLUDED columns on indexes

Ignore WITH RECOMPILE

Ignore the WITH RECOMPILE clause

Ignore WITH CHECK OPTION

Ignore the WITH CHECK OPTION clause

Ignore NULL ON NULL INPUT

Ignore the NULL ON NULL INPUT property

Ignore Maximum Queue Readers

Ignore the maximum queue readers property on service queues

Ignore Permission Sets

Ignore permission differences on assemblies

Ignore Boundary Values

Ignore boundary value alignments on partition functions

Ignore Accent Sensitivity

Ignore accent sensitivity on full text indexes

Ignore Change Tracking States

Ignore change tracking states on full text indexes

Ignore Selected Stoplists

Ignore stop list differences on full text indexes

Ignore Service Names

Ignore service names on event notifications

Ignore Broker Instances

Ignore broker instances on event notifications and routes

Ignore ROWGUIDCOL Properties

Ignore the ROWGUIDCOL property

Ignore Column Sparsity

Ignore differences in column sparsity

Ignore Data Space Default Selections

Ignore data space DEFAULT settings

Ignore Full Text Catalog Defaults

Ignore full text catalog DEFAULT settings

Find Constraints By Signature

Enable the ability to match constraints by their schema, rather than their name. This is useful when comparing databases which are using system-named constraints.

Consider Column Order

Consider a table as different if it’s columns are in a different order

Find Objects In Any Schema

Allow objects to be found in other schema if they are not found in the correct schema.

Ignore Corrected Object Names

Ignore object names that are not correct because sp_rename has been used.


Generation Options

The generation options apply to each synchronization performed and specify how the schema modification SQL will be generated under various circumstances.

Setting

Description

Batch Separator

The batch separator that will be emitted between SQL batches in saved scripts

Use Object Presence Checks

Whether to use IF EXISTS and IF NOT EXISTS when generating DDL SQL

Use Transacted Modification SQL

Whether to place schema modifications in a transaction, with rollback management

Always Specify Collation

Whether collation should always be specified, or only specified when it is different from the database default

Replace User Defined Types With Base Types

Whether user defined types should be scripted as their base type

Keep Trigger Order

Whether trigger order should be preserved

Allow System Named Constraints

Whether system named constraints should be scripted as system named constraints, or whether they should explicitly use the generated name of the source constraint

Warn About UNSAFE Assemblies

Whether to warn about UNSAFE assemblies

Auto Create Files For File groups

Whether to create files for file groups in the default location

Use Online Index Building

Whether to use online index rebuilds (only available in Enterprise Edition)

Emit Warnings In Output SQL

Whether to emit the generation warnings in comments with each batch

Emit Table Constraints In-Line

Whether to emit check, default, unique and primary key constraints with their related tables

Fix Object Names

Whether to fix object names that have become incorrect through the use of sp_rename

Rebuild tables when altering assemblies

Whether to rebuild tables when altering assemblies.


Synchronization Methods

There are three synchronization methods available in Schema Inspector. These control the method by which synchronization will occur.

Method

Description

Available when target is

Direct

Direct synchronization executes the schema  on the target database. The SQL used for modification is not saved, though a report can still be generated.

A database

Script

Script synchronization generates the schema modifications into a SQL script file, and no execution is performed.

A database, a snapshot or blank

Hybrid

Hybrid synchronization executes the schema modifications directly on the target database, while also saving them into a SQL script file.

A database