JKSQL (6/12/2009)
yes exactly.there would be one on filter = 0 and then one on filter = 1
The table probably should have been split but there is already existing code and they have identical fields just the key has changed.
That makes no sense. How would that be any different that a Unique constraint on both that just included the IsFilter column?
That is, how is what you want any different from this?:
CREATE UNIQUE NONCLUSTERED INDEX [IX_X] ON [dbo].[X]
(
[XName] ASC,
[XUsersID] ASC,
[IsFilter] ASC
)
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]