Skip to main content
Game Development

Return to Answer

improved formatting a little
Source Link
edit approved Jan 26, 2012 at 16:06
famousgarkin
edit approved Jan 26, 2012 at 16:06
famousgarkin
  • 688
  • 7
  • 23

MySQL is free, is fast, can handle really big tables, is easy to use and you can find documentation and help extremely easy.

I also know MySQL better than say PostgreeSQLPostgreSQL and that is why I choosechose that one for my persistent multiplayer game.

Go with what you know best and if the worst case scenario happens (everyone wantwants to play your game and the DB knuckelsknuckles) you can always change (or buy a faster server).

MySQL is free, fast, can handle really big tables, easy to use and you can find documentation and help extremely easy.

I also know MySQL better than say PostgreeSQL and that is why I choose that one for my persistent multiplayer game.

Go with what you know best and if the worst case scenario happens (everyone want to play your game and the DB knuckels) you can always change (or buy a faster server).

MySQL is free, is fast, can handle really big tables, is easy to use and you can find documentation and help extremely easy.

I also know MySQL better than say PostgreSQL and that is why I chose that one for my persistent multiplayer game.

Go with what you know best and if the worst case scenario happens (everyone wants to play your game and the DB knuckles) you can always change (or buy a faster server).

Source Link
Valmond
Valmond
  • 2.5k
  • 2
  • 18
  • 28

MySQL is free, fast, can handle really big tables, easy to use and you can find documentation and help extremely easy.

I also know MySQL better than say PostgreeSQL and that is why I choose that one for my persistent multiplayer game.

Go with what you know best and if the worst case scenario happens (everyone want to play your game and the DB knuckels) you can always change (or buy a faster server).