Q. How can I restrict access to my SQL Server so that it only allows certain machines to connect?
(v1.0 19.10.1998)
How can I restrict access to my SQL Server so that it only allows certain machines to connect?
A. SQL Server has no built-in tools/facilities to do this. It also does not have the facility to run a stored-procedure on connection that could be written/used to do this. Therefore you have the following choices : -
SQL Server does not have such a function, nor does it provide the function of executing a specific process when connecting. Here are several implementation methods
1. Put the SQL Server behind a firewall and use that to restrict access. This is the most secure and functional way to do what you want.
Using a firewall, it provides security and the tools you want to use.
2. Write your own ODS Gateway and point the clients at that instead of the SQL Server - the ODS Gateway will then do the checking. However, there is nothing stopping clients figuring out the correct SQL client-config entries to point straight at the SQL Server. There are examples of ODS code in the SQL Programmers Toolkit - available for free download from the MS website.
Write your own ODS gateway instead of SQL Server client - check in ODS Gateway. However, this does not stop normal client connections to SQL Server. There is an example of this in the SQL Programmers Toolkit, which can be downloaded for free from the Microsoft site.
3. Write a constantly running/scheduled stored-procedure that checks the relevant column in sysprocesses (net_address), and then issues a KILL command for any processes that should not be running. Note that this only works for MAC addresses. This way allows people to connect and possibly make changes before they are spotted and killed.
Write a stored procedure to check the corresponding column (net_address) in sysprocesses
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
