Download - Natural Born Killers, Performance issues to avoid

Natural Born Killers, performance issues to avoid

Richard Douglas

2 Natural Born Killers

Natural Born Killer

http://www.flickr.com/photos/merille/4747615138/sizes/z/in/photostream/


Source: http://cheezburger.com/View/5939764992


Adhering to best practices?

http://www.flickr.com/photos/12693492@N04/1338123903/sizes/m/in/photostream/


Your host

• Richard Douglas

• Systems Consultant

• SQL Server MCITPro

• Maidenhead SQL User Group Leader

• Blog: http://SQL.RichardDouglas.co.uk

• Twitter: @SQLRich

• Email: [email protected][email protected]

http://sql.richarddouglas.co.uk/

mailto:[email protected]





Agenda

• Statistics

• Table Design

• Scalar UDF’s

• Indices

• Key lookups

• Sargability

• Table variables

• Parameter sniffing


Statistics

• SQL uses a cost based optimizer

• Costs influenced by statistics


Statistics

• Creating Statistics– Automatic

– Manual

– CREATE STATISTICS

– sp_CreateStats

• Updating Statistics

• Sp_UpdateStats

• UPDATE STATISTICS

Permanent Table Temporary Table

1st record 1st record

- 6 records

LT 500 recs, 500 changes LT 500 recs, 500 changes

GT 500 recs, 500 changes + 20%

GT 500 recs, 500 changes + 20%


Table Design

http://www.flickr.com/photos/aresauburnphotos/2699269321/sizes/o/in/photost

ream/


Example of bad design


Example of a better design


Table Design – Size comparison


Good table design benefits

• Minimise the CPU overhead.

• Increase the number of records in the buffer cache.

• Reduce the amount of physical disk IO.

• Reduce the amount of network traffic.

• Reduce the data file size(s).

• Reduce the working size of the Transaction Log.

• Reduce Full/Diff /T-Log backup file size.Thereby increasing your ability to deliver your RTO.

• Keep transaction time to a minimum.


Scalar User Defined Functions

• The Good– Re-Usable code

• The Bad– Runs once per record in record set

– They don’t take advantage of parallelism

– They use Nested Loop joins regardless

• The Ugly– So ugly it’s hidden from the query plan and IO statistics


Scalar UDF Solutions and Alternatives

• If you have to use them:– View the actual IO usage in Profiler

• If you can replace them:– Look at Table Value Functions

– Look at CLR


Indices


It’s all about DWI knowledge:

Indexing strategies

D W Ia

t

a

o

r

k

l

o

a

d

n

t

e

r

n

a

l

s


Bad example; Surname, Firstname, Middle Initial

Golden Rules for Clustered Indexes

• Narrow

• Static

• Progressive

• Unique

• Fixed width

• Not Null

Impacts nonclusteredindexes

Fragmentation

Space impact

This example will have 13 bytes of overhead alone;

• 4 byte uniquifier

• 2 byte variable offset + 6 bytes for variable length fields

• 1 byte for NULL values and NULL bitmap


Golden Rules for NonClustered Indexes

• Have an optimal clustered key

• Not narrow

• Reduce unnecessary overhead

– Fixed Width

– Not null

• Consolidate

• Index foreign keys


Key Lookups – The silent killer


Sargability

• SARGable – “Search ARGument able”

• T-SQL functions around a predicate can break SARGability

• Some caveats to remember


Table Variables Vs. Temp Tables

Table Variables

• Fast when used with small data sets.

• Have a limited scope

• Use less locking and logging resources than temp tables– http://sql.richarddouglas.co.uk/archive/2011/06/rollback-gotchas-

part-2-2.html

• Estimated statistics always show 1 record

• Cannot be altered after they are declared

• Mythbuster - MAY be memory only, this isn’t guaranteed

• Generally faster with smaller data sets

http://sql.richarddouglas.co.uk/archive/2011/06/rollback-gotchas-part-2-2.html










Table Variables Vs. Temp Tables

Temp Tables

• Uses statistics– Stat population will cause recompiles (statement level in 2005 +)

– Can create better plans

• Wider scope

• Can be rolled back

• Can be altered after creation

• Generally faster with larger data sets


Parameter Sniffing

• What is it?– It’s all a matter of statistics

• How do I know when it will affect me?– Monitor the IO and CPU

– This means baselining your environment

• What are my options?– Rewrite dynamic queries

– Query Hints:

– WITH RECOMPILE

– OPTIMIZE FOR

– Plan Guides


Demos


Summary

• Statistics

• Table Design

• Scalar UDF’s

• Indices

• Key lookups

• Sargability

• Table variables

• Parameter sniffing

32 Dell SoftwareUnderstanding Indices

Any questions?

Thank you

[email protected]@SQLRich

http://bit.ly/11jr4fC

Download - Natural Born Killers, Performance issues to avoid

Top Related