Symptoms
Assume that you create a local stored procedure that calls a remote stored procedure on a linked server through an EXECUTE statement in SQL Server 2019. When one of the remote stored procedure parameter values is a system variable (@@servername, @@servicename,...) like in the following example:
create procedure test
as
begin
execute [myLinkedServer].[myDB].dbo.myproc @@Servername
end
An access violation may occur. Additionally, you may receive an error message that resembles the following:
Msg 596, Level 21, State 1, Line LineNumber
Cannot continue the execution because the session is in the kill state.
Msg 0, Level 20, State 0, Line LineNumber
A severe error occurred on the current command. The results, if any, should be discarded.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Resolution
This issue is fixed in the following cumulative update for SQL Server:
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
References
Learn about the terminology that Microsoft uses to describe software updates.
