For example, if I know that one of my previously opened tabs contained scripts for setting up Extended Event sessions within Azure SQL Database, I can simply type session in the search window: I also get the ability to search across these tabs.

This allows me to track down previously opened tabs, even if I didn’t save them. By clicking on Closed, I get a list of all the tabs going back in time that I’ve had open on this SSMS instance: This shows the tabs currently open, but you can see that there is a listing under All tabs for closed tabs. You can use the keyboard shortcut designated above, Ctrl+Q, or you can use a button installed on the button bar to get a history of the tabs you had open in your SSMS environment: There is also a literal history of the tabs on your system. Tab history can also reconnect the tabs to the databases they were connected to prior to closing them. Further, if you didn’t save that tab, no worries because tab history has all the T-SQL code, just as it was before you closed it, covering for you in the event of a problem. Reopening your tabs helps ensure that you see the same work as you did when you closed it. Once it’s enabled, you get a number of behaviors that can prove extremely helpful.įirst up, you can restore on launch all the tabs you had open when you last closed SSMS. You can enable or disable tab history according to your own preferences. Take a look at the Options for SQL Prompt and you’ll find a set of options under Tabs > History: SQL Prompt can help with both these problems. It’s also easy to get rid of tabs and scripts that you later wish you had back. It’s sometimes too easy to close SQL Server Management Studio (SSMS) without saving your work.

Sql tabs select all from databsae