#Datagrip multiple cursors code
#Datagrip multiple cursors windows

I might open that in a different Window, but I tend not to (because I then have to close that window at some point).

#Datagrip multiple cursors code

Instead of a child Sproc I might want to open the source code for a VIEW that is being used. Currently I do that in the same Window, and retain the existing Results (which enables me to find the point in the code where I want to make a change). Open a different, child, SProc and look at that. Now I want to fix the runtime error, or make the darn thing work PROPERLY!! I might get a runtime error too, of course. Each of those Debug statements has a column name matching the SProc Name and a value of 'DEBUG(1)' with a unique ID If I set that to 1 then I get a whole load of extra SELECTs outputting debug info interspersed with the actual output (in the results pane). At some point (either because I'm trying to fix a new problem, or because I've just added a new feature) I run the Unit Test and I get some output in the Results Pane. I open the file containing an SProc that I want to work on. some Unit Tests, and also a bunch of SELECT TOP 10 for the various tables, and JOINs, that enable me to have a quick look at some data, or to modify those 'Sandpit Selects' to change the WHERE to find some 'rows of interest' I don't RightClick & Edit an SProc in SSMS because a) I prefer Files for Version Control and Rollout (to QA and PROD) and b) at the top of each file is an EXEC statement which 'logs' that the script was run (date/time, name, and 'Version')Īt the bottom of each file is a comment with a Test Rig - e.g.

I am guessing that either this is not a problem for other people (they live with it, and have never considered how 'expensive' it is), or they just don't work like that (in which case this Old Dog could definitely learn a New Trick)īackground: I have each SProc, Trigger and View in its own file. but right now I'm really struggling with the amount of time it seems to be taking me just to work, in a practical sense, with only half-a-dozen-files.

#Datagrip multiple cursors windows

Part of that is the full-path style that SSMS appears to adopt (compared to QA) - which means that pop-up lists of WINDOWS don't show me enough - its like trying to manage a rocket-ship through a letter-box!īeyond that, I have some imagination that there will be lots of Tools that will help productivity. working out which ones I'm still needing, and which ones are now redundant) and I've always wound up with lots of TABs and found it a chore to close them (i.e.

I have used SSMS a bit, when on client site or Remote Connected to a server etc. My initial issue is trying to get a working environment / IDE that I am comfortable with.