February 26, 2004 at 9:42 pm
Hi All,
I've got a background from Foxpro, at that time when I created a foreign key column, the FoxPro would automatically index that column.
Now, In Sql Server, I've got a few tables with so many foreign keys. Is it still a good design behavior if I create an index for each column? I have no doubt about creating index on foreign key columns before until I got an alert that it would slow down the Insert/Update performance.
I need some advice on this subject. Still I need to create index on that foreign Keys? Does creating composite Index instead of indexing on each column would increase benefits?
I'd appreciate much for any suggestions
Thanks in advance
Hendry
February 27, 2004 at 4:29 am
Generally you should index foreign keys. I usually only create conposite indexes when I need to cover the query, or because its a constraint.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply