|
![]()
We are considering running .NET 2.0 on IIS 6 and SQL Server 2005 on one system instead of managing two servers (a web server and a database server).
Is there any reason why it would be bad to run web services and your database on the same server?
Disk thrashing could be a problem if you have a heavy userload. It's usually preferable to have SQL Server on it's own machine, since it is constantly accessing the disk.
It also gives you a single point of failure. If your server goes down, both your database and your web service are inaccessible.
Is there any reason why it would be bad to run web services and your database on the same server?
No I think that should work pretty good
Is there any reason why it would be bad to run web services and your database on the same server?
I am soooo far from an expert ,but i'll give you my 2 cents ( got to be highly overvalued)
What about the vulnerablity to hackers and viruses if the database shares the server with web services.?
Is there any reason why it would be bad to run web services and your database on the same server?
Your best option would be to setup the database and webserver on different boxes. Also the db server should only allow traffic on port 1433 (default port for ADO/SQL communications). Ideally the db server would also exist behind a firewall seperate from the web server for real security.
However...we all know of times when budget and other restraints means this is not possible so here are some suggestions for best performance when hosting web and sql on the same hardware.
|
