Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
CanadaDBA
583 Posts |
Posted - 2004-11-16 : 13:30:58
|
| I want to make our production server secure and prevent it from service to our test / developers department. The question is how it is possible to force the SQL-Server (in our production) to serv only specific IPs and do not serv the others? Or probably, you may have a better idea to implement this.Canada DBA |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2004-11-16 : 13:55:55
|
| Yes. Do not provide any logins for that server to your testers or developers. If they have access via a Windows login or group, use sp_revokedbaccess or sp_revokelogin to prevent them from connecting via Windows authentication. Make sure no one has the sa password and they're not using sa in the applications. If you're not sure, change the sa password. |
 |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-11-16 : 14:50:49
|
| A firewall?==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2004-11-16 : 20:26:52
|
| VPN?--------------------keeping it simple... |
 |
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2004-11-16 : 20:30:10
|
quote: Originally posted by jen VPN?--------------------keeping it simple...
Wow... there is a contradiction if EVER I saw one Damian |
 |
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2004-11-16 : 20:35:28
|
| The login way is the "best" way to go, but putting your SQL server on a different subnet would probably be easiest for you to impliement. You should alway seggregate your production and development environments. This is especially important when it comes to viri and worms. Michael<Yoda>Use the Search page you must. Find the answer you will.</Yoda> |
 |
|
|
|
|
|