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

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.