Hello,
I have a situation here...
where we are inserting data of candidate...which includes fields...
1. First Name, Middle Name, Last Name ... (varchar(50))
2. Passport ID (no duplicates allowed but may be null )
3. Telephone number... ( may be null but no duplicates allowed )
4. Date of Birth ( mandatory )
5. Email id .......(no duplicates allowed but may be null )
The problem is that we already have about 1 lakh enteries in the database..
and it is expected to grow with time...
We need to define indexers such that it doesnot take time for searching or while inserting a new datafield into the database.
I hope that i am clear.
since, i suspect that that as it grows it will become more and more slow...!
This is database to store "resumes of different candidates".
So have decided...that
1. name 2. Passport no. 3. Email id: 4. Contact number
be the fields to prevent duplicacy of candidate data...
This involves checking for candidates existence every time anybody tries to make a new entry into database.
Please help to decide over the indexers...
Any good suggestions are welcomed...
Thanks for the reply...
\With regards,
Girish R. Pawar
You could easily have dupicates for Name. I would most certainly break the name into at least LastName and FirstName.
Two candidates 'could' be sharing a contact telephone number, so your 'no duplicates' constraint may be a problem.
I will often have an 'Age' field on the input form (BUT it isn't saved to the database) -it acts as a 'cross-check' against the DOB. DOB is so critical in some situations, we want to catch the obvious 'transpositions' immediately.
Your choices of indexes seem reasonable.
No comments:
Post a Comment