I have found that it is faster to call stored procedures across a linked server than to do a direct table select. You may want to try encapsulating you...

Yeah you are missing something obvious. You are joining on c.PR_PER_ADDR_ID and I think you want b.PR_PER_ADDR_ID. Check out the bolded code, I also italicized the aliases in...

You can run the trace using Profiler 2005 and the TSQL_Replay template and you should be fine.

Check out this for an interesting answer to the DB problem:

http://www.sqlnewsgroups.net/group/microsoft.public.sqlserver.server/topic6085.aspx

According to the documentation...

Did you use Profiler 2000 or 2005? In Profiler 2005 you need to use the TSQL_Replay trace template at a minumum in order to replay a trace.

Another thing to...

You can create a package and then re-use it by using the Execute Package Task.

I'm pretty sure this will work:

[font="Courier New"]SELECT

   SUM(OL.QuantityShipped) AS qty_shipped,

   SUM(ISNULL(QuantityReturned, 0)) AS qty_returned

FROM

   T_OrderLine  OL LEFT OUTER JOIN

   T_ReturnLines RL ON

       OL.OrderLine = RL.OrderLine AND

       RL.ReturnDate BETWEEN '2008-08-23'...

Do you have a NULL? Check for NULL using Dataset!Field.Value Is Nothing. I'd do this in your case:

=IIF(LEN((ReportItems!LocalBallots.Value &

ReportItems!CountyBallots.Value & ReportItems!CountyBilling2.Value).ToString().Trim) <> 0 AND

ReportItems!CountyBallots.Value<>"0", ReportItems!CountyBilling2.Value*2, "")...

What's your storage situation? Is tempdb on it's own drive array?

Normally you would have at least a development environment and a production environment and when you have tested all your changes you load the production data into the development database...

Do you mean you want 1 query to return all your results or 2 queries (queries 2 and 3 joined)?

Pretty good Bob, I wonder if you can make the podcast:D

If you are receiving the data as a parameter why can't you...

Sorry this is my bad. I answered incorrectly in the first post. You can use the NULLIF command, but in SQL by defualt NULL never equals anything including...

Yes that looks okay.

You can create a DTS package that runs the procedure and saves to a file and then schedule the DTS package in SQL Server Agent.