| Author |
Topic |
|
iansr
Starting Member
23 Posts |
Posted - 2003-04-16 : 07:01:47
|
| Hi all, For security reasons the company where im working would like to trim the number of sql servers installed in the network. As such, I was wondering would it be possible to have SQL server be restricted ONLY to the local machine in which it is running and have no effect whatsoever to other machines in the network?Thanks!Ian |
|
|
KnooKie
Aged Yak Warrior
623 Posts |
Posted - 2003-04-16 : 07:03:24
|
| SQL Server 2000 comes with a personal edition i believe that is for use on one machine only i think.I've not had a need to try it though.===========PaulEdited by - KnooKie on 04/16/2003 07:03:55 |
 |
|
|
iansr
Starting Member
23 Posts |
Posted - 2003-04-16 : 07:07:30
|
| Thanks for the reply,If the 'personal edition' is something like the desktop edition in SQL 7.0, then i believe it only restricts the number of concurrent users or something, its still visible across the network though. |
 |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2003-04-16 : 07:35:31
|
| OK, are you cutting down on the NUMBER of SQL Servers installed on various computers, or are you trying to RESTRICT access to SQL Server to only the actual machine on which it's installed? Your original question doesn't make this clear.As far as restricting access, you can disable all of the network libraries for SQL Server, it will then be able to connect to the local SQL Server using shared memory access. Books Online has details on how to use shared memory. |
 |
|
|
iansr
Starting Member
23 Posts |
Posted - 2003-04-16 : 07:50:52
|
| Yes to both.We are cutting down the number of sql servers on various machines.. And Im thinking (perhaps as an alternative) If it would be okay to simply restrict the sql server "sphere of influence" to only the local machine. Therefore, theoretically, if a new sql slammer worm hits it, it CANNOT infect other sql servers in the network.Thus, i might be able to keep my local SQL Server from being discarded. Anyway, the SQL Server installation is for local testing only.Edited by - iansr on 04/16/2003 07:52:30Edited by - iansr on 04/16/2003 07:54:06 |
 |
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
Posted - 2003-04-16 : 13:04:00
|
| To make a SQL Server respond only to local connections (via LPC/Shared memory) simply remove all Server Network libraries using the Server Network utility i.e. move them into the disabled protocols list box and restart SQL Server. It will now not respond to attempts to connect from the network.HTHJasper Smith0x73656c6563742027546f6f206d7563682074696d65206f6e20796f75722068616e6473203f27Edited by - jasper_smith on 04/16/2003 13:10:03 |
 |
|
|
iansr
Starting Member
23 Posts |
Posted - 2003-04-16 : 20:59:00
|
| Ok, Ill try it out and let you know how it goes.Thanks!Ian |
 |
|
|
byrmol
Shed Building SQL Farmer
1591 Posts |
Posted - 2003-04-16 : 21:21:07
|
| Taking the "Server" out of "SQL Server".....Step 1:Pull the network plug out of the back of the box.Step 2:Set every database to single use only.Step 3:Drink beer.DavidM"SQL-3 is an abomination.." |
 |
|
|
iansr
Starting Member
23 Posts |
Posted - 2003-04-16 : 21:40:29
|
| Heheh.. That should work :)Ill look into the single database option.Thanks! |
 |
|
|
|