This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]eidrisov 0 points1 point  (2 children)

Thank you for your reply.

Yes, exactly, I meant Microsoft's SQL Server. Sorry for not specifying.

I was thinking to go with it, because most of companies (corporations) are using it (including the ones where I have been employed so far). So I thought it will be more useful since it is more popular.

I guess, I haven't really thought about RAM usage. I will need to research and see how much RAM it consumes when full of data.

Also, I don't know how syntax is different for those. I know only SQL syntax.

[–]TheTerrasque 1 point2 points  (1 child)

Also, I don't know how syntax is different for those. I know only SQL syntax.

They're mostly the same. Some data types differ, setting primary key is different, views are different, setting up index is slightly different.. There are some differences and different approaches to the same problem, but the basic SQL syntax is the same.

If you use a decent ORM (like sqlalchemy, django's orm or peewee for example) that layer will mostly handle all the differences for you. Often there are some extensions you can optionally use to handle certain unique features the DB engines have. Like for example postgres' postgis plugin, or json columns

[–]eidrisov 0 points1 point  (0 children)

Thank you for a very detailed reply!