User profile for alanghopkinson

Our inline constraints came individual object creation files were stored in source code control system. I am not sure how these were generated originally (perhaps a modeling tool such as ERWin) while the table constraint is from within Enterprise Manager. EM does not provide an option to use inline DEFAULT constraints. So, the solution seems to be to generate the scripts using the same tool so it will use the same style. i.e. assuming EM, that would imply running these individual CREATE scripts against an intermediary DB and then generating from there. / comments

Our inline constraints came individual object creation files were stored in source code control system. I am not sure how these were generated originally (perhaps a modeling tool such as ERWin) whi...

0 votes

Regarding the original issue, the script with the 'ALTER TABLE...ADD CONSTRAINT.. ' style was generated by Enterprise Manager while the other came from source code control (individual object scripts). I would expect that scripting via EM to be a very common method and therefore ignoring this statement would likely affect a large number of your users. Of course, the prioritisation is up to you so this is just my two cents. / comments

Regarding the original issue, the script with the 'ALTER TABLE...ADD CONSTRAINT.. ' style was generated by Enterprise Manager while the other came from source code control (individual object script...

0 votes

I understand your point but generating lots of spurious differences sort of defeats the purpose of the tool. I tried your workaround to set the "ignore contraint and index names" but it didn't change the result. I also tried to set up a test by creating two simple scripts with the different syntaxes test1.sql ===== CREATE TABLE [AccessControlList]( [ACL_AccessControlListId] uniqueidentifier ROWGUIDCOL DEFAULT NewId() NOT NULL, [ACL_SecurityDescriptorId] uniqueidentifier NOT NULL, [ACL_Type] varchar(25) NOT NULL, CONSTRAINT [PK_AccessControlList] PRIMARY KEY NONCLUSTERED (ACL_AccessControlListId) WITH FILLFACTOR = 90 ON INDEXES, CONSTRAINT [FK_AccessControlList_SecurityDescriptor] FOREIGN KEY ([ACL_SecurityDescriptorId]) REFERENCES [SecurityDescriptor]([SDE_SecurityDescriptorId]) ) go test2.sql ===== CREATE TABLE [dbo].[AccessControlEntry] ( [ACE_AccessControlEntryId] uniqueidentifier ROWGUIDCOL NOT NULL , [ACE_AccessControlListId] [uniqueidentifier] NOT NULL , [ACE_Type] [varchar] (6) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL , [ACE_StandardAccessRights] [varchar] (500) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL , [ACE_GenericAccessRights] [varchar] (500) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL , [ACE_CustomAccessRights] [bigint] NOT NULL , [ACE_TrusteeId] [uniqueidentifier] NOT NULL , [ACE_SystemFunctionId] [uniqueidentifier] NULL , [ACE_Inheritance] [tinyint] NULL ) ON [PRIMARY] GO ALTER TABLE [dbo].[AccessControlEntry] ADD CONSTRAINT [DF_AccessControlEntry_ACE_AccessControlEntryId] DEFAULT (newid()) FOR [ACE_AccessControlEntryId], CONSTRAINT [PK_AccessControlEntry] PRIMARY KEY NONCLUSTERED ( [ACE_AccessControlEntryId] ) WITH FILLFACTOR = 90 GO Unfortunately, I received a "Object reference not set to an instance of object" error when I tried to run the comparison. Any thoughts? / comments

I understand your point but generating lots of spurious differences sort of defeats the purpose of the tool. I tried your workaround to set the "ignore contraint and index names" but it didn't chan...

0 votes

How can we help you today?

alanghopkinson

Comments