I believe I have found a bug in SQL Compare 11 (v11.6.11.2463). I created a user defined table type with memory optimization turned on. It also has a primary key set as an auto increment identity.
I receive an error when using SQL Compare when this user defined table type exists. SQL allows me to create the type, and allows me to use it. But SQL Compare throws an error when this object exists in the database. The version of SQL Server we're using is 12.0.2000.8, Enterprise 64-bit. (I believe the IDENTITY(1,1) to be the specific thing that causes the error because it works fine without the IDENTITY(1,1)).
CREATE TYPE [MAIL].[MailSplitSort] AS TABLE(
[ID] [int] IDENTITY(1,1) NOT NULL,
[mtligID] [int] NOT NULL,
[SortOrder] [int] NOT NULL,
[ZipID] [int] NOT NULL,
[Pieces] [int] NOT NULL,
[MaxPieces] [int] NOT NULL,
[SplitNumber] [int] NULL,
INDEX [IX_MailSplitSort_ID] NONCLUSTERED (
[ID] ASC
)
)
WITH ( MEMORY_OPTIMIZED = ON )
GO
I receive an error when using SQL Compare when this user defined table type exists. SQL allows me to create the type, and allows me to use it. But SQL Compare throws an error when this object exists in the database. The version of SQL Server we're using is 12.0.2000.8, Enterprise 64-bit. (I believe the IDENTITY(1,1) to be the specific thing that causes the error because it works fine without the IDENTITY(1,1)).
CREATE TYPE [MAIL].[MailSplitSort] AS TABLE(
[ID] [int] IDENTITY(1,1) NOT NULL,
[mtligID] [int] NOT NULL,
[SortOrder] [int] NOT NULL,
[ZipID] [int] NOT NULL,
[Pieces] [int] NOT NULL,
[MaxPieces] [int] NOT NULL,
[SplitNumber] [int] NULL,
INDEX [IX_MailSplitSort_ID] NONCLUSTERED (
[ID] ASC
)
)
WITH ( MEMORY_OPTIMIZED = ON )
GO