The SSMS team at Microsoft finally decided to remove the constraint that allowed only extensions with whitelisted package ids to be loaded into SSMS. Now you just develop your extension and it just works. Will be using Visual Studio 2017 this time around Because the updated SSMS 18 is now based on the VS 2017 Isolated Shell.
The process for extending older versions of SSMS should be similar though. Background All I wanted was to create a simple SQL Server Management Studio (SSMS) extension to simplify what was already a simple action that I repeat a couple of times a week. I thought, how hard could it be… it’s just a simple action.
For years I’ve been using excel or dynamic SQL to generate SQL scripts to do data loads and updates and to generate IN predicates . For a small number of rows or values this is quicker than importing the required data into SQL Server. A few days ago I idly wondered how difficult it would be to create a SQL Server Management Studio extension to do these jobs directly in SSMS. The answer was ...
It also provides us with the named pipe that we can use to connect to the server instance using SSMS (Sql Server Management Server). However to connect to this database using Visual Studio, you need to use the instance name.
The downside I felt about SSMS is that it is available for free till SQL Server 2008 R2. SQL Server 2012 onwards, one need to purchase a license of the same. I feel if we use both of these of the mentioned features, we can reduce the chances of making mistakes while running the same query on Multiple Servers or Multiple Databases.
5. Disconnected Development The new SQL Server Object Explorer lets you connect to and interact with any database right from inside Visual Studio. But SSDT offers a great deal more than a mere replacement for the connected SSMS experience. It also delivers a rich offline experience with the new SQL Server Database Project type and local database runtime (LocalDB). Actually this is one great ...
Indeed, SSMS is alive and well in SQL Server 2012, and it continues to serve as the primary management tool for database administrators who need to configure and maintain healthy SQL Server installations.
