The only reason that I can think of is to balance the load among systems.
This might be because you want to split the load between the data base
server and the application, or because you want to run the application on
more than one server.
Regards,
Jerry Schwartz
Global Information Incorporated
hlpful
Thanks
Ratheesh K J
- Original Message -
From: "Brent Baisley" <[EMAIL PROTECTED]>
To: "Ratheesh K J" <[EMAIL PROTECTED]>;
Sent: Monday, August 28, 2006 7:33 PM
Subject: Re: Seperating Application server and Database server
In addition to what the
In addition to what the others told you, security would be a big reason. If the application server is compromised, whether through
your application code or some other service on the box, then they also have local access to the database files.
If you setup a database server, you can open just the
Ratheesh K J wrote:
> Hello all,
>
> Currently our application and MySQL server are on the same machine.
>
> When should these be seperated?
>
When:
- your performance is dropping, and
- you have identified that your bottleneck is CPU usage, and
- both your MySQL server and your applicati
Ratheesh K J wrote:
Hello all,
Currently our application and MySQL server are on the same machine.
When should these be seperated?
What are the main reasons that we should be having a seperate DB server?
There are at least three possible reasons. First, if your applications
are using lot
