Which RDBMS?
-
I come from a Microsoft background. I'm pretty good at managing SQL Server databases, making them parallel and fast, and I know T-SQL quite well. To a lesser degree I know SQL92 but I sometimes get T-SQL mixed into it. I'm trying to decide what RDBMS to run on my Debian VPS. Obviously it's not going to be SQL Server. I expect light traffic. I'm wondering if Postgre might be the best option (most familiar) for me? Or if it would be overkill as I only really need simple stuff for the most part. I don't think I'll need triggers or jobs, for example. Maybe I'd also be taking on too much management. I'd prefer it be something i can set up and forget about more or less. Mysql is another option and might be worth learning because it's so ubiquitous, but my main concern with it is overhead in terms of learning curve. My biggest priority is to reduce that curve. I don't want to spend time learning about a different RDBMS way of doing things wherever I can avoid it. I just don't want to invest the time. I'm not sure which one would be a good fit for my use cases, which are still open ended at this point, except light traffic and simple, smallish datasets. Like I said, by biggest priority is a flattish learning curve, so the closer I can get to MS SQL Server "feel" the happier I'll be. In the alternative, an RDBMS that's fairly automatic with few user facing moving parts outside of SQL/DDL/DML would be okay. I'm not sold on those two offerings either. If someone has a better idea, I'm all for trying it.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
honey the codewitch wrote:
I come from a Microsoft background. I'm pretty good at managing SQL Server databases, making them parallel and fast, and I know T-SQL quite well.
[...]
honey the codewitch wrote:
what RDBMS to run on my Debian VPS.
Did you forget [SQL Server for Linux](https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-setup) is a thing? If not, what disqualifies it?
-
I come from a Microsoft background. I'm pretty good at managing SQL Server databases, making them parallel and fast, and I know T-SQL quite well. To a lesser degree I know SQL92 but I sometimes get T-SQL mixed into it. I'm trying to decide what RDBMS to run on my Debian VPS. Obviously it's not going to be SQL Server. I expect light traffic. I'm wondering if Postgre might be the best option (most familiar) for me? Or if it would be overkill as I only really need simple stuff for the most part. I don't think I'll need triggers or jobs, for example. Maybe I'd also be taking on too much management. I'd prefer it be something i can set up and forget about more or less. Mysql is another option and might be worth learning because it's so ubiquitous, but my main concern with it is overhead in terms of learning curve. My biggest priority is to reduce that curve. I don't want to spend time learning about a different RDBMS way of doing things wherever I can avoid it. I just don't want to invest the time. I'm not sure which one would be a good fit for my use cases, which are still open ended at this point, except light traffic and simple, smallish datasets. Like I said, by biggest priority is a flattish learning curve, so the closer I can get to MS SQL Server "feel" the happier I'll be. In the alternative, an RDBMS that's fairly automatic with few user facing moving parts outside of SQL/DDL/DML would be okay. I'm not sold on those two offerings either. If someone has a better idea, I'm all for trying it.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
I use SQL Server in a corporate environment. I just read an article about MySQL that basically says to avoid it and use MariaDB instead. Many commenters highly recommend PostgreSQL. I have not worked with it but that would be my choice if I could not use SQL Server.
-
honey the codewitch wrote:
I come from a Microsoft background. I'm pretty good at managing SQL Server databases, making them parallel and fast, and I know T-SQL quite well.
[...]
honey the codewitch wrote:
what RDBMS to run on my Debian VPS.
Did you forget [SQL Server for Linux](https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-setup) is a thing? If not, what disqualifies it?
I've heard of it. A) I don't necessarily trust it. Historically, outside of VS Code, Microsoft's track record with cross platform software products is not good. B) Due to A I haven't looked into licensing but I'm assuming they'll want to charge me, and I already pay enough for my VPS given how little use I get out of it.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
I use SQL Server in a corporate environment. I just read an article about MySQL that basically says to avoid it and use MariaDB instead. Many commenters highly recommend PostgreSQL. I have not worked with it but that would be my choice if I could not use SQL Server.
I've never heard of MariaDB, but I'd be interested in the "why nots" of mysql given how common it is in the wild.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
I've heard of it. A) I don't necessarily trust it. Historically, outside of VS Code, Microsoft's track record with cross platform software products is not good. B) Due to A I haven't looked into licensing but I'm assuming they'll want to charge me, and I already pay enough for my VPS given how little use I get out of it.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
SQL Server runs very fine on Debian 12 and RHEL. I've been using for a couple of years now, never had any problems. The RHEL install has high traffic in production, the Debian install is what I use for development. If it is for personal use just go with the developers license.
-
SQL Server runs very fine on Debian 12 and RHEL. I've been using for a couple of years now, never had any problems. The RHEL install has high traffic in production, the Debian install is what I use for development. If it is for personal use just go with the developers license.
I'm not sure if it qualifies as personal? Other people will end up hitting it. I'll have to look into the licensing details. Thanks!
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
I've never heard of MariaDB, but I'd be interested in the "why nots" of mysql given how common it is in the wild.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
It's now owned and managed by Oracle, and they've been viewed as not the best to deal with an open-source product. MariaDB is created by the original creator of MySQL, so it's pretty much (older versions anyway) a drop-in replacement. I'd either go with MariaDB or Postgres if I had to choose.
TTFN - Kent
-
I come from a Microsoft background. I'm pretty good at managing SQL Server databases, making them parallel and fast, and I know T-SQL quite well. To a lesser degree I know SQL92 but I sometimes get T-SQL mixed into it. I'm trying to decide what RDBMS to run on my Debian VPS. Obviously it's not going to be SQL Server. I expect light traffic. I'm wondering if Postgre might be the best option (most familiar) for me? Or if it would be overkill as I only really need simple stuff for the most part. I don't think I'll need triggers or jobs, for example. Maybe I'd also be taking on too much management. I'd prefer it be something i can set up and forget about more or less. Mysql is another option and might be worth learning because it's so ubiquitous, but my main concern with it is overhead in terms of learning curve. My biggest priority is to reduce that curve. I don't want to spend time learning about a different RDBMS way of doing things wherever I can avoid it. I just don't want to invest the time. I'm not sure which one would be a good fit for my use cases, which are still open ended at this point, except light traffic and simple, smallish datasets. Like I said, by biggest priority is a flattish learning curve, so the closer I can get to MS SQL Server "feel" the happier I'll be. In the alternative, an RDBMS that's fairly automatic with few user facing moving parts outside of SQL/DDL/DML would be okay. I'm not sold on those two offerings either. If someone has a better idea, I'm all for trying it.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
Have you considered SQLite? [SQLite Home Page](https://www.sqlite.org/) It might fit your use case. Some caveats, though * It's a single writer/multiple reader. When writing, it locks the entire DB, (only for the duration of the write, I think), so if you need multiple, concurrent DB writes, then probably not for you * Although you can declare fields as int, float, varchar, etc, under the hood SQLite stores everything as text, so you can do this:
sqlite> create table t(datum int);
sqlite> insert into t values('Hello World');
sqlite> select * from t;
Hello WorldIf your DB will only be accessed by an application, it may not be an issue. Update: On the plus side, it's about as fast as read/write on a plain file.
"A little song, a little dance, a little seltzer down your pants" Chuckles the clown
-
I come from a Microsoft background. I'm pretty good at managing SQL Server databases, making them parallel and fast, and I know T-SQL quite well. To a lesser degree I know SQL92 but I sometimes get T-SQL mixed into it. I'm trying to decide what RDBMS to run on my Debian VPS. Obviously it's not going to be SQL Server. I expect light traffic. I'm wondering if Postgre might be the best option (most familiar) for me? Or if it would be overkill as I only really need simple stuff for the most part. I don't think I'll need triggers or jobs, for example. Maybe I'd also be taking on too much management. I'd prefer it be something i can set up and forget about more or less. Mysql is another option and might be worth learning because it's so ubiquitous, but my main concern with it is overhead in terms of learning curve. My biggest priority is to reduce that curve. I don't want to spend time learning about a different RDBMS way of doing things wherever I can avoid it. I just don't want to invest the time. I'm not sure which one would be a good fit for my use cases, which are still open ended at this point, except light traffic and simple, smallish datasets. Like I said, by biggest priority is a flattish learning curve, so the closer I can get to MS SQL Server "feel" the happier I'll be. In the alternative, an RDBMS that's fairly automatic with few user facing moving parts outside of SQL/DDL/DML would be okay. I'm not sold on those two offerings either. If someone has a better idea, I'm all for trying it.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
We dropped SQL Server in favor of PostgreSQL years ago, and never looked back. It has been multi-platform for a long time and is very stable. The only thing I regret is that they decided to use Python for the PgAdmin tool, the older version was written in C++ and much "leaner and meaner".
-
I come from a Microsoft background. I'm pretty good at managing SQL Server databases, making them parallel and fast, and I know T-SQL quite well. To a lesser degree I know SQL92 but I sometimes get T-SQL mixed into it. I'm trying to decide what RDBMS to run on my Debian VPS. Obviously it's not going to be SQL Server. I expect light traffic. I'm wondering if Postgre might be the best option (most familiar) for me? Or if it would be overkill as I only really need simple stuff for the most part. I don't think I'll need triggers or jobs, for example. Maybe I'd also be taking on too much management. I'd prefer it be something i can set up and forget about more or less. Mysql is another option and might be worth learning because it's so ubiquitous, but my main concern with it is overhead in terms of learning curve. My biggest priority is to reduce that curve. I don't want to spend time learning about a different RDBMS way of doing things wherever I can avoid it. I just don't want to invest the time. I'm not sure which one would be a good fit for my use cases, which are still open ended at this point, except light traffic and simple, smallish datasets. Like I said, by biggest priority is a flattish learning curve, so the closer I can get to MS SQL Server "feel" the happier I'll be. In the alternative, an RDBMS that's fairly automatic with few user facing moving parts outside of SQL/DDL/DML would be okay. I'm not sold on those two offerings either. If someone has a better idea, I'm all for trying it.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
SQL for Linux is a good, reliable product. From experience... If you are looking for something more multi-platform, go fro MySQL - a very good product too. Also from experience...
"It never ceases to amaze me that a spacecraft launched in 1977 can be fixed remotely from Earth." ― Brian Cox
-
It's now owned and managed by Oracle, and they've been viewed as not the best to deal with an open-source product. MariaDB is created by the original creator of MySQL, so it's pretty much (older versions anyway) a drop-in replacement. I'd either go with MariaDB or Postgres if I had to choose.
TTFN - Kent
Maybe these would help? [MariaDB vs PostgreSQL - Difference Between Open-Source Relational Databases - AWS](https://aws.amazon.com/compare/the-difference-between-mariadb-and-postgresql) [Compare MariaDB vs SQL Server](https://www.influxdata.com/comparison/mariadb-vs-sqlserver/) I will certainly check out MariaDB as a replacement for MySQL in a personal project.
There are no solutions, only trade-offs.
- Thomas SowellA day can really slip by when you're deliberately avoiding what you're supposed to do.
- Calvin (Bill Watterson, Calvin & Hobbes) -
Have you considered SQLite? [SQLite Home Page](https://www.sqlite.org/) It might fit your use case. Some caveats, though * It's a single writer/multiple reader. When writing, it locks the entire DB, (only for the duration of the write, I think), so if you need multiple, concurrent DB writes, then probably not for you * Although you can declare fields as int, float, varchar, etc, under the hood SQLite stores everything as text, so you can do this:
sqlite> create table t(datum int);
sqlite> insert into t values('Hello World');
sqlite> select * from t;
Hello WorldIf your DB will only be accessed by an application, it may not be an issue. Update: On the plus side, it's about as fast as read/write on a plain file.
"A little song, a little dance, a little seltzer down your pants" Chuckles the clown
It might be a little primitive for my needs. While no current projects require any real concurrency on writes I might certainly need it in the future, but particularly, I'd like a bit more data integrity than what you demonstrated above. Thanks though. Isn't that an in memory capable DB or am I thinking of another one? There was one I was considering using in my projects as a kind of queryable dataset system.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
SQL Server runs very fine on Debian 12 and RHEL. I've been using for a couple of years now, never had any problems. The RHEL install has high traffic in production, the Debian install is what I use for development. If it is for personal use just go with the developers license.
-
It might be a little primitive for my needs. While no current projects require any real concurrency on writes I might certainly need it in the future, but particularly, I'd like a bit more data integrity than what you demonstrated above. Thanks though. Isn't that an in memory capable DB or am I thinking of another one? There was one I was considering using in my projects as a kind of queryable dataset system.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
SQLite can certainly be used as an in-memory database, but only within the context of a single process. So maybe not useful in your use case
"A little song, a little dance, a little seltzer down your pants" Chuckles the clown
Well, not for this scenario, but the dataset thing was intended for single process, in memory stuff. Think Datasets in .NET but for C++, for example, and queryable.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
I come from a Microsoft background. I'm pretty good at managing SQL Server databases, making them parallel and fast, and I know T-SQL quite well. To a lesser degree I know SQL92 but I sometimes get T-SQL mixed into it. I'm trying to decide what RDBMS to run on my Debian VPS. Obviously it's not going to be SQL Server. I expect light traffic. I'm wondering if Postgre might be the best option (most familiar) for me? Or if it would be overkill as I only really need simple stuff for the most part. I don't think I'll need triggers or jobs, for example. Maybe I'd also be taking on too much management. I'd prefer it be something i can set up and forget about more or less. Mysql is another option and might be worth learning because it's so ubiquitous, but my main concern with it is overhead in terms of learning curve. My biggest priority is to reduce that curve. I don't want to spend time learning about a different RDBMS way of doing things wherever I can avoid it. I just don't want to invest the time. I'm not sure which one would be a good fit for my use cases, which are still open ended at this point, except light traffic and simple, smallish datasets. Like I said, by biggest priority is a flattish learning curve, so the closer I can get to MS SQL Server "feel" the happier I'll be. In the alternative, an RDBMS that's fairly automatic with few user facing moving parts outside of SQL/DDL/DML would be okay. I'm not sold on those two offerings either. If someone has a better idea, I'm all for trying it.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
When you look for things, look for ANSI SQL. Those are the common bits across the things SQL. There are a few implementation/platform specific things. Like Oracle does 'sequences' and MSSQL has 'identity'. But a big swath of most standard DDL/DML is highly portable. And I'd say what I think really matters in RDBMS is more about set theory than it is about SQL dialects/specifics. Normalized vs denormalized and stuff like how to identify where indexes are going to help or where they may be more costly (in disk space and maintenance) than the ROI (in performance).
-
When you look for things, look for ANSI SQL. Those are the common bits across the things SQL. There are a few implementation/platform specific things. Like Oracle does 'sequences' and MSSQL has 'identity'. But a big swath of most standard DDL/DML is highly portable. And I'd say what I think really matters in RDBMS is more about set theory than it is about SQL dialects/specifics. Normalized vs denormalized and stuff like how to identify where indexes are going to help or where they may be more costly (in disk space and maintenance) than the ROI (in performance).
I believe SQL92 is ANSI? Also my big concern isn't language, but actual maintenance of the DB.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
I believe SQL92 is ANSI? Also my big concern isn't language, but actual maintenance of the DB.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
One of the good things about PostgreSQL is that it does not need as much maintenance as SQL Server. Our customers usually don't have the skills to maintain an SQL Server properly. Of course this is dependent on how complex the database is.
-
I believe SQL92 is ANSI? Also my big concern isn't language, but actual maintenance of the DB.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
Yeah I think so. "These editions colloquially became known as SQL-86, SQL-89, and SQL-92. So, if you hear those names in reference to an SQL format, note that it is referring the various editions of this standard." Read more at the ANSI Blog: The SQL Standard – ISO/IEC 9075:2023 (ANSI X3.135) https://blog.ansi.org/?p=158690
-
It's now owned and managed by Oracle, and they've been viewed as not the best to deal with an open-source product. MariaDB is created by the original creator of MySQL, so it's pretty much (older versions anyway) a drop-in replacement. I'd either go with MariaDB or Postgres if I had to choose.
TTFN - Kent
Kent Sharkey wrote:
MariaDB is created by the original creator of MySQL, so it's pretty much (older versions anyway) a drop-in replacement.
As I understand it that description is not correct. When MySQL was bought by Oracle it was open source. At point in time a branch was taken of MySQL and then given the name MariaDB. The open source nature of development has continued on that branch. Following provides information on contributors to MariaDB SHOW CONTRIBUTORS - MariaDB Knowledge Base[^] I do know of Percona in that list and I can say that they have done, to my mind, extensive work improving both the open source version and there own variation which they sell/license. And specifically in terms of performance. Following is release history and it seems pretty active to me MariaDB Server - All releases - MariaDB.org[^] Conversely the release history for MySQL is much more sparse. There has been speculation that the focus of Oracle is not on MySQL and certainly not on the free version (they have a paid one). One might suppose quite reasonably that that is because Oracle wants either their paid version used or even Oracle database used instead. MariaDB Server - All releases - MariaDB.org[^]
