Toad World® Forums

6.7.0.91: Bug, regression, Primary keys do not get added

This is a problem that was fixed in the previous beta but has reappeared in the new one. Primary keys do not get added.

Comparison source pane:

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON
GO

CREATE TABLE [dbo].[InventoryCostingTotal] (
[Sku] nvarchar(200) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[RollupTotal] decimal(19, 4),
[StaticTotal] decimal(19, 4),
[SeCost] decimal(19, 4),
[SeTotal] decimal(19, 4),
CONSTRAINT [PK_InventoryCostingTotal_Sku] PRIMARY KEY([Sku]) WITH (FILLFACTOR=100) ON [PRIMARY]
) ON [PRIMARY]

Comparison target pane:

SET ANSI_NULLS ON
GO

SET QUOTED_IDENTIFIER ON
GO

CREATE TABLE [dbo].[InventoryCostingTotal] (
[Sku] nvarchar(200) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[RollupTotal] decimal(19, 4),
[StaticTotal] decimal(19, 4),
[SeCost] decimal(19, 4),
[SeTotal] decimal(19, 4)
) ON [PRIMARY]

Generated script:

USE [StoneEdgeRogue]
GO

/*
Script created at 11/30/2015 10:32 AM.
Please back up your database before running this script.

Source server: redacted
Source database: redacted

Target server: redacted
Target database: redacted
*/

SET NUMERIC_ROUNDABORT, IMPLICIT_TRANSACTIONS OFF
GO

SET ANSI_PADDING, ANSI_NULLS, QUOTED_IDENTIFIER, ANSI_WARNINGS, CONCAT_NULL_YIELDS_NULL, ARITHABORT, XACT_ABORT ON

Note that the generated script does nothing.

This started out as renaming a PK, but the script generated the first time dropped the PK completely. A second pass at the schema compare discovered the need to create a PK.

Hi Mark,

Sorry for this regression issue. This issue has been fixed.

Kelly