xSQL.SchemaCompare.SqlServer Namespace > ComparisonOptions Class : IgnoreNameInDefinition Property |
'Declaration <ComparisonOptionDescriptorAttribute(ComparisonOptionTypeEnum.ComparisonOption)> Public Property IgnoreNameInDefinition As System.Boolean
[ComparisonOptionDescriptorAttribute(ComparisonOptionTypeEnum.ComparisonOption)] public System.bool IgnoreNameInDefinition {get; set;}
[ComparisonOptionDescriptorAttribute(ComparisonOptionTypeEnum.ComparisonOption)] public: __property System.bool get_IgnoreNameInDefinition(); public: __property void set_IgnoreNameInDefinition( System.bool value );
SQL Server supports various formats for the object name in the definition, such as name, schema.name, [name] or [schema].[name]. In some cases, a difference in the name does not indicate a "true" difference in the schema.
Consider, for example, a view named "view1" with the following definitions in two databases:
CREATE VIEW dbo.view1 AS <select_statement>
CREATE VIEW [dbo].[view1] AS <select_statement>
If the only difference between these definitions is the way the name is formatted, you might want to consider them equal and not trigger a schema difference. This options achieves precisely that by ignoring the name when the definitions are compared.
Please note that this option effects only the comparison of the definition. The name is preserved when the object is scripted. Changing the scripted name to a unified and standard format can be achieved via the option StandardizeNameInDefinition.
The default value for this option is false.
Target Platforms: Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2