Feb VTD – SQL Dev Track: My Session February 19th, 2009

Vinod Kumar

It was really nice to see a whole bunch of people attend my session on “7 things I wish Developers Knew about SQL Server”. On an average I had double the number of attendees when compared to the other sessions on the same track. It is really nice and thanks for attending the same. If you have any specific feedbacks, please drop a line and I will try to answer them. BTW, I know I had less time as far as Q&A is concerned but that is the format of the online event to be precise and crisp. But you have some space here for discussions. BTW, please ask questions relevant to the session and any feedbacks specific for me.

Tags: , ,

This entry was posted on Thursday, February 19th, 2009 at 13:54 and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

5 Responses to “Feb VTD – SQL Dev Track: My Session”

  1. Sathish says:

    Thanks Vinod. The VTD is very useful especially for ppl who are started looking into 2005/2008 from 2000.

  2. Dharmendra says:

    Thanks, it better than last year ‘Train the Trainer Session”.

  3. Balaji Venkateswaran says:

    Vinod, Thanks for your recommendation.  We are very clear about this approach after the session, however we were discussed about keeping the gender column (stores M/F) as part of index; due to its less selectivity.  In my case, we are just storing 0 or 1.  I will implement your comments and see how SQL reacts.

  4. Balaji Venkateswaran says:

    hi, I was part of the VTD session yesterday and alos attended SQL query tuning session in Cognizant few weeks back.  My question is: If we have the column for keeping the status of the row (active/inactive) as bit datatype.  In scenarios, we need to filter based on this column.  I have the index (both clustered and covering) but not on this row status column.  In such scenario, the execution plan shows the bookmark lookup.  Is it a best way to include the column as part of covering index?  Or any other suggestions, please. :)

    Vinod: Balaji, if you attended my session before on Query Tuning then you know the answer to why it did a bookmark. It is be default behaviour. Now you can create a covering index via the INCLUDED columns as part of the non-clustered index.

  5. Balaji Venkateswaran says:

    It’s really a nice session, however we need more tips on SQL server query tuning.

Leave a Reply