||SQL Server Tips by Robin Schumacher
A number of database gurus are beginning to sound the alarm about a
new type of SQL-related problem, one that has been given the name,
system waste. Just what is system waste? The definition is any code
run on the database server that does not add value to the business.
Experts claim there is a lot of code being run in database-driven
applications that does not, for example, cause purchase orders to be
printed faster or deliver customer information to online users any
better. It is code that simply uses up CPU cycles and competes for
I/O resources that true business-related logic could take advantage
Such code can be difficult to find, but there is definitely value in
going through the exercise. Eliminating code that runs very fast is
still worthwhile because the most efficient query will always be the
one that has not been run or has to run!
Back up for a moment and return to the issue at hand; how to perform
SQL workload analysis in general. There are some global factors to
consider when using this method. The next section will begin with
global factors. It will then move into capturing and examining
individual SQL statements and stored code executions.
The above book excerpt is from:
High-Performance SQL Server DBA
Tuning & Optimization Secrets