Pros and cons of accessing sql server using ssms locally over on the actual server I need your help DBAs, I need to know the pros and cons of my question.

We have this new "DBA", who doesn't know about DBA really, he got promoted to DBA temporarily to become an IT supervisor, He does not know any sql and no scripting skills.

He just took out all our developers' access to sql server to connect locally. I want to justify to our director that whatever this guy is doing is not comfortable for us..accessing the server and running the ssms.

Btw, he just changes access without even sending any courtesy emails. I need your advise on whether I'm wrong. I'm a developer for this company and for my past 10yrs, I've never worked in a company where you actually run your SSMS on the actual server.

Here's what I gather and my opinion.


Risk to accidentally rebooting the SQL Server.
Data security on the server.


I wish to add more so I can present this to my Director, I'm just not comfortable doing non-server stuff on the server period.
As a general practice we never even install SSMS on the server hosting SQL Server.

You got the first two already 

1.Risk to accidentally rebooting the SQL Server.

2.Data security on the server.

However there are more:

First of all each session that goes to the server will take up resources (Memory/Cpu/Diskspace,DiskIO) needed by the SQL Server engine, this means a server might get under pressure by allowing people to directly connect on the Server. Which will slow down performance and might even cause timeouts to your applications.

When accessing the SQL Server Server, you can copy and duplicate data on the disks if there is not a good security structure, meaning you can easily fill up the diskspace where your sql server database files are located. Meaning your files won't be able to grow any more

If you have not set up the security rules well, you are able to install other software on the servers also taking away precious memory from the SQL Server server.