Yes, please post solution. Thanks,

Yup, that's the old-style join syntax. I'd recommend converting it to the ANSI join syntax for readability.

Oops my bad, I saw interpreted the underscore in the second table name as a period and thought I saw 4-part naming.

Can you post execution plans (graphical)? That will...

Also check out K. Brian Kelley's tips on MSSQLTIPS.

Fixed Database Roles

Fixed Server Roles

Ah, I always forget about those odd ball time zones. Just like the one in Indiana that doesn't do DST. Good catch!

Looks like you are using a linked server. Are the summed columns on the linked server table? If so, I;d recommend doing this a bit differently so that...

Happens all the time, no worries.

YOu could use the second suggestion, have a GMT offset column that is tinyint. So if your offset is 5 (EST) you'd do DateAdd(hour,...

Ray K (12/21/2009)

---

This actually brings up another thought. Hypothetical situation: let's say my .NET OOP code and my SQL Server reside on different servers. I have a large...

Is it the database file or the log file that is growing out of control?

What is the recovery model of the database?

What is happening in the database when...

I don't think you want to put the criteria in the WHERE clause because that will likely cause the Optimizer to see the LEFT JOIN as and INNER JOIN. ...

Assuming you are using SQL Server 2008 since this is 2008 forum, have you looked at the DateTimeOffset data type? You could use it or you could store the offset...

Jeff,

The OP specifically casts to datetime in the code provided so that's what I ran.

Execution Plans would help here and full table schemas (including indexes), without this information any suggestions like the one I'm about to make will just be shots in the dark...

No problem. Of course I was an idiot and didn't completely read Andrew's post until after I had re-written the whole thing EXACTLY as he had :crying:

I believe you need to run setup from the command line with the SKUUPGRADE = 1 parameter. See this blog post.