Re: The SA Mess
From: Adam Machanic (amachanic_at_hotmail._removetoemail_.com)
Date: 03/16/05
- Next message: Simon Worth: "Re: Audit login failure (with generation of alerts)"
- Previous message: Russell Stevens: "Re: The SA Mess"
- In reply to: Russell Stevens: "Re: The SA Mess"
- Next in thread: Ross Presser: "Re: The SA Mess"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 16 Mar 2005 15:25:11 -0500
"Russell Stevens" <rustyprogrammer@online.nospam> wrote in message
news:enDqxImKFHA.1284@TK2MSFTNGP14.phx.gbl...
>
> If you want users to be able to connect to a SQL database via the
> Internet, then a firewall does not do you much good as you have to open
the
> port anyway.
That's kind of my point; SQL Server was never meant to expose a
hardened, open port on the 'net. It's meant to be used behind a firewall to
talk to app servers -- which are meant to expose a hardened, open port. I'm
just curious about what kind of applications you're running that require the
open port?
-- Adam Machanic SQL Server MVP http://www.sqljunkies.com/weblog/amachanic --
- Next message: Simon Worth: "Re: Audit login failure (with generation of alerts)"
- Previous message: Russell Stevens: "Re: The SA Mess"
- In reply to: Russell Stevens: "Re: The SA Mess"
- Next in thread: Ross Presser: "Re: The SA Mess"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
Loading