On 2/15/2010 2:58 PM, Justin Dearing wrote:
On Mon, Feb 15, 2010 at 2:06 PM, David Krings <ram...@gmx.net
<mailto:ram...@gmx.net>> wrote:
Do you have TCP/IP enabled? That is turned off by default in MSSQL.
Why? Because everyone needs it....
I'm actually kinda glad that Microsoft turns that off, because not
"everybody" needs it.
First of all, you don't need it if your application is on the same
machine as the SQL server. Second of all, if you don't know what your
doing, you don't want your SQL server open to the world. Third, its not
that hard to turn on once you know where to look. So its secure by default.
Don't get me wrong, I'd be all for a prompt during the install to turn
on TCP access and warn you of the risks. I also realize that most real
world usages of SQL server require TCP access. However, especially for
the developer and express editions, a few hoops to make it harder to
hang yourself is a good thing.
I agree, but working with especially SQL2008 professionally made me really
deeply loathe this POS. I could give plenty of reasons, but that will be
somewhat pointless here. Not to say others are better, the new MySQL workbench
doesn't work on Server 2003 and is incapable of making remote connections.
Which idiot decided that this sad excuse of a GUI tool is ready for prime
time? Luckily they still offer the old tools, which work perfectly fine.
Maybe that is what I get for shying away from the command line....
In regards to TCP/IP and SQL2k5, how many apps run on the same server? Yea,
there are some, but my guess is that in reality the vast majority connects
remotely. Aside from that, security is a good thing, but then why is it
allowed by default to use weak or even no sa password? Just asking
rhethorically....
David
_______________________________________________
New York PHP Users Group Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk
http://www.nyphp.org/Show-Participation
