Hi,
We just detected (after logn investigation) that linking/unlinking static data is broken since few versions.
If table is created with PK clustered and descending, it is not possible to link static data.
If static data is linked, change can be checked in, but immediatelly on tab GetLatestVersion "DataUnlink" will appear.
Getting version to new, empty database will result in missing data inside this table, and data link will be unmarked.
Script to reproduce problem:
CREATE TABLE [dbo].[TestTable](
[Id] [INT] NOT NULL,
[attValue1] [TINYINT] NOT NULL,
[attValue2] [NVARCHAR](100) NOT NULL,
CONSTRAINT [PK_TestTable] PRIMARY KEY CLUSTERED
(
[Id] DESC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]
GO
Hi
We just detected (after logn investigation) that linking/unlinking static data is broken since few versions.
If table is created with PK clustered and descending, it is not possible to link static data.
If static data is linked, change can be checked in, but immediatelly on tab GetLatestVersion "DataUnlink" will appear.
Getting version to new, empty database will result in missing data inside this table, and data link will be unmarked.
Script to reproduce problem:
CREATE TABLE [dbo].[TestTable](
[Id] [INT] NOT NULL,
[attValue1] [TINYINT] NOT NULL,
[attValue2] [NVARCHAR](100) NOT NULL,
CONSTRAINT [PK_TestTable] PRIMARY KEY CLUSTERED
(
[Id] DESC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]
GO