Till SQL Server 2008 R2, if you want to change the database on which you would like to execute a SQL query in SQL Server Management Studio (SSMS), the keyboard shortcut to do so was CTRL + U from the query window.
Now from SQL Server 2012, it is CTRL + ALT + J.
So those who tried this using the old shortcut, keep in mind that the new shortcut.
Have you ever opened a standard GP stored procedure?
I do it at least on a weekly basis and have always found it impossible to read as it is. So I end up aligning the procedure first and then read it to understand the logic.
Not anymore. David has shared information on some portals which does this in seconds and give us an aligned code.
Standing out from his list is Poor SQL, from what I learned from my usage.
And there is a plugin for SSMS which does this from within SSMS. This tool is called SSMS Tools Pack.
In spite of having more critical deliverables for today, I still wanted to post this article, because of it’s importance.
This particular issue is no less than an acute pain. And I mean it.
In SQL Server Management Studio, from versions 2005 till 2008, there is an option called “Auto Recover” which triggers a process that save whatever we are writing in the Query Editor… every 5 to 10 mins. And that’s real pain for us, especially if we are working on remote or thru’ internet.
Sometimes, the system gets hung for so long that you would sit in front and wait till it “recovers” from the “recovery” itself.
BUT, there IS a solution which is unsupported by Microsoft SQL Server team, but harmless and effective. There is a registry entry called “AutoRecover Enabled“, which by default is set to 1. We have to change it to 0. This will not trigger that painful process anymore.
Do a find in Registry Editor for the above option, and you would be able to see that.
References for this solution:
We are thru’… Enjoy a Hang-Free SQL Session…!!!