>>>>Hi,
>>>>
>>>>What works better (better practice) when creating a unique index that is used in FK constraints on child tables? Unique index using this syntax:
>>>>
>>>>
>>>>CREATE UNIQUE INDEX IX_deptfile_cost_cent_site_no ON deptfile (cost_cent, site_no )
>>>>
>>>>
>>>>or creating a constraint using the following syntax:
>>>>
>>>>
>>>>ALTER TABLE [dbo].[deptfile] ADD CONSTRAINT [IX_deptfile_cost_cent_site_no] UNIQUE NONCLUSTERED
>>>>(
>>>> [cost_cent] ASC,
>>>> [site_no] ASC
>>>>)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
>>>>
>>>>
>>>>?
>>>>
>>>
>>>Use CREATE CONSTRAINT as when you create a unique index, the unique constraint is created anyway.
>>>>TIA
>>
>>Just to make sure I got it. You are suggesting the following syntax?:
>>
>>
>>CREATE CONSTRAINT IX_deptfile_cost_cent_site_no ON deptfile (cost_cent, site_no )
>>
>
>This doesn't seem correct. Your second syntax was correct.
Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
