We’re going to do that with the help of the SQL Server Power Shell module.
I suppose from the log the failures are: - Get DPLocations failed with error 0x87d00215 - Failed to get DP locations as the expected version from MP 'KK14local'.
Error 0x87d00215 Double check your site boundary settings and make sure you can ping the DP server name from the computer that you are pushing the client install to.
But there’s a better way: you can import all that saved information right into SQL Operations Studio, and it’s pretty painless, too. In this shell, just like VS Code, when you want to change or add a setting, you don’t do it in the defaults, you set them in your personal settings file, which is the panel on the right.
Buckle up, because this involves a little knowledge of how settings are saved in Operations Studio, and how we can quickly get saved connection information out of SSMS and into your new application. Like I mentioned in my last post, changing settings in SQL Operations Studio requires you to modify a text file. To pull up your settings, either click “File - Settings” or use Control-Comma (,) on your keyboard (Note: keyboard shortcuts are king in both VS Code and SQL Ops Studio, I’d recommend practicing). Essentially, if you want to override a setting, you find it in the left panel, and copy/paste it into your settings, which trumps the defaults.
Even then, if we could aggregate it, that’s still a lot of manual work. This functionality makes it easy to add things into your existing settings once you have them loaded.
Now we need to get our registered servers from SSMS.
It’s a smaller install, it’s pretty snappy, and the interface is way cleaner and easier to manage (and officially supports dark themes).
There’s built in source control and support for extensions. Not yet, though; there’s still a lot to work out, like the fact that it can’t give you actual execution plans (just estimates) and other things.
The settings are saved in JSON format, which is nice and easy to work with as a key:value pair.
If you were to add connections through the UI, they get added to your settings file and here’s a sample of what it would look like: Inside your settings file, two new sections get created.
In case you didn’t notice, I’m already in love with SQL Operations Studio.