defyant_2004 (12/16/2013)
We really want to protect the server and limit the amount of unnecessary access. Although I am not an expert at DBA work, I have used SSMS in the past and it seems to provide everything our DBAs should need to maintain our SQL Servers without logging onto the server itself and messing things up. We have a 90% uptime we must keep. We also want to prevent any risk for corrupting our Windows Server installations.
From your original question, this and other of your replies in the thread it seems you have simple SQL set up and your DBAs are very limited in what they are able to do. It also sounds like they would like to do more and improve the service they provide. You say yourself you are not an expert in DBA work, and using SSMS in the past is no qualification and does not give you an insight into the full range of DBA work.
Talk with your DBAs, either give them RDP and lay down ground rules or provide them remote alternatives so they can do more without having to refer to others all the time. Really I cannot see what things they would 'mess up' if they are professional.
Are any of your database related files large? Having to move those between drives or servers whilst remote involves two hops and is unnecessarily time consuming.
---------------------------------------------------------------------