stop accessing peoples SQL server through SQL management Studio.
-
i want to stop some peoples in my organization to access SQL server through SQL managment Studio.
-
i want to stop some peoples in my organization to access SQL server through SQL managment Studio.
You can't. You can't know how they're accessing it and it shouldn't matter anyway; either they have access or they don't.
-
You can't. You can't know how they're accessing it and it shouldn't matter anyway; either they have access or they don't.
How can you say this ? i know they are accessing through SQL management studio.what you think if we can change the port or any other method ?
-
How can you say this ? i know they are accessing through SQL management studio.what you think if we can change the port or any other method ?
Azam Niaz Ch. wrote:
i know they are accessing through SQL management studio
How?
-
i want to stop some peoples in my organization to access SQL server through SQL managment Studio.
Forget the client tool, SSMS is just a UI and can be replaced by a number of tools. You need to control access to your database/servers using the standard security setting built into the database and server applications. Assuming you are system admin for the database you can start setting login requirements, creating schemas and other standard practices.
Never underestimate the power of human stupidity RAH
-
i want to stop some peoples in my organization to access SQL server through SQL managment Studio.
The quickish and simple way: (1) remove SSMS from their computers (2) restrict access to the server so that they can only access views and cannot perform any updates, inserts or deletes or do anything else for that matter - views only, that's a simple way of providing more security. Notes: given (2), (1) is not strictly necessary, however the only people using SSMS should be the DBAs so it is probably best to get people out of the habit of having access to it(I know... if people download Toad they will have similar features available).
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
Azam Niaz Ch. wrote:
i know they are accessing through SQL management studio
How?
Just FYI, it looks like the Management Studio executable identifies itself as something similar to "Microsoft SQL Server Management Studio" or "Microsoft SQL Server Management Studio - Query" when it connects to SQL Server. This shows up in the program_name column of the dynamic management view sys.dm_exec_sessions. Scott
-
Just FYI, it looks like the Management Studio executable identifies itself as something similar to "Microsoft SQL Server Management Studio" or "Microsoft SQL Server Management Studio - Query" when it connects to SQL Server. This shows up in the program_name column of the dynamic management view sys.dm_exec_sessions. Scott
Which means nearly nothing; you can set the applications' name in the connectionstring. It would not be hard to create a console-app to have me execute SQL with the same or no name at all. If someone has access, he has access. Disabling the tool he/she uses simply means changing tool to achieve the same.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)
-
The quickish and simple way: (1) remove SSMS from their computers (2) restrict access to the server so that they can only access views and cannot perform any updates, inserts or deletes or do anything else for that matter - views only, that's a simple way of providing more security. Notes: given (2), (1) is not strictly necessary, however the only people using SSMS should be the DBAs so it is probably best to get people out of the habit of having access to it(I know... if people download Toad they will have similar features available).
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
GuyThiebaut wrote:
the only people using SSMS should be the DBAs
NNnnnnnnooooo, don't make the developers use VS for Ghus sake. We have a bunch of DBA's who are so divorced from the developers I have never even met one. They only look after production and accept scripts from us for changes.
Never underestimate the power of human stupidity RAH