Primary key constraint dropped but not recreated.

Forum for users of SQL Compare schema synchronization utility

Primary key constraint dropped but not recreated.

Postby Mattias » Mon Sep 30, 2013 5:27 pm

SQL Compare 10.5.0.611

I am removing identity from a column so the table is dropped and recreated. But the recreated table does not get primary key constraint.
In a later stage this makes the whole installation fail because of a foreign key.

This is part of the created script with transactions removed for readability.

PRINT N'Dropping constraints from [dbo].[GroupOrVariableType]'
GO
ALTER TABLE [dbo].[GroupOrVariableType] DROP CONSTRAINT [PK_GroupOrVariableType]
GO
PRINT N'Rebuilding [dbo].[GroupOrVariableType]'
GO
CREATE TABLE [dbo].[tmp_rg_xx_GroupOrVariableType]
(
[id] [int] NOT NULL,
[descr] [varchar] (50) NULL
)
GO
INSERT INTO [dbo].[tmp_rg_xx_GroupOrVariableType]([id], [descr]) SELECT [id], [descr] FROM [dbo].[GroupOrVariableType]
GO
DROP TABLE [dbo].[GroupOrVariableType]
GO
EXEC sp_rename N'[dbo].[tmp_rg_xx_GroupOrVariableType]', N'GroupOrVariableType'
GO
PRINT N'Adding foreign keys to [dbo].[ConnectCall]'
GO
ALTER TABLE [dbo].[ConnectCall] ADD CONSTRAINT [FK_ConnectCall_GroupOrVariableType] FOREIGN KEY ([groupOrVariableTypeID]) REFERENCES [dbo].[GroupOrVariableType] ([id])
GO
Mattias
 
Posts: 4
Joined: Mon Sep 30, 2013 5:02 pm
Location: Sverige

Postby Mattias » Mon Sep 30, 2013 6:24 pm

I did some more testing and this only happens when the option ignore indexes is selected. Primary keys will not be created for new tables either.

Is it possible to ignore index comparison and still have primary keys created?
Is there any reason that this should not be possible?
Mattias
 
Posts: 4
Joined: Mon Sep 30, 2013 5:02 pm
Location: Sverige


Return to SQL Compare Previous Versions

Who is online

Users browsing this forum: No registered users and 0 guests