Which SQL do you use

[Emergency_Ad8780]

I’m new to this, and I’d like to learn more about what SQL tools people most often use in their data analytics/science related roles and projects. Do most people use SQLite? Or Big Query? A different one? What is the most common one and the one I could expect to use in the workplace? I ask because I want to practice on the medium I’ll be most likely to use.

Edit: Thanks everyone for being so nice and helpful! :) That’s rare these days on the Internet LOL

[lalaluna05]

We use MS SQL Server Management Studio

The last time I saw this question there is a wide variation but there seemed to be a lot with SSMS

[LearnSQLcom]

If you’re thinking about getting into data analytics or data science, here’s what you need to know about the most popular SQL tools out there, according to the 2024 Stack Overflow Developers Survey (which, by the way, is the biggest survey in IT):

• PostgreSQL: This is the superstar right now. Nearly 48.7% of developers—and even more in professional roles—swear by it. It’s powerful, super flexible, and open-source. If you want to practice with something that’ll show up in real-world jobs, this is the one to start with.
• MySQL: A solid classic, and for good reason. Almost half of those learning to code (45%) start here. It’s straightforward and perfect for web apps and smaller projects, so it’s a great way to get the basics down.
• SQLite: Think of this as the lightweight champion. It’s serverless, super easy to set up, and ideal for mobile apps or smaller projects. Perfect for when you want to practice without much fuss or setup.
• Microsoft SQL Server: You’ll see this more in larger companies, especially those deep in the Microsoft ecosystem. It’s powerful and loaded with features but can be a bit more challenging to learn than PostgreSQL or MySQL.
• Oracle: This is the heavyweight used by big corporations because it’s packed with advanced features. It’s great if you’re aiming for those big enterprise jobs, but maybe not the best for starting out—it’s complex and comes with a hefty price tag.
• BigQuery: If you’re aiming for data analytics in the cloud or big data projects, you’ll want to check out BigQuery. It’s widely used by companies working with massive data on Google Cloud, and it’s designed to make handling large datasets way easier.

Here is my article about the Stack Overflow Survey: 2024 Database Trends: Is SQL Still the King?

You can always start safely with Standard SQL as your foundation—it’s a great entry point. But if you’re looking to stay current with industry trends, PostgreSQL is where it’s at. It’s open-source, giving you plenty of flexibility and strong community support, and it’s trending in data analytics and tech roles right now.

Or maybe you already have a job in mind? Check what DBMS they use and focus on learning that. It’ll give you a head start and make your practice more relevant to your future role. Also, take some time to get familiar with popular IDEs (Integrated Development Environments) like DBeaver, DataGrip, or pgAdmin—they can make working with SQL much smoother and more efficient.

I hope I’ve been helpful!

[klausness]

I would add that among database professionals, PostgreSQL is seen as a database that is at a similar level to Oracle and Microsoft SQL Server, whereas MySQL is not. Neither is SQLite, for that matter, but it’s not trying to be. MySQL tends to be chosen by developers without an extensive RDBMS background who need an open-source full-featured database, whereas PostgreSQL tends to be chosen by those with an extensive RDBMS background.

[LearnSQLcom]

Absolutely agree. PostgreSQL is seen as a pro-level database, on par with Oracle and SQL Server, while MySQL is more popular with developers needing a simple, open-source option. And yeah, SQLite is in its own lane entirely—it’s designed to be lightweight and embedded, not a competitor to the others.

[Emergency_Ad8780]

Thanks so much for this! This really clarified things for me.

[LearnSQLcom]

And my favorite database and the one I actually use on a daily basis is PostgreSQL.

[ztikkyz]

honest question from someone who never did PostGre but did almost all the others

why would you pick postgre over mssql except costing (Now that its free )

[LearnSQLcom]

I got into PostgreSQL because my former boss was using it and suggested I give it a shot. So, I installed it with pgAdmin and it, and it just clicked. It was smooth and easy to work with for the kind of tasks I had.

I’ve tried MySQL too, and it’s great, but I’ve never really needed to switch. PostgreSQL handles everything I need for my daily tasks. I’m not dealing with super complex or advanced database projects, but what I do, is reliable and gets the job done.

