The method I used for a similar issue to the OP about a year ago was to build up the OPENQUERY() call inside a dynamic statement. Something along the...

In my own opinion, and as a standard I've seen in many different environments, I'd prefer the same name in all environments. This allows you to write scripts that...

SQL Server by default will attempt to use all (except for a few hundred MB) of the memory on a server. Given that it's up to 7.4 GB, we...

What exactly do you mean by a "flatfile" database backup? Are you referring to just copying the .MDF and .LDF files to a different location?

If so, then the biggest...

A major difference between your development and production environments could be CPU resources, specifically the number of cores. It's possible that in production the Maximum Degree of Parallelism has...

Jeff Moden (8/30/2009)

---

You certainly had the right idea. Just so you know, though... Since you were striving for a 2k solution, be advised that spt_Values only has 0-255 contiguous...

Whoops, I mistakenly thought that spt_values was accurate up to 32K instead of 2048. I should have double-checked that one. The error will manifest as a problem if...

I'll do it, because I just love writing SQL Server 2000-compatible code without using temp tables 🙂

DECLARE @StartDate datetime, @EndDate datetime

SELECT @StartDate = '2009-08-01', @EndDate = '2009-08-30'

SELECT Periods.SalesHour, ISNULL(Sales.SalesAmount, 0)...

It sounds like AWE hasn't kicked in. Have a look in the ERRORLOG to see if there's an "AWE Enabled" message near the start.

You've mentioned configuring AWE Enabled with...

See if management will change their requirements? 😉

We've passed...

To do this, you'll need a list of all...

It sounds like you're using SQL Server 2000 - I have the same problem running my query under SQL Server 2000. Try this instead, which should work with either...

The only way you should get that error is if the "CONVERT(varchar(13), SalesDT, 121)" part used in the SELECT clause is different from the value used in the GROUP BY...

What was the error? I'm guessing a conversion error, but the following code block works for me:

CREATE TABLE #Sales (SalesDT datetime, SalesAmt money)

INSERT INTO #Sales (SalesDT, SalesAmt) VALUES ('2009-08-28...

You could try converting the datetime to a varchar(13), and grouping by that, with a result like '2009-08-28 13'.

SELECT CONVERT(varchar(13), SalesDT, 121) + ':00', Sum(SalesAmt) AS SalesAmount FROM Sales

WHERE SalesDT...