I'm a self teaching beginner, and I know absolutely nothing about the technical specs of computers/programming in general. I am using a C# book to learn it, and I mainly just want to learn everything that relates to game development, if something has no part in game development/no use in it. I won't bother learning it for the time being. All I currently need to know is, does SQL have use when it comes to game programming?
So while you don't use SQL to build a game, it's still good to know it. It allows your game to smoothly interact with the relational databases that contain important game-related data. Furthermore, the most successful games use data to personalize players' experience and to drive the game's constant improvement.
Most games don't rely on SQL for anything. Some games use it on backends for certain business processes, but login authentication and billing aren't gameplay. It is great for many kinds of business processes, but it is based on disk-based data and assorted ways to slice and dice data sets.
. NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications, including games. . NET has been used by game engine and framework developers to enable safe cross-platform scripting across multiple gaming platforms.
A Database for Video Games Whether you're a solo developer or working on AAA titles, MongoDB gives you the best way to work with data.
99% of the time, no.
SQL is used for storing and retrieving large amounts of data quickly and efficiently. Think of a database as a filing cabinet (or usually a room full of filing cabinets) and SQL as an ultra efficient filing clerk!
If your game needs to store and retrieve lots of data (maybe a highly complex strategy game for example) then the answer may swap to yes, but on the list of things to study I would put it waaaay down.
If you do need to store settings etc. from your game you're better off
Perhaps SQLite where the overheads are minimal, but unless you need the indexing (fast access) and lots of storage it would be better for roll your own as SQL Server itself is overkill and heavy on system resources, not something you'd want running alongside your game.
In summary, I would say no, SQL does not normally have a place in game design (client side stuff anyway).
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With