SQL Server 2008 Tutorial - Index Essentials!

Why use indexes on your tables in SQL Server 2008? This video describes in graphic detail what performance is like if you do not use indexes. Optimize performance and troubleshoot performance problems.

[EdwardKench]

Thanks for the positive feedback! As a fresh job seeker, I think it's important to take an attitude of differentiation. Don't try to compete on cost, by believing that you can start at lower pay than others with more experience might demand. Figure out what you have done that made you different, perhaps in class, the things that you were better at than others, and emphasize those. Take the route of differentiation instead of cost leadership. Figure out what makes you different and sell it!

[EdwardKench]

@Akiii001 Yes, SQL will add a clustered key to any field(s) used for the primary key. But if those fields are not part of the WHERE clause, then SQL will still do a table scan if other fields that are used in the WHERE clause do not also have an index on them. You should then add non-clustered indexes to any other fields that are used in WHERE clauses. Thanks for the feedback!

[EdwardKench]

@Akiii001 No, that would generally not be a good idea because the maintenance of the indexes would cause a performance hit on the system and usually you won't be using every field in a WHERE clause. It's best to control access to the tables by only allowing stored procedures to query tables and deny any direct ad hoc access. This way there is no need to worry about a field without an index being referenced in a query, because you are fully aware of which fields need indexes.

[sunilraju]

Hi you r dng really amazing job...Can u plz tell me suppose in an interview d HR will ask for fresher job seeker what project u have done and wt r all d things hv u done during d project and wts ur role in d project and wt r all d problems u hv faced in d project....

[BenNitti]

Who is this guy? That's hilarious.

[zreticuli]

Is this Lev Yielmaz's vocal/voice?