Home/ Questions/Q 5938237
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T15:39:23+00:00

Here’s my simple scenario: I’ve a Users table and a Locations table. ONE User

  • 0

Here’s my simple scenario:

I’ve a Users table and a Locations table. ONE User can be related to MANY Locations so I’ve a UserLocation table which is as follows:

ID (int-Auto Increment) PK
UserID (Int FK to the Users table)
LocID (Int FK to the Locations table)

Now, as ID is the PK it is Indexed by default in SQL-Server. I was a bit confused about the other two columns:

OPT 1: Shud I define an Index on both the columns like:
IX_UserLocation_UserID_LocID

OR

OPT 2: Shud I define two separate Indexes like : IX_UserLocation_UserID
& IX_UserLocation_LocID

Pardon me if both do the same – in that case pls explain. If not – which one is better and why?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You should probably create two separate indexes. One thing that is often forgotten with foreign keys is the fact that deleting a user might cascade-delete the user-location relation in your table. If there is no index on userID, this might lead to a table-lock of your user-location relation. The same applies to deleting a location.

    • 0