ASP.net and SQL config

Hello,

We are testing our first internal IIS 6.0 box as most of our web content has
been published via Websphere and/or Domino. Anyway, this new server's purpose
is to be a general web box for various internal portals, apps and the like.
I'm the network/server guy not the developer but I have a quick question or
two.

The developers are working on some in-house ASP.net apps (they are new to
ASP also) that connect to a separate SQL 2005 DB server and couldn't get them
to work. So, they installed SQL 2005 Express on the web server and ran the
Surface Area configuration tool and then it would allow them to connect to
the remote DB server.

To me, this just doesn't sound correct. From a performance and security/best
practice perspective I was hoping to keep this new IIS 6 box as clean as
possible. I just don't think SQL has to be installed on the web server! Can
anyone dish out some advice or links to documentation? I've searched on
Google and haven't found much yet but I'm still looking.

Thanks,

C

RE: ASP.net and SQL config

why you need to install sql onto the web box,

the problem is not very clear but as general case.
any asp application that need to communicate with an external sql db all it
needs is:

1)user name and password to connect to the DB (connection string)
2)the communiction between the web box and the sql machine is availble .
port 1433 tcp is open

http://support.microsoft.com/kb/287932


"myoman" wrote:

> Hello,
>
> We are testing our first internal IIS 6.0 box as most of our web content has
> been published via Websphere and/or Domino. Anyway, this new server's purpose
> is to be a general web box for various internal portals, apps and the like.
> I'm the network/server guy not the developer but I have a quick question or
> two.
>
> The developers are working on some in-house ASP.net apps (they are new to
> ASP also) that connect to a separate SQL 2005 DB server and couldn't get them
> to work. So, they installed SQL 2005 Express on the web server and ran the
> Surface Area configuration tool and then it would allow them to connect to
> the remote DB server.
>
> To me, this just doesn't sound correct. From a performance and security/best
> practice perspective I was hoping to keep this new IIS 6 box as clean as
> possible. I just don't think SQL has to be installed on the web server! Can
> anyone dish out some advice or links to documentation? I've searched on
> Google and haven't found much yet but I'm still looking.
>
> Thanks,
>
> C