BUG: @@OPTIONS Does Not Revert to Pre-Procedure Setting

• Microsoft SQL Server version 6.5

SYMPTOMS

If the SET statement is used inside a stored procedure or trigger to set an option, it will revert back to its former setting properly after the stored procedure or trigger execution is completed; however, the @@OPTIONS global variable remains set.

For example, if you execute sp_helpdb, which sets NOCOUNT on, and check @@OPTIONS after that, the output will show 512 for NOCOUNT although the message stating how many rows were affected by the statement will be there.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5.

Additional query words: golden sp1 sp2 sp3 sp4 sp5 st proc sproc sp

Keywords : kbbug6.50
Version : winnt:6.5
Platform : winnt
Issue type : kbbug