Recently I ran into some interesting bug that I haven't yet found any reference to. The environment is: Server1 (REL) running SQL Server 2K SP3, Server2 (CRM) running SQL Server 2K SP4. Each server is connected to another one via linked server. While connected to REL, I need to execute stored procedure on CRM that in turn goes to REL and extracts some data (usually it runs in a job, but sometimes I execute it manually). On my computer I have both SQL Server 2005 and SQL Server 2K client tools. When I open SQL Server 2005 Management Studio on my computer, connect to REL and execute the stored procedure (
EXEC CRM.[db_name].[owner].[sp_name] @param1), server returns all the output messages by which I know that the procedure actually ran till the end, but after last message I see the following:
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Very informative, isn't it? Verification shows nothing unusual, looks like the procedure did all it has been intended to do. But the really curious thing is that executing the same command from Query Analyzer of SQL Server 2K doesn't produce any error message at all - the procedure just finishes succesfully! Executing the procedure from a job also doesn't produce any error notifications. Looks like Query Analyzer gets right output this time while Management Studio has some bug in it. All I have been able to find about the error message has nothing to do with my case. It refers to a case when stored procedure is executed on SQL Server 2005 that previously has been upgraded from SQL Server 2K (
BUG #: 412387).