Sunday, February 26, 2012

Databases per Server

All,

I have 2 web applications running on 2 W2K servers. Each server has a local SQL server(2000). We are about to upgrade the servers to Windows 2003. The web applications are running classic ASP and VB COM+ objects. We are going to take the opportunity to seperate SQL from the web server. What will end up with is 2 web servers running the applications and a single database server with 2 databases servering up the data. We will upgrade the SQL2K to SQL2K5.

My question is how will the SQL performance be affected? What's the best place to locate the COM+ objects? What kind of pitfalls do I need to be aware of?

Thanks

BB

Make sure that the consolidated box has suitable hardware to support both apps (memory, disks, processors). Also, remember that now the a failure of the SQL Server will bring down both while if one database starts hogging resources, the other would be adversely affected. Similarly you'll only have one set of system databases so make sure that tempdb is on a fast set of disks.

Certainly one area you may need to check any conflicts arising from any SQL Server configurations that may differ on the current boxes and also any login conflicts. Remember, also that future patches will be applied at the server level and both apps will need to be able to run on the same SQL version.

You are able to run multiple instances on one box which would allow you to allocate resources better to each application or could consider virtual servers which is becoming more and more popular these days.


HTH!

|||

Great advice - thanks!

What about the increase in network traffic. Is there something to do hardware wise? Like adding a second NIC card? Will that even make a difference?

Thanks