April 29, 2024 at 12:00 am
Comments posted to this topic are about the item Exporting and Importing Registered Servers in SSMS
April 29, 2024 at 7:20 am
And that's why there are central management servers and Powershell...
April 29, 2024 at 12:27 pm
There are at least 2 big advantages to using a Central Management Server instead of locally managed Registered Servers.
The only disadvantage I've found is that some connection properties don't get saved to the CMS repository - especially "trust server certificate" and "encryption =". They seem to work at first but if you restart SSMS, they are gone. MS broke this in SSMS 20 and probably on purpose as part of their ill-considered push to force every connection to be encrypted. For an on-prem network, that is completely unnecessary. For those of us who use a CMS with 100s of servers registered in it, we now have to install valid certificates on every server, or stop using CMS. Thanks Microsoft.
At least locally registered servers preserve those settings between restarts. CMS does not. 🙁
April 30, 2024 at 8:06 pm
When migrating to a new computer, there's a useful post out there how to de-hash the pw to clear text on source and re-hash once copied to the new computer. Saves the hassle of typing in pw for each registered server.
April 30, 2024 at 8:17 pm
And that's why there are central management servers and Powershell...
agreed, the deployment of a central management server provides this list centrally for all users, adding warehousing capability and harvesting of sql instance and database info provides a central reporting point too
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply