|    Register
 
About TMQ

The owner and DBA doing the work will be Jason Massie. He has 8 years experience as a DBA and has specialized in performance tuning for the last five. Jason has spoken at the Professional Association of SQL Server Conference, the North Texas SQL Server Users Group and is scheduled to speak at SQL Connections in Orlando this Spring. He has a technical blog at http://statisticsio.com

Jason has the following certifications:

  • Microsoft Certified IT Professional Database Administrator (early adopter)
  • Microsoft Certified IT Professional Database Developer
  • MCDBA (7.0 and 2000)
  • MCSE
  • MCSD

You are here  :   Order
Tuesday, November 18, 2008
We are very confident in our tuning methodology. If for some reason that we cannot provide gains, we will provide a full refund so there is no risk to you.
Directions

1. Go through the check out.
2. Send query, schema, and query plan per our instructions.
3. We will send a script with optimizations.
4. Follow our implementation instructions.
Your tuning Order

The normal price is 59.99. There is a 25% discount until 01-15-2008. Order now and be fast within hours. Optionally, you can choose to have the tuning expedited.

TMQ Query Tuning $45.00
Expedite(optional)
 $15.00

 

Options

Questions?
End to end SQL Server performance tuning

Do you need more than tuning a single query?

Our sister site can help. Visit now.


You Need to Upgrade Your Flash Player
You Need to Upgrade Your Flash Player
How it works
  1. Identify what query is slowing down your app.
  2. Send us the query, schema, and the query plan.
  3. We send you an optimized query and/or index changes.

That's it! Our process is simple, fast, and cost effective.


Expedites

An expedite is a rush order. We have a 120 minute or less resolution time commitment on expedites. Normal orders may take as long as 24 hours. If we cannot complete the expedited order within 120 minutes, we will refund the expedite fee. The expedite fee is only $15.


Your Query

This section is for the query you need tuned. Please paste the entire SQL statement or stored procedure code. If you need help identifying the query, please refer to our FAQ.


Your Schema

We need the schema for all objects involved in the query we are tuning. You can generate this through enterprise manager or SSMS. This includes the create statements for the tables, view and\or functions as well as indexes, constraints and triggers. Please refer to instructions in our FAQ. We also have a screencast video demonstrating this. We may also need the data or a subset of the data but we will let you know and provide scripts for extracting it.


Query Plan

We need the xml plan for SQL 2005 or the text based showplan on SQL 2000. We have instructions on gathering this info in our FAQ.


Name
email
Feedback
SubmitCancel

select r.cpu_time

                ,r.logical_reads

                , r.session_id

into #temp

from sys.dm_exec_requests as r

 

waitfor delay '00:00:01'

 

select substring(h.text, (r.statement_start_offset/2)+1 , ((case r.statement_end_offset when -1 then datalength(h.text)  else r.statement_end_offset end - r.statement_start_offset)/2) + 1) as text

                , r.cpu_time-t.cpu_time as CPUDiff

                , r.logical_reads-t.logical_reads as ReadDiff

                , r.wait_type, r.wait_time

                , r.last_wait_type

                , r.wait_resource

                , r.command

                , r.database_id

                , r.blocking_session_id

                , r.granted_query_memory,r.session_id

                , r.reads

                , r.writes

                , r.row_count

                , s.[host_name]

                , s.program_name

                , s.login_name

from sys.dm_exec_sessions as s inner join sys.dm_exec_requests as r

on s.session_id =r.session_id and s.last_request_start_time=r.start_time

left join #temp as t on t.session_id=s.session_id

CROSS APPLY sys.dm_exec_sql_text(r.sql_handle) h

where is_user_process = 1

order by 2 desc

 

drop table #temp

select total_worker_time/execution_count as AvgCPU

, total_elapsed_time/execution_count as AvgDuration

, (total_logical_reads+total_physical_reads)/execution_count as AvgReads

, execution_count

, substring(st.text, (qs.statement_start_offset/2)+1, ((case qs.statement_end_offset

when -1 then datalength(st.text)

else qs.statement_end_offset

end - qs.statement_start_offset)/2) + 1) as txt

, query_plan

from sys.dm_exec_query_stats as qs

cross apply sys.dm_exec_sql_text(qs.sql_handle)as st

cross apply sys.dm_exec_query_plan (qs.plan_handle)as qp

order by 1 desc

Query Tuning FAQ

 

How much does it cost?

Answer:
We charge $59.99 for tuning a query but until 01-15-2007 the price is discounted 25%. There is a money back guarantee if we cannot provide a gain.

What if I need multiple queries tuned? Do you offer a bulk package?

Answer:

Email us if you have 5 or more queries that need tuning and we will give you a quote. If you need more than that tuned, we suggest you you look into the services of our sister site, http://sqlvelocity.com. They do a total package tuning engagement.

How is payment made?

Answer:

Our checkout is through paypal. However, we can make other arrangements.Email us.


Are there queries that you cannot tune?
Answer:

There is a possibility that it is as optimized as it is going to get but we have not come across that yet.

There is always a way to take it to the next level. However, the work it may take would be prohibitive. Queries requiring complete redesigns and implementation of new features fall into this category. We will provide other options though. One option will be a refund.

For example, you may submit a query that is optimally index and the query is well designed but you need it to go faster. After we determine that it is optimally tuned, we may see that partitioning or a faster disk subsystem could help. We will provide this info and a refund. We may also be able to work out a custom quote to enable the partitioning or migrate the data to the faster drive or recommend a partner.

How can I identify queries needing tuning in SQL Server 2005?
Answer:

We can get this info 3 different ways. We can get the worst performing queries that are currently executing with this query. You can get semihistorical poor performing queries with this query.

You can also get this info from a SQL trace.

How do I find queries that need tuning with SQL 7.0 or SQL 2000?

Answer:

Before SQL Server 2005, a SQL trace is the only practical method. Please contact us if you need assistance with this
Copyright 2007 by Tune My Query     |    Privacy Statement    |    Terms Of Use