Comments on: Tuning your SQL Query – Generating a Proper Execution Plan.

By: Metin

Metin — Wed, 28 Nov 2012 19:46:00 +0000

Satnam, you gave a good sample. But We should be very carefull by including columns inside creating a noncluster index. The disc space and the cost of Insert statements will be increase by the number of Indexes and the columns which have been included. It depence on the attitude of your Table. For those, which get lots of inserted data, it is not preffered to use. But in the other hand, which are mostly get read from many sessions, the performance will come to front and those cases we suggest to use…

By: Oliver

Oliver — Fri, 23 Nov 2012 15:30:53 +0000

Satnam, is it okay to remove idx_city since it has already been included in the second index idx_key_student_first_name? You’ve excluded student_id on idx_key_student_first_name but you didn’t dropped idx_city. Won’t that be redundant? What are the pros and cons of having same column in one or more indexes?

By: Prakash

Prakash — Fri, 23 Nov 2012 03:55:52 +0000

Are you keeping same column (city) in both indexes? or drop the 1st index (index idx_city)?

By: Ibra

Ibra — Thu, 22 Nov 2012 22:03:17 +0000

Very basic info…I guess this could be useful for inexperienced DBA’s and Dev’s…

By: Valentin

Valentin — Thu, 15 Nov 2012 23:39:12 +0000

Hardly any more basic than this…

By: Adrian Facio

Adrian Facio — Wed, 14 Nov 2012 14:49:24 +0000

Like it.