Execute Procedure GUI issues after manipulating the Object Explorer tree (2 ways)

Execute Procedure GUI issues after manipulating the Object Explorer tree (2 ways) by Jon Seigel

Closed

as Won't Fix Help for as Won't Fix

Type:	Bug
ID:	777432
Opened:	1/24/2013 11:40:12 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

See repro steps.

Scenario 1 doesn't crash Management Studio, but you do have to open a new Execute Procedure window and copy over all the parameter settings.

I tested both scenarios in 2008 R2 and 2012 Management Studios with the same result.

Details (expand)

English

SQL Server 2012 SP1

Tools (SSMS, Agent, Profiler, Migration, etc.)

Windows 7 Enterprise

US English

1. In Object Explorer, go into a database and expand the Stored Procedures node.
2. Right-click a stored procedure and select Execute Stored Procedure. (Opens the Execute Procedure GUI)

Scenario 1:
3a. Refresh the Stored Procedures node in Object Explorer either by (a) right-clicking the node and selecting Refresh, or (b) selecting the node and using the toolbar button.

Scenario 2:
3b. Either drop the database, or disconnect from the server in Object Explorer.

4. In the Execute Procedure GUI that opened previously, click OK as if to execute the procedure (parameters don't matter).

Scenario 1:
Error message pops up: "Object reference not set to an instance of an object. (SqlMgmt)" The user must cancel to dismiss the dialog box.

Scenario 2:
No error, but the resulting script window is automatically connected to the server-in-context (with prompt if there isn't one), and executed on that server.

Scenario 1:
No error; a script window opens with appropriate code, and the procedure is executed.

Scenario 2:
The script window should connect to the original server, not the server-in-context (which could potentially be very dangerous).

0 attachments

Hi!,

Thank you for reporting this bug. We took a look at this bug and triaged it against several others and unfortunately, it did not meet the bar to be fixed and we are closing it as 'won't fix'.

Regards,
Sanjay Nagamangalam, SQL Server Manageability