Hey Kim,
thanks for all your work, the outstanding WCs, the DNR interviews,...
Somewhere in your #5 WC you mentioned creating a (clustered, primary) index on social security number AND employee id. I don´t understand what the additional employee id is good for in the index, cuz the ss_id should be unique anyway.
Relatedly, in WC#7 you talk about a second column possibly being useful (for SEEKing or something?) in a compound index. I very well understand compound indexes, but I got no idea what firstname could help in an index on lastname, firstname when you seek for a first name, e.g.
Hope this is understandable and you´ll see this, though it´s in an older blog!
TIA
G
thanks for all your work, the outstanding WCs, the DNR interviews,...
Somewhere in your #5 WC you mentioned creating a (clustered, primary) index on social security number AND employee id. I don´t understand what the additional employee id is good for in the index, cuz the ss_id should be unique anyway.
Relatedly, in WC#7 you talk about a second column possibly being useful (for SEEKing or something?) in a compound index. I very well understand compound indexes, but I got no idea what firstname could help in an index on lastname, firstname when you seek for a first name, e.g.
Hope this is understandable and you´ll see this, though it´s in an older blog!
TIA
G
