I'm not a fan of IIS and SQL on the same box, for both performance and security reasons. So here's how:

Set up the DNN files on your web server (let's say 10.10.10.9), and create your DB (MyDNNDB) and DB user on the SQL server (let's make it 10.10.10.6).

In your web files, edit your web.config connection strings (2) to read like this :

<!-- Connection String for SQL Server 2000/2005-->
Data Source=10.10.10.6;Initial Catalog=MyDNNDB;User ID=DBUser;Password=DBUserPass" providerName="System.Data.SqlClient"

That's it...
 

one thing i should point out. the IBM x335 have only 2x 36GB SCSIs in a RAID1. i never had any intention of storing any data locally. nor do i have the space for it. there is plenty of juice (dual xeons, 2-4GB of RAM) on each one. but these are pizza boxes.

now i do have a NAS with bound GB NICs. and all the x335 have them as well. they are on their own LAN as well. regular network traffic runs off a 3rd GB NIC in each server. the SQL server is currently setup using the NAS for all DB storage. this is another reason why i thought of pointing the [new] IIS server box at the SQL server's storage space. but from the looks of it, that is not a recommended path.

i guess my next path is for a DAS with eSATA and a PCI eSATA card in the IIS server box. how about that route for now. until our SAN is built, still 8 months away from being completely implemented. at that point all data storage will be in the SAN. and those speeds will reach 4GB transfer speed.

yay, nay?