Modifying MS SQL Stored Procedure

[Robin-Britz]

Firstly, thanks @dbeaver for the epic app and all the effort!
I'm really enjoying this a lot over SQL Server Management Studio! <3

Goal I want to achieve:

1. Modify Stored Procedure - preferably in 1 step to instantly open SQL Console with the correct DB selected (in SSMS you right click the Stored Procedure, right click > modify > good to go)

In DBeaver I am doing the following to just modify a stored procedure, it's quite a few steps:

1. Find the Stored Procedure I want to modify on the desired DB
2. Right Click > View Procedure (or F4)
3. On the tab that opens on the right > click "Source" to view the Stored Procedure "code"
4. On the bottom right > click "Open in SQL Console" to edit the Stored Procedure
5. It opens in dbo@master by default - I use the dropdown at the top to select correct DB (even though I did step 1)

Can I setup a shortcut somehow to even just open the stored procedure in SQL Console instantly?

[E1izabeth]

It sounds like a good idea. Could you create an issue with this use case?

Currently I can propose you to use Open Database Object dialog. Maybe you will find the procedure faster, if you know the name

[barryseymour]

I have this issue as well. Your suggestion works, and is fast, but it doesn't open the source code in a standard query window. There's no option to include a USE statement, or to use CREATE OR ALTER procedure.

You could take a cue from SSMS in this regard.

[AP-Kitsu]

It sounds like a good idea. Could you create an issue with this use case?

Currently I can propose you to use Open Database Object dialog. Maybe you will find the procedure faster, if you know the name

I think something like SSMS creating a query with ALTER already written is just much faster

[chad-k12lift]

Came here for this exact same reason. Would love a more streamlined way to handle altering stored procedures in SQL Server.

[gciapparelli]

I found this thread and lost all hope... after two years, no news :-(
DBeaver is amazing, but it's really annoying for those of us who constantly develop on its foundation to go through the difficult path to perform a simple task like modifying a procedure.

Is this behavior unique to MS SQL Server?