We reset the riverbed Wan compresion hardware and it seems to have cleared this up for now. I will need to keep an eye on it but hopefully this...

I had already dropped the miliseconds due to this issue. I agree that I should drop the time stamp however even though all our date fields are defined as...

I added the code for rpt_sp_get_date_range.

The stored proc is not complete. I have hard coded the dates for testing and will add logic so that a frequency (D,W,M,Y) and and offset can be passed.

Here...

3 hours into it I got my first stat of 5% back. There is obviously sonething very wrong but at least I now know it's actually trying to do...

I assume you are referring to the SQL Server current log. It's pretty clean. I see where we had our daily backups done but nothing else.

Checking the server...

Looks like the disk utilization is very high on the DB server so that may be a big part of the problem. I am going to let the current...

Could go either way but it saves some time when doing data validation and allows me to more easily hook it up to BI tools if I can reference it...

Only hitch I ran into was that the CROSS APPLY was joining to a UNION between 2 table which caused my quantities in table 'a' to double up. Not...

Yes to all of the above. We are pretty sure that we need to delete and re-create the outlook user and profile on the server. Our network ops...

Looks like this is an issue between exchange server 2010 and Outlook 2002. Sounds like xp_startmail, xp_sendmail and xp_stopmail do not work with exchange 2010. Still tracking down...

Looks like OUTER APPLY is not supported in SQL 2000 but I did get this to work on a SQL 2008 instance which we will be migrating to soon I...

I really appreciate the feedback on this. I suspected the issue might be scoping of the selection values but was not sure if there was a way around it....