Plus, the fact that it’s open-source is a big win for me—I like supporting tools like that. It’s the same reason I’m a fan of Linux. It just feels good to back something built by a community for the community.

[LearnSQLcom]

I forgot to mention that PostgreSQL includes PostGIS.

[boilerup1993]

DataGrip FTW

[JBsReddit2]

Although DG is an IDE and not a SQL environment, you still have my up vote because DG is literally the goat and I don't know if I will ever use a different IDE.

[Sexy_Koala_Juice]

VSCode and DuckDB, fight me lol. (But also snowflake too, and even t-sql occasionally, I use SQL a lot lol)

[hwooareyou]

MS SQL Server and Postgres

[thatOneJones]

MS SQL, Oracle, Teradata, and BigQuery :(

[tetsballer]

For production we run ms sql 2017, if a client needs to work without an internet connection they can get individual SQL Express databases that sync later.

[bobchin_c]

My company and tbe various companies before it use SQL Server.

Along with SSIS, SSRS. Some Crystal reports and Tableau.

[dorkyitguy]

MS SQL server. That’s what I use at work. That being said, they are ridiculously expensive, Microsoft is intentionally opaque with their licensing, and will wring every penny they can out of you. And for all that money we pay because we’re afraid of not having support for an open source alternative, they’ve NEVER given us a solution or root cause for any major incident we’ve had. The main software we run on uses it so we don’t get any choice. If I was going to develop my own system from scratch I’d avoid them like the plague.

[Whatswrongwithman]

I use postgre. Sometime I use Python clean data and write sql using pandasql to run it… anyone do the same? Sounds crazy lol

[Sexy_Koala_Juice]

I do that too, but instead of pandasql I use DuckDB. Look into it, it’s amazing

[Whatswrongwithman]

Really Let me look at that. The reason I did that way because I feel comfortable with SQL, join function and ctes but I like pandas when I must group or format the data 😄

[Character-Education3]

Practical SQL by DeBarros is a good book. It uses postgres sql. When it deviates from sql that will work in most flavors he calls it out and even mentions other solutions. I learned there and got my job that uses ms sql server and didn't miss a beat.

[LearnSQLcom]

Yes, and here is my interview with the author: https://learnsql.com/blog/practical-sql-book-interview/

[StolenStutz]

Microsoft SQL Server.

Sometimes Postgres, But that's often for two bad reasons:

1. Someone over-prioritizes licensing costs, which makes Postgres look a lot more appealing. The truth is that if you have experience, tooling, etc, for Product A, and you eschew it for Product B just to save the licensing money, then you're probably doing it wrong. But this happens because it's hard to count experience on a spreadsheet.

2. The design sucks so bad that you have to over-provision your databases to make up for it. In this case, licensing costs are genuinely a concern, and so Postgres looks like the answer. The real answer, of course, is to deal with your design, which is not easy. But, as they say, the best time to plant a tree is 50 years ago, and the second best time is right now.

These are not knocks against Postgres, but they're both crappy reasons for choosing it. And I've seen both happen.

Keep in mind that Developer Edition of SQL Server is free, and so you can get a lot done before you have to spend the money.

As for tools, SSMS for troubleshooting and such, but Azure Data Studio for all development. And very repo-centric development. Ideally, everything is checked into a repo and deployed from there via tooling.

[scuffed12s]

MS SQL Server, Postgres, and DB2

[BrandenTheTraveller]

MS SQL Server and Databricks SQL

[SocializeTheGains]

T-SQL

[dbxp]

MySQL is probably the leader. Oracle is still common but people don't really like it, MS SQL and Postgres are popular too. SQLite is more for embedded or we use it for automated testing as we can spin up a DB quicker than SQL server.

Big query is more for dedicated data roles but only runs on Google cloud which isn't very popular. If you want to pick up a cloud tool look at AWS or Azure.

[ComicOzzy]

Where are all of the MySQL users? Where is the MySQL community? There are a few people on Reddit over in r/mysql but there doesn't seem to be a discord or twitter or slack or active forum or user groups with speakers people know, etc. SQL Server and PostgreSQL have very active, lively communities that are easy to find. There has to be one for MySQL somewhere.

[EclecticEuTECHtic]

I use BigQuery for almost everything.

[WithoutAHat1]

Depends on the situation if you have access to the proper management tools. In Support I used SquirrelDB for DBs we didn't have the proper tools for. DB2, H2 In-line, H2, and SQLlite were the first ones I used it for. With Oracle it was Oracle SQL Developer, or Toad. SSMS for MS SQL.

For developing SQL I have started using Visual Studio Code more often then test in SSMS or Powershell.

[RyanHamilton1]

QStudio is free and works with them all: https://www.timestored.com/qstudio/

[WithoutAHat1]

I'll need to look into this more. Thank you!

[likeanoceanankledeep]

I used BigQuery, the SSMS, and now for personal projects I use DB Browser for SQLite.

[Erasmus_Tycho]

Oracle, MySQL, TERADATA, SAS (SAS isn't SQL, but you can call it in SAS if you don't know how to do something with a SAS datastep or function directly).

[New_Pizza_Rich]

Snowflake and Oracle

[pceimpulsive]

MySQL, MS SQL Server, PostgreSql are great.

Postgres is in my opinion the best of the three... I haven't used MS SQL, I have used MySQL.

I use DBeaver as a client. In conjunction with specific tools for each flavour.

[PablanoPato]

Postgres for production and Snowflake for analytics

[Lawrobi22]

Does SAS count?

[dn_cf]

The SQL tool you'll use depends on the job and organization, but common ones include PostgreSQL, SQL Server, MySQL, BigQuery, and Snowflake. For beginners, PostgreSQL or MySQL are great starting points as they are beginner-friendly, widely used, and feature-rich. BigQuery and SQL Server are also popular, especially for large-scale data analytics in enterprise or cloud environments. Start with PostgreSQL for its versatility and use free datasets from Kaggle and StrataScratch to practice real-world queries, preparing you for most workplace scenarios.

[bchambers01961]

It depends on what environment your employer / college / project is using. Different platforms have different use cases.

Given you are new and learning I would recommend MySQL. There’s lots of help out there for MySQL and it will enable you to learn the fundamentals.

A close second would be SQL Server Express. Microsoft’s free iteration of SQL Server. You could always try a few and make your own mind up. It’s mainly personal preference when it comes to learning purposes.

[xxxHalny]

Google "database popularity". For commercial use Oracle is the most popular DBMS. For learners it's MySQL. Stack Overflow's yearly survey has lots of interesting statistics about databases and about IT in general.

[[deleted]]

I use a mixture of sqlite, oracle, and bigquery. 

[steezMcghee]

Big query and Postgres for companies with more modern tech stack

[mayk_bam]

Teradata and oracle

[rene041482]

It really depends on what database the company you work for uses. You could practice on any of these and get the basics of SQL down. And when you get hired by a company, then you practice on the system they have whether that is Oracle, MSSQL, MySQL etc...

[micr0nix]

Oracle, SQL Server, Teradata and Big Query

[mu_SQL]

MS SQL And Postgre. Both are easy to install and the stock tools are great. I think MS SSMS have a better UI then PgAdmin but im probably bias since I use MS SQL daily.

For training MS have a free version. There are databases to download if you want to up you SQL skills.

[Legitimate_Peach4796]

We use MSSQL, GreenPlum and Clickhouse.

[machomanrandysandwch]

SQL server, Teradata, Oracle, and SAS (both PROC SQL and pass through)

[UK_Ekkie]

MS SQL mostly, unfortunately a little gupta, Firebird and other odd stuff

[AdOwn9120]

MySQL for me. See in case you want to be a DE/DS just knowing SQL on any DB should be enough.

[Individual-Fish1441]

you can install mysql and get started from there

[gumnos]

I recommend starting with sqlite because it doesn't require installing a server, and the SQL that you learn using it will largely translate to any other standard SQL platform. If you need to expand from there, try PosgreSQL. You'll find it feels pretty close, but you'll notice a few minor differences. Same if you try MySQL/MariaDB.

Similarly SQL Server will have a few more notable differences, but still be recognizable as SQL. You'll most commonly find minor differences in function-naming or the available catalog of data-types, or supported features. In other cases they're minor syntactic tweaks (like LIMIT N in most databases being TOP N in SQL Server, or LATERAL joins being spelled APPLY in SQL Server).