Comments
Sort by recent activity
Thanks for confirming this is an issue.
I look forward to the next releases which will address this annoyance!
Mostly it annoys me because in that example it looks like I have 2 indexes covering the same columns, one is unique and one non-unique! :shock: / comments
Thanks for confirming this is an issue.
I look forward to the next releases which will address this annoyance!
Mostly it annoys me because in that example it looks like I have 2 indexes covering th...
The "About SQL Doc" reports I'm on 2.0.1.51, so I think I'm up to date.
Here's a table definition that produces the strange results when you generate the .chm, and below is the Indexes section in the chm.
SERVERPROPERTY('productversion')
9.00.4053.00 SP3 CREATE TABLE [dbo].[RepAccount]
(
[ID] [int] NOT NULL IDENTITY(1, 1),
[Account_ID] [int] NOT NULL,
[Rep_ID] [int] NOT NULL,
[DateModified] [datetime] NOT NULL CONSTRAINT [DF_RepAccount_DateModified] DEFAULT (getdate())
) ON [PRIMARY]
GO
ALTER TABLE [dbo].[RepAccount] ADD CONSTRAINT [PK_RepAccount] PRIMARY KEY CLUSTERED ([ID]) ON [PRIMARY]
GO
ALTER TABLE [dbo].[RepAccount] ADD CONSTRAINT [IX_RepAccount_AccountID] UNIQUE NONCLUSTERED ([Account_ID], [Rep_ID]) ON [PRIMARY]
GO
CREATE NONCLUSTERED INDEX [IX_RepAccount_RepID] ON [dbo].[RepAccount] ([Rep_ID], [DateModified]) INCLUDE ([Account_ID]) ON [PRIMARY]
GO
Name Columns
PK_RepAccount ID
IX_RepAccount_AccountID Account_ID, Rep_Id
IX_RepAccount_RepID Account_ID, Rep_Id, DateModified / comments
The "About SQL Doc" reports I'm on 2.0.1.51, so I think I'm up to date.
Here's a table definition that produces the strange results when you generate the .chm, and below is the Indexes section in t...