The ORACLE tutorial is: how to restrict SQL Server from connecting only the specified machine. 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 my SQL Server from connecting only the specified Machine?
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 cocould be written/used to do this. therefore you have the following choices :-
SQL Server does not have this function and does not provide the function to execute a specific process during connection. Several implementation methods are introduced here.
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.
The firewall 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 to replace the SQL Server Client-check in ODS gateway. However, the normal client connection to SQL Server cannot be stopped. In the SQL Programmers Toolkit, you can download this sample from the Microsoft Site for free.
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 shocould 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 columns in sysprocesses (net_address)
<