1 Server + SQL + MySQL + .NET + PHP

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Hi,
Looking for some advice here on performance issues with the above apps running on a single server. We currently have a Dell PE2650 Intel Xeon with 2 GB RAM running as our live server with 5 x SQL2000 databases. I have now been asked to put a MySQL database on here too but I am worried about performance issues, obviously dependent on the amount of users hitting it. On the webserver we are running IIS6 & .NET but they also want to configure PHP to connect back to the MySQL server as well
as IIS connecting back to the SQL2000 from a DMZ to LAN.

Is this a good idea to host both apps on one server, do they even play together? I'm not keen on the idea and would prefer to keep them seperate until we can migrate the MySQL to SQL, any opinions appreciated.

To summise:
DB_SERVER >>>>>> SQL2000 + MySQL
| |
| |
WEBSERVER >>>>>> IIS6 + .NET + PHP


Cheers

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

It is generally considered a very bad idea to host more than one RBMS on a system.

Alot of the settings tend to assume they are the only major app on the machine.

They will both want to consume large ammounts of processor and IO resources.

In theory its possible with tuning and a fast enough box, dual processor / RAID etc, but why bother ?

Its generally alot harder and you are possibly looking at a single point of failure. Maybe you could create a dual homed cluster or use virtualisation but you're only talking about one server so lets ignore this.

Also you will need to have staff trained on both systerms etc, then theres licensing etc etc.

Thats why most people pick one vendor and stick with it. Of course with open source and open standards this can be less of an issue.

Seriously how much is an new webserver and database server going to cost ? How many man hours could you waste on breaking the existing setup ? How much will the downtime damage the business ? If its a small set up for a non critical site then sure go ahead.

 

Well it sounds like a small shop or non critical system otherwise they wouldn't even consider it.

I'd mention all you concerns and objections in a document / email, get your boss to accept full responsibility for any ensuing disaster in writing. Theres ITIL and Disater Recovery/Avoidance docs that detail risk analysis etc. Ask around DBA forums and MSSQL & MySQL support what their reccomended install is. Ask them what they think about it. If its a migration ask them what a typical migration strategy might look like etc.

Theres a few DBA's that frequent CertForums they will probably be able to give you more details.

Personally I'd ditch IIS while your at it too and implement two seperate stacks on two physically seperate systems. Use Apache instead its currently the best of breed product. If you have any *nix expertise consider not using windows as the OS. Also some non intel servers are much better designed for the high threading / low latency required for web servers.

 

hi,

Well it sounds like a small shop or non critical system otherwise they wouldn't even consider it.

I'd mention all you concerns and objections in a document / email, get your boss to accept full responsibility for any ensuing disaster in writing. Theres ITIL and Disater Recovery/Avoidance docs that detail risk analysis etc. Ask around DBA forums and MSSQL & MySQL support what their reccomended install is. Ask them what they think about it. If its a migration ask them what a typical migration strategy might look like etc.

Theres a few DBA's that frequent CertForums they will probably be able to give you more details.

Personally I'd ditch IIS while your at it too and implement two seperate stacks on two physically seperate systems. Use Apache instead its currently the best of breed product. If you have any *nix expertise consider not using windows as the OS. Also some non intel servers are much better designed for the high threading / low latency required for web servers.

Thanx I will do this before any steps are taken.

 

You haven't mentioned much about the machines involved.

With a *lot* of spindles and a *lot* of memory it may work. Without that it will be painful.

Harry.

 

hi



very cute

 

Looks like Harry has an admirer

 

Something that I missed was that the original posting was a year ago.....

Harry.

 

yes i didn't realise that it was a old post , cheers Jimmy