asked on Hwo to cache proc to avoid warnings?
I have two SQL 2000 databases, one my dev and one a client's. On mine, if I execute a proc with some parameters, the first time I get some warning messages but the second time with the same params I don't. On the client's, I get the warnings every time. The warnings themselves can't be suppressed but why does one cache and the other not?
Microsoft SQL Server
Last Comment
JDSX
Why don't you post the warnings that you get?
ASKER
This is an example of the warning:
Warning: The table '#group_summary' has been created but its maximum row size (8469) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
I know why I get it, I don't want to suppress it. In fact I don't think it's even possible to suppress it. What I want to know is why in one database this error only appears at the first execution and in the other database it appears every time. Thanks.
Warning: The table '#group_summary' has been created but its maximum row size (8469) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
I know why I get it, I don't want to suppress it. In fact I don't think it's even possible to suppress it. What I want to know is why in one database this error only appears at the first execution and in the other database it appears every time. Thanks.
Are the service packs the same between the two machines?
ASKER
No. The one that doesn't repeat the warning has SP4, the other is SP1. Was there something released in a service pack to affect this?
ASKER
Actually I take it back, I read it wrong. Here's the @@VERSION output:
--Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
--Microsoft SQL Server 2000 - 8.00.2187 (Intel X86) Mar 9 2006 11:38:51 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
The first is the one that doesn't repeat.
--Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
--Microsoft SQL Server 2000 - 8.00.2187 (Intel X86) Mar 9 2006 11:38:51 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
The first is the one that doesn't repeat.
If I were a betting man, I'd bet that was your problem....
ASKER
I'll update the first and see what happens.
ASKER
It's not the service pack. I hate working with ASP because there's no apparent way to handle recordsets containing these unsuppressable warnings.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.