* according to this, couchbase 2.2.0 starting 20th of June*The underlying problem is that My SQL accepts identity updates (when there are no changes) but Sql Server being properly designed complains with this bad practice.
This article discusses three common problems DBAs are likely to encounter when columns have an identity property that will auto-increment its value when data is inserted.
So the set of packages affected by an incorporation—or constrained by the incorporation—can be much larger than the set named in the incorporation package.
If you try to install a different version of a package whose version is constrained by an incorporation, you will receive an error message and the update or install operation will fail.
In general, the supported way to update a package whose version is constrained by an incorporation is to update the incorporation package.
Sometimes you need to install software that is constrained by an incorporation at a different version than the incorporation allows.
Products To Insert GO CREATE TABLE Product ( Product ID INT NOT NULL IDENTITY(1,1) PRIMARY KEY, [Name] NVARCHAR(50) NOT NULL, Product Number NVARCHAR(25) NOT NULL, List Price MONEY NOT NULL) GO CREATE UNIQUE INDEX IX_Product_Product Number ON Product ( Product Number ) GO CREATE TABLE Products To Insert ( Row ID INT NOT NULL IDENTITY(1,1) PRIMARY KEY, [Name] NVARCHAR(50) NOT NULL, Product Number NVARCHAR(25) NOT NULL, List Price MONEY NOT NULL, Inserted Identity Value INT NULL) GO INSERT Product ([Name], Product Number, List Price) SELECT TOP 450 [Name], Product Number, List Price FROM Adventure Works. Product ORDER BY Sell Start Date, Product ID GO INSERT Products To Insert ([Name], Product Number, List Price) SELECT [Name], Product Number, List Price FROM Adventure Works. Product GO The Product table has an identity column as its primary key. The Products To Insert table has the Product Number column and a column for whatever identity value is inserted when we put the row into the Product table.
Unfortunately this is part of a much larger project. Forgive me if this shouldn't be logged here or I have done something stupid, publishing migrations doesn't seem to apply the Identity flag to a column but only on Sql Server. Migrations are currently only generated based on the active provider (SQLite).
I'm using Open Iddict with Identity to generate the base schema for the database. You'll need to compensate for any additional providers you intend to run the migrations on.
Tools: 1.0.0-preview2-final Operating system: Windows Server 2008 R2 Visual Studio version: (e.g.
CREATE TABLE [dbo].[tm2] ( [id] [int] NOT NULL, [aid] [int] IDENTITY(1,1) NOT NULL, [txt] [nchar](10) NULL, CONSTRAINT [PK_tm2] PRIMARY KEY CLUSTERED ([id] ASC) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] GO SET IDENTITY_INSERT [dbo].tm2 ON MERGE INTO [dbo].tm2 AS Target USING (VALUES (1,2,'qdqewqf'), (2,3,'#ED7F00') ) AS Source ([ID], [aid], [txt]) ON (Target.[ID] = Source.[ID]) WHEN MATCHED AND () THEN UPDATE SET aid = Source.aid, txt = WHEN NOT MATCHED BY TARGET THEN INSERT([ID], aid, txt) VALUES(Source.[ID], Source.aid, Source.txt) WHEN NOT MATCHED BY SOURCE THEN DELETE; SET IDENTITY_INSERT [dbo].tm2 OFF USE tempdb; CREATE TABLE dbo.