felixg's questions

I'm running CentOS 6.2 on ESXi 5. The machine has 2 NICs, eth0 is connected to the Internet and eth1 to a LAN. eth0 has a single colo provided IP address, so the netmask is 255.255.255.255. The gateway is of course on a different subnet. After boot I've no Internet access, I'm solving it by running:

route add -host x.x.x.x dev eth0
route add default dev eth0 gw x.x.x.x

I want this to be automatic. Currently I've added these lines to the rc.local script. I've tried the recommended path of adding a route-eth0 script, but it doesn't work. I don't know what is correct syntax representing the route commands, nor how to see the errors my attempts generate. Can this be done via route-eth0 or some other expected CentOS way?

[Clarification]
My ifcfg-eth0:

DEVICE="eth0"
NM_CONTROLLED="yes"
ONBOOT=yes
HWADDR=xxx
TYPE=Ethernet
BOOTPROTO=none
IPADDR=82.166.38.XX
PREFIX=32
GATEWAY=82.166.190.YYY
DNS1=xxx
DOMAIN=xxx
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no

Aseq's second scenario is very close, but the actual IP assignment is more complex. I got 82.166.38.XX, 82.166.38.XX+2 but they are reachable only through the 82.166.190.YYY, so if I put non 255.255.255.255 netmask those machine cannot communicate.

I think if I could translate the route syntax to ip addr syntax, it should work.

I'm running a SQL EXPRESS 2005 server currently hosting ~50 databases. The databases serve clients' CMS/eCommerce websites. The connections are to a single instance, no user attached instances are being used. Median DB size is 5MB, the largest 20MB. The website are mostly low traffic, the CPU utilization is < 10%, and the SQL process uses at most 350MB RAM.
For now I'm well within the SQL server express limits of 1CPU/1GB RAM. In the upcoming expansion the number of databases may double. If I assume linear growth in requirements, the 1GB limit still wont be reached. But I'm concerned the number (> 100) of databases may become an issue. I'm not sure if this usage scenario is what Microsoft had in mind for express.
Is there any information or preferably real-world experience regarding SQL server express capability to handle lots of small databases? Can I expect it to run 150 databases, or should I start working on migrating to other database servers/file-based databases?

We're hosting >100 websites on a single IIS7 server, and adding about a dozen monthly. The problem is using the IIS manager - it displays all of the sites under the "Sites" node. The list is very long and difficult to navigate.
Is there a way to categorize/divide the list some how (hierarchically)? Preferably in a controllable way - by customer, by website type? The MSSQL server management studio has the same issue with displaying many databases in a single list.