MS SQL Server Performance and tuning

I have a stored procedure that I need t have tuned...  It takes about 3 seconds to return the Rows...  According to the "BOSS" at my compaany... that's too slow...  There are other SPs that make up the page that this is attached to.  All in All the whole page takes about 11 seconds.  This SP is the most complex.

The proc is below....

      SELECT, p.project_name, p.project_Manager, p.project_Manager_email, p.project_start_date, p.project_end_date,                   
            COUNT(DISTINCT as TTLstaff,
            DATEDIFF(day,getDate(), p.project_end_date) AS DaysRemain,
            COUNT(DISTINCT d.deliverable_id) as lateDelivs,
            COUNT(DISTINCT t.task_id) as TTLTsk,                               
            COUNT(DISTINCT s.issue_id) as TTLIss,
            COUNT(DISTINCT rx.risk_id) as TTLRsk           
      FROM projects p, project_intermediate pi                      
            LEFT OUTER JOIN resources r ON ( = AND r.assigned = 1)                               
            LEFT OUTER JOIN deliverables d ON ( = AND
                  (( getDate() > d.due_date
                        and d.date_submitted IS NULL )
                                    ( d.date_submitted > d.due_date
                                          and d.date_submitted IS NOT NULL )))          
            LEFT OUTER JOIN tasks t ON ( = AND t.spid IS NULL                              
            LEFT OUTER JOIN issues s ON ( = AND s.spid IS NULL                               
            LEFT OUTER JOIN risks rx ON ( = AND rx.spid IS NULL           
      WHERE pi.user_id = 'XXX' AND =
      AND p.inactive = 0 AND pi.spid IS NULL  
      GROUP BY, p.project_name, p.project_Manager, p.project_end_date, p.project_Manager_email, p.project_start_date, p.project_end_date  
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

how many tables you are joining here, and how many fields each table have and how many records?
create views for the tables u are using in this query with only the needed fields for this query. Then use those views in this query instead of querying the tables directly.
This is a really wide subject and there can be several optimizations can be done to this query. But by just looking at your query it is hard to say what to do without knowing your schema, data and your business requirment.

But as a startup you can look at your query plan and see which part of the query is more costly. Then try to create indexes on columns used in WHERE clause and JOIN statements. For this you can use the Database Engine Tuning Advisor to get index recommendations. (

Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

Alpesh PatelAssistant ConsultantCommented:
That does not make any difference.
pborreggAuthor Commented:

With respect to the number of tables...There are 7

The number of fields... There are 12

Number of rows...So far, less than 20.

When I break up this SP into smaller chunks, the time taken to get back the data is less than a second.

Is there a way to daisy chain to the smaller selects, one after another, to get the same result?

Yes, making VIEWs is something I've considered.  I'm currently working on that...

Thanks all for your input so far...

I ran an execution plan and boy oh boy... there is a cost doing those joins...the CPU is being tasked, in milliseconds, but some are only .000001 and others are .03434524 for example.

12 fields not a problem I believe. But if its large no of fields table like 50/60+, then at that time creating this kind of view surely help (Also the volume of data). I faced it and solved like this.

Go ahead and check for views in yours whether it helps or not.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
pborreggAuthor Commented:
Are the number of Left Outer Joins causing a problem?

I've got indexes on all the columns I'm querying.

I've got to solve this problem and fast.  My boss is furious that this query takes so long to process.

if i can get a the structure of your tables without any records , i can construct this query in an entire different manner.  
pborreggAuthor Commented:
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.