MySQL or SQLite - Multiple servers
#1

So. I'm currently using SQLite to manage 3 servers. Now, it's getting pretty annoying to modify a value of each server's db. So I thought about implementing MySQL instead and have all 3 servers connected to a single db. That way I will be able to manage servers without a problem. BUT, I also want to keep these 3 servers optimized. So, you guys think its worth having MySQL to manage 3 servers?

I've been using MySQL & SQLite each a year roughly. I love both of these systems. So again, would YOU use MySQL in this case?
Reply
#2

Well that depends really...
I'd use MySQL personally, just because it's always been easier for me to manage.

Do you want a combined information pool? Like do you want players from one server to be able to login to another?
Do you have a high player-count? If not, are you expecting to?

Adding several servers to the same connection will ultimately lag all 3 if the data-transfer becomes too much
Reply
#3

Yeah, I want all data from a db to be used withing all 3 servers, so yes, a registered player can log in into server 2 or 3 using that same db.

There's usually 10-20 players daily per server for at least a few hours. That's pretty much every day. No, I don't expect the players count to rise since that's about our server's max slots

I used to use 2 servers in one db, no lag at all. I don't think there would be much lag having 3 servers running the same connection.
Reply
#4

Looking for a few more opinions
Reply
#5

I'd move to MySQL, if I were you.

Might be rumour, but from what I've heard SQLite is more intensive on a HDD than MySQL is, for reading and writing, and the more connections you have, the more likely you're going to have a problem. But at any rate, that does sound logical.

The only real differences within SA-MP is that SQLite is faster for single transactions, MySQL (the threaded plugins) can be more reliable when you thread your queries and can generally match in speed once you thread your queries, plus you don't risk your server hanging after a query and you'll have fewer bugs to deal with - the SQLite port for SA-MP isn't perfect, there's quite a few bugs that can cause your server to hang (i.e. trying to retrieve null values IIRC).

Plus, the syntax/extra functions in MySQL are worth moving to, just for that very reason.
Reply
#6

Quote:
Originally Posted by Calgon
Посмотреть сообщение
I'd move to MySQL, if I were you.

Might be rumour, but from what I've heard SQLite is more intensive on a HDD than MySQL is, for reading and writing, and the more connections you have, the more likely you're going to have a problem. But at any rate, that does sound logical.

The only real differences within SA-MP is that SQLite is faster for single transactions, MySQL (the threaded plugins) can be more reliable when you thread your queries and can generally match in speed once you thread your queries, plus you don't risk your server hanging after a query and you'll have fewer bugs to deal with - the SQLite port for SA-MP isn't perfect, there's quite a few bugs that can cause your server to hang (i.e. trying to retrieve null values IIRC).

Plus, the syntax/extra functions in MySQL are worth moving to, just for that very reason.
Actually Calgon is right its better to move to MYSQL ..advanced and easy to use...well to my opinion..try to use it by MYSQL i think that you will manage your servers better by this..
Reply
#7

Alright cool. Thanks for the comments
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)