MUServer and SQL Server separate?

[hntri]

Hi all.
I wanted to know if it is true that if the MuServer and the SQL Server are in two different host slows the server.
Currently I have two vps: one has the MuServer with Windows Server 2003 R2 SP2 and the other SQL Server 2008 R2 (Developer Edition) on Windows Server 2008 R2 (Datacenter Edition). Both are in the same datacenter and have the same IP range.

The reason I did this is because the server and the SQL Server together I consume a lot of RAM.

This has consequences?

Thanks!

That ok.

In mssql server : you only run titanserver( in config file add ip of muserver)
In muserver u only run : bor connect, gamesserver ( config ip of mssql )

Solution for u :
- I have web for muserver it have 2 part ( 1 only run in your server and save all yr information of yr db. 1 run in hosting only a templa)

Solution :
-mssql server : mssql + base server source web
-mu server : bor, gameserrver.
- hosting : client web source ( becare check that hosting ,which can not local hack like shell,....)

If u want to setup. I will do it for u.

[Locomoto]

I don't recommend running a server between 2 machines. There will be gaps in network latency & the cost to run both machines will be expensive.

[hntri]

I don't recommend running a server between 2 machines. There will be gaps in network latency & the cost to run both machines will be expensive.

No problem with it,man.
If 2 server in sảme datacenter. The network, which tranfer server to server less 1000mbs (local Lan)

- and if u wanna open 2-3 or 10 muserver, u only need mssql server or 1 database. That is best solution for u

About website:
- the host or yr vps ,which support anti-ddos is very expensive.

U need 1 solution about that.
If u put website in muserver, they ddos yr wweb --> server u die
If u use web with 2 part of wweb, they dont know yr ipserver,... They only ddos in hosting --web die ,yr server is not problem

[theguyontherun]

Hey there; having sql and mu on different servers will only slow you down if you have lag between the sql and mu. If they are within the same network it wont matter as the comm. between the 2 wont suffer much. If they are across the web then you may increase the lag.

If you are doing this simply because of more security; then all you have to do is lock down all unused ports put sql on a non-standard port; change mu ports as well. Set your firewall to stop fragmented packets and make sure to keep an eye on fake/malicious packets. Also, monitor your network traffic and dont be afraid to block ip ranges, if you block a few good apples along with a lot of bad apples; the rest of the server population will gain in the end and you will get more traffic.