You think?? :hehe:

The image data type is a BLOB type. It stores a 16 byte pointer in the data record that points to the first data page that holds the image...

From the tests I had the OP run, the GROUP BY and SUM are not needed.

I believe he has the solution.

😎

Well, I think that partially explains why I don't have the issue. I am an administrator on our servers. I can't think of anything other than what Microsoft...

That too....

I'm thinking that the GROUP BY is irrelevant and that what is needed inplace of the CASE WHEN SUM(v.PurchaseAmt)/15000 < 0 ... is this

FLOOR(v.PurchaseAmt/15000)

😎

Please explain this code snippet:

,CASE WHEN SUM(v.PurchaseAmount)/15000 <= 0

THEN 0

ELSE...

Now, take out the group by clause and rerun it. does it still work, does it return the same result set?

does the following work in SSMS, and if so what is the result, if not the error message.

SET @ConsultantID = '0000344'

SET @StartDt = '11/01/2007'

SET @EndDt = '10/31/2008'

--

SELECT

...

Using a SQL Server backend for your application, any individual or group with system administration privledgs is going to be aboe to see your database structure and the data stored...

Plus, it looks like the value you have being returned is not <= 0.

Not from the code snippet. How about all the code, that may help in understanding what the query is doing.

😎

Is that the actual code from the stored procedure or is that from a trace?

It might be better if you provided the code for the entire stored procedure, we might...

Since it looks like you are doing a delete tmpTable, also try changing that to truncate tmpTable.

😎

I think keeping or dropping the clustered index also depends on how the data is coming in. If the incoming data is already sorted based on the clustered index,...