How can I limit SQL Server to only allow a specified machine to connect
- 2020-05-10 23:05:34
- OfStack
The ORACLE tutorial you are looking at is: how to limit SQL Server to a specific machine. How can restrict access to my SQL Server so it only certain machines to connect?
(v1.0 19.10.1998)
How can I limit my SQL Server to a specific 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 could be written/used to do this. Therefore you have the following choices :-
SQL Server does not have such functionality, nor does it provide the ability to perform a particular procedure at connection time. There are several ways to do this
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.
USES a firewall, which 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.
writes its own ODS gateway instead of SQL Server's client - check in ODS gateway. However, this does not stop normal client connections to SQL Server. There is one such example in 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.
writes a stored procedure to check the appropriate columns in sysprocesses (net_address)
(v1.0 19.10.1998)
How can I limit my SQL Server to a specific 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 could be written/used to do this. Therefore you have the following choices :-
SQL Server does not have such functionality, nor does it provide the ability to perform a particular procedure at connection time. There are several ways to do this
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.
USES a firewall, which 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.
writes its own ODS gateway instead of SQL Server's client - check in ODS gateway. However, this does not stop normal client connections to SQL Server. There is one such example in 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.
writes a stored procedure to check the appropriate columns in sysprocesses (net_address)