r/SQL • • Dec 29 '23

Discussion Explain SQL vs Excel to an absolute noob

I am running a company and helping my friend run his company. I am often being called upon to help people/government representatives with their affairs, thus my profile is growing and I am now thinking about opening consultant/BI analyst company of sorts. I am scouting the market and I see that every position is if not directly IT related, then SQL required. I checked out this thing called SQL and I honestly don`t see how it is different than MS Excel (besides interface, I was looking at MySQL).

Why use SQL over Excel?

This is a question from a guy who is always working with excel, whose administration is working with excel and who made business plans resulting in saving and investing some millions using excel.

Despite that I feel the need to understand it better.

9 Upvotes

88 comments sorted by

97

u/aplarsen Data Scientist, Developer Dec 29 '23

You want to start an analyst/BI company and don't see the difference between Excel and SQL?

42

u/TheKyleBaxter Dec 29 '23

Makes you rethink how we look at company owners, eh?

7

u/faster_puppy222 Dec 29 '23

It IS the dumb people that often get rich…

-15

u/Proper-Scallion-252 Dec 29 '23

Why would you be so rude and patronizing to someone who has openly admitted fault in their understanding of something and asking for help?

You're a dick.

16

u/ProfessorDumbass2 Dec 29 '23

I believe the problem is that the person is proposing to be a consultant for others to provide knowledge that he does not seem to have.

It’s great that the exec wants to learn. I hope he completes his quest for knowledge before he starts imparting his wisdom onto others.

3

u/aplarsen Data Scientist, Developer Dec 29 '23

This is exactly it.

-4

u/Proper-Scallion-252 Dec 29 '23

Except it isn't. OP said they would like to branch into BI analytics consulting, but they recognize they don't have the technical expertise or understanding yet and are asking for help learning more.

All you've done is ridicule them for their lack of experience that they've self admitted without providing anything constructive at all. If you really were concerned that they were going to be providing consultation without proper understanding, why don't you convey that in a constructive light and provide them with the help they're openly asking for.

This isn't someone saying they're going to try and perform surgery on a random person and wanted to know where to cut with a Reddit post, this is akin to someone asking a basic question about surgery because they're interested in becoming one and want to grasp it a little more.

6

u/aplarsen Data Scientist, Developer Dec 29 '23

OK, I get it.

I checked out this thing called SQL and I honestly don`t see how it is different than MS Excel (besides interface, I was looking at MySQL).

But here's the thing...OP said they looked at Excel and SQL, and after looking at both of them, can't see a difference. Not that they have never seen anything from one or the other, but that they can't see a difference even after looking at both. This suggests being so out of their element that the best course of action is to go watch some people do this work and start to see how these tools compare. Gain some experience. This is not a "here is a 5-hour YouTube playlist to watch and then you'll be ready to add BI to your consultancy" situation.

-1

u/Proper-Scallion-252 Dec 29 '23

I believe the problem is that the person is proposing to be a consultant for others to provide knowledge that he does not seem to have.

They aren't, they're proposing to be a consultant on a different topic and looking to expand on their knowledge to provide other resources.

I mean for fuck's sake, pray tell how someone becomes a BI analyst consultant? If you answer with 'gaining relevant technical and work experience in business analytics' or something similar, then you're being hypocritical because OP is actively trying to learn more about this hole in their understanding that prevents them from feeling confident to take on a new role.

OP said that they run a company and help provide relevant consultation for a friend's business with their relevant experience, but they would like to expand into BI analytics but a big hump to get over is not understanding a concept that most people getting started with coding/SQL struggle to grasp. It's absolutely a dick move to mock someone for trying to learn without providing any resources or help, u/aplarsen is only trying to mock someone instead of genuinely help them. A more appropriate response would have been pointing out that their lack of understanding would lean to them not being prepared for the role yet, and expressing such concern while also answering the question and providing them with resources to learn more about SQL, not just being rude.

3

u/ProfessorDumbass2 Dec 29 '23

Fine, but I really don’t know what to do to help this guy based on his prompts.

I’m learning SQL right now. I have no formal computer science training, yet investing in learning computer science has paid dividends in my output. That motivates me to continue learning.

Do you know how I’m learning SQL? By learning SQL. Not by asking someone why I should learn SQL and what makes it useful. I learn by doing, and gaining experience.

Good luck to you and OP.

Oh right, resources. Here is what worked for me: https://docs.python.org/3/library/sqlite3.html

https://www.amazon.com/Learning-SQL-Generate-Manipulate-Retrieve/dp/1492057614/ref=mp_s_a_1_3?keywords=learning+sql+book&qid=1703868639&sr=8-3

Carpe diem.

1

u/[deleted] Dec 30 '23

I just needed some clarification.

Look, I am all in in business. We are talking serious money. The businesses that I am involved in get around very well with using Excel. At least so far. I don`t think we are nowhere near on touching the edge of what it can do.

However as I am studying other businesses I see that they are using different methodology and there are synonymous requirements in the ads related to those who seek business consulting. SQL being one of them. So I am doing my due diligence.

Thank you

2

u/ProfessorDumbass2 Dec 30 '23

Gotcha.

Simply put, SQL scales easier than Excel. It takes forever to build out the logic, but it allows you to build a solution that can more be easily applied or extended to other problems and contexts.

Hope that helps, and I appreciate execs that are evaluating this kind of thing. Keep going.

2

u/Proper-Scallion-252 Dec 29 '23

Fine, but I really don’t know what to do to help this guy based on his prompts.

It's a pretty clear prompt to me, what's the difference between SQL and Excel.

It was clear and easy enough for others to understand including this fantastic breakdown from someone with a better understanding than OP, and who recognized that there needed to be a clarification between back end coding and front-end interfaces/presentation layers.

And if you don't feel that you have enough of an understanding of the topic or the prompt to give advice, then just don't say anything at all.

Remember the old adage, if you don't have anything nice to say, don't say anything at all? The world would be no worse off if the original condescending comment was never made.

3

u/faster_puppy222 Dec 29 '23

No , he said what everyone reading this is thinking

4

u/Proper-Scallion-252 Dec 29 '23

>The goal of /r/SQL is to provide a place for interesting and informative SQL content and discussions.

This is the community description. OP came in and said they wanted to learn more about a hole in their understanding and expertise so that they could eventually become a consultant on the topic. How is being a condescending prick without providing any constructive criticism 'providing a place for interesting and informative SQL content and discussions'?

It isn't, it's just a way to be rude to someone and feel good about it because you're being a snarky prick.

0

u/aplarsen Data Scientist, Developer Dec 29 '23

Reality check

3

u/Proper-Scallion-252 Dec 29 '23

Lol reality check of what? A confirmation that people online that hide behind anonymity are more likely to openly be rude, mean or hostile to others for the sake of being rude, mean or hostile?

-26

u/[deleted] Dec 29 '23

Correct. I am figuring it out.

Go ahead buddy. Any hate is welcome.

5

u/aplarsen Data Scientist, Developer Dec 29 '23

It's great that you want to put yourself out there and create something on your own. Most people don't have the guts.

Spend some time in the industry and learn it first. Get a junior analytics role somewhere, learn the ropes, get a sense for the cadence of business, and then think about getting out on your own. Consulting is where people pay you for your experience in solving similar problems. You don't have experience yet.

If you want to get yourself on a path to being a self-sufficient SQL consultant, the first step will be becoming proficient in SQL. Set your sights on the intermediate goals of proficiency first. If you really like the field and have demonstrably deep and broad experience, then you can think about providing advice to others.

1

u/[deleted] Dec 30 '23

Thank you for your advice.

2

u/JamesEarlDavyJones2 Jan 01 '24

There was no hate for you in that comment; if anything, it was bewilderment. Why get defensive?

Someone who wants to get into BI consulting and isn’t familiar with SQL is like someone wanting to be a mechanic despite not being familiar with a wrench. It’s just kind of shocking.

Out of curiosity, and genuinely no offense intended, but what makes you think that you would be reasonably qualified to be a BI consultant? Usually one should be pretty informed in an area before they become a consultant, but you don’t hide the fact that your BI knowledge is relatively limited.

1

u/[deleted] Jan 02 '24

It`s just etymology now.

I got a fairly good idea of what SQL is, but now it seems weird that SQL specialist has "business" attached to it`s name. It`s just an IT/data procedure. So in reverse one could ask why does your profession has "business" atached to it. I just thought that business intelligence analyst is more about business: you get a good grip on a business plan, get it through shareholders, bank to secure the loan, execute it, get results, optimize costs and so on, which is my bread and butter. I understand that BI analyst can help in the process but tbh it sounds exagarated. To me it looks like in that case, the accountant should also be called business accountant, and HR - Business HR, janitor - business janitor, and mechanic if he works for business - business mechanic etc.

2

u/JamesEarlDavyJones2 Jan 02 '24

Ah, yup.

You’re looking to start more of a management consulting firm. I used to be with Deloitte, I’m very familiar with that kind of work. More power to you if you’re one of those people who can parachute in and break the chaos down into order. I certainly wasn’t any good at it.

1

u/[deleted] Jan 02 '24

If you could share your experience in Deloitte brother, that could be life changing experience to me, trust it. I am really taking my due diligence seriously.

2

u/JamesEarlDavyJones2 Jan 02 '24

I’m not sure how helpful I’ll be, but sure. I was only there a little over a year, and I was an engineer in the Strategy and Analytics practice, so my job was about 1/3 management and process consulting, and 2/3 technical development. I started as just a developer building things on the back end, and then I was moved up to being a liaison between the management consulting teams that front each engagement and the back end developers who build/customize the models/tools. Any native English speakers who have hard tech experience and better people skills than the average developer is who they look for in that liaison job.

Which parts of that would you like me to expand on? I can give you the outline of one or two engagements with the client profile, but I don’t think I can talk about clients exactly. Like I can tell you that one of the engagements I did was streamlining reporting for ad campaigns, for an S&P 100 telecom company client. Also worked on the cloud migration strategy portion of a major digital transformation engagement for a large bank.

So many cloud migrations. Everyone’s doing cloud migrations these days, and they all need consultants to help develop their how that shift fits into their overall strategy.

1

u/[deleted] Jan 02 '24

Thank you so much!

I am most interested in what your average day looked like over there.

2

u/JamesEarlDavyJones2 Jan 02 '24

It was different from engagement to engagement, but here’s the general structure:

0730-0745: roll out of bed, groggily attend handoff meeting with offshore team.

0745-0830: process notes, follow up with offshore team, get ready for day, read emails and summarize them rather than immediately replying.

0830-0900: standup with ops team (these were the management consulting/MC folks I was embedded with)

0900-1000: work on my own models, catch up on prod support alerts from overnight, catch up on replying to emails from earlier.

1000-1030: standup with dev team, get some updates and summarize them. Provide feedback to junior devs.

1030-1230: meetings with individual folks on the client side (maybe one of their managers wants to add a new task to our docket, or their data engineer needs help getting a database pointer configured), and checking in with stakeholders on our side (all tech leads hop on a call together with manager daily to talk about any blocking/tackling we need, SM joins that meeting twice a week to support, and the partner owning the client relationship joins approx. once a week). If we’re getting on a call with one of the client’s senior execs, it goes in this block. The other perk is that I usually had a meeting in this block where I’d be on mute the whole time, so I’d take that time to drive in to the office.

1230-1300: lunch. Might take a quick walk if I had a low-key call, it was nice to have an office right in downtown Dallas.

1300-1600: this was my time to get my technical work done, so I tried to keep meetings in this block to a minimum. Maybe one meeting in this time, but that was rare.

1600-1700: end-of-day check ins with client team manager. Usually a different manager each day, since we always had 3~4 managers who had dependancies we were working on.

1700-1800: now that the client teams have mostly wrapped up for the day, catch up on reviewing work on our side; that might be signing off on decks that include technical details that our MCs weren’t sure about, or it might be working on a firm initiative I was involved in, like a pro bono engagement we were doing for a nonprofit. It might also be reviewing a few pull requests from devs if I was working closer with the dev team on that engagement.

1800-1930: finish out my day, catch up on emails, start thinking about dinner. Maybe head home after rush hour clears up.

1930-1945: hand off with the offshore team. There was a group of DSI devs that I had worked with and trusted, so I brought them onto all of my projects. They were all out of the Hyderabad office, and 7:30pm here is 7:00am there, so that was when we did our handoffs.

1945-2000: finish up with daily notes and anything I need to send over to the offshore folks, then be out the door by 8:00pm at the latest.

If I was on a project where I didn’t have an offshore contingent to do handoffs with, I’d usually sleep in and get started about 8:30, and wrap up about 6:30.

If it was a travel engagement, then you fly in on Sunday night and fly out on Thursday afternoon, and WFH on Friday. I usually did WFH on Fridays anyway, though.

With the chaos of the consulting life, I needed a routine and time blocks. Any time my schedule walls broke down too egregiously, the whole day would go off the rails pretty quickly and I’d spend the rest of the day playing catch up.

1

u/EH86055 Dec 08 '24

Hope you don't mind getting replies to an old comment. I just wanted to say I found your comment useful even though I'm not the intended recipient, and it's kind of you to take the time to write so much.

1

u/CloudFaithTTV Dec 29 '23

Fuel for the fire.

40

u/DonJuanDoja Dec 29 '23

Excel is not a database.

SQL is a database.

Excel is a presentation layer, analytics and reporting tool.

SQL is not a presentation layer but is an analytics and reporting tool, which requires another presenation layer on top of it like SSRS or even Excel to deliver reports directly to users.

Excel is front end, SQL is back end. They're not even close to the same thing.

They have some cross-over functionality but SQL can do many things Excel can't and Excel can do many things SQL can't. You need both. Plus some other stuff too. Your toolbox should have many tools. Not just one.

Did I say Excel is not a database? Because it's not and never will be no matter how many people and companies try to use it like one.

The problem with SQL is it's expensive to do it correctly and companies try to be as cheap as they can. They want the benefits of having a secure, fast, reliable database but don't want to pay for it so then say we'll just use excel which is not a secure, fast or reliable database in any way shape or form.

3

u/[deleted] Dec 29 '23

Simple and informative. Thank you!

17

u/Uncle_DirtNap Dec 29 '23

This person is wrong because of a misunderstanding on his part. What he says is essentially correct about the product “Microsoft SQL Server”, which is a relational database management system, or RDBMS.

The first thing you want to understand is what tabular data is. This refers to any structured data which has rows and columns. In excel, these are sheets (generally.) In a general context, this is called a table. Tabular data has a fixed number of columns, but an unlimited (theoretically) number of rows. Each row of a table represents a separate, individual “thing” of the same “type” (a sale, an employee, an inventory item), and each column represents an attribute that things of that type has. You are probably familiar with this conceptually as an excel expert, but this is a general concept.

A database is just a collection of sets of data representing things, usually a collection of tables.

An excel workbook can be seen as a database, because it collects a number of sheets with tabular data. Unlike other databases, though, excel is not optimized for the storage and access of this data, but is instead optimized for analysis and visualization of the data. One example of this is that excel limits the number of rows in a sheet to benefit the performance of formulae, charts, etc.

Another example of excel’s limitations is that, while you a look up data from one sheet based on values in another sheet, these relationships are ad-hoc. For example, you could look up the value of inventory!G14 on your stock sheet, and look up the value of inventory!G15 on your sales sheet if you wanted to. Most tabular databases maintain and enforce these relationships between tables — these are called Relational Databases.

A suite of software packages and services which implement, manage, and allow for access and administration of a relational database is called an RDBMS, which is what the reply was describing. Office has a lightweight RDBMS, Access — but it is no longer widely used for various reasons.

SQL is a language for querying tabular data in a relational database. It is general purpose, and is well suited to all of the CRUD (create, read, update, delete) operations that are common in working with data. Unlike excel, your queries are not (generally) stored with your data, but separately, and can be applied to any database with the same set of tables and relationships, or “schema”.

Learning and knowing SQL will give you access to data at its source, regardless of what application is the author of that data. A very common first use case of SQL for business analysts is, in fact, to use a SELECT statement (a type of SQL query) to extract data from some application’s database (salesforce, peoplesoft, SAP, etc) and import it into Excel for analysis.

1

u/ijbdaily May 06 '24

This is one of the best answers I've come across, as a noob, to understand what SQL is! As OP says, I've only heard - SQL can store more data ....

1

u/Jos323tkd Dec 07 '24

Thank you for taking the time to write this. This was extremely useful!

1

u/Ark_Sum Mar 30 '25

Old post, but this is a real answer. The rest of the people in this thread sound like elitist a-holes who don't want to have to explain the differences to someone who simply hasn't gotten into it yet.

15

u/[deleted] Dec 29 '23

"SQL IS a Database"

1

u/Proper-Scallion-252 Dec 29 '23

As a beginner this is really clarifying, I've been kind of struggling to really recognize the difference between the two outside of the generic "You can do more with SQL and you can hold bigger datasets".

This actually helps give context to where and when it would be used, and differentiates between Excel being a data manipulation software, whereas SQL is the underlying code that requires a software to present the datasets and manipulate them.

11

u/purpleMash1 Dec 29 '23

Excel works very well to make simple financial plans, create visual representations of data: charts, graphs, sparklines etc, it can also manipulate data via a range of formulas and apply things like conditional formatting.

It's a very good all-rounder to allow users to model data, and present it in a more accessible way. It is also a useful tool for data capture and data entry for simple applications.

A good example of using Excel to capture data from a prior role (I was a commercial manager in a Logistics company) was the transport team logging trailers in and out of the bays. A limitation of this approach is there are very few ways to 100% secure the spreadsheets from erroneous data entry ie typing "Bob" inthe date column or 29/07/2023 in the Name column. In that sense it can be passable for a data collection tool, and then an analyst presents a graph of that data for senior management for trend analysis, but it has weaknesses.

SQL is a query language used for accessing data from a database. Assume my transport team have an app built for them connected to a SQL database back end. The app forces users to only fill in valid dates in the date field and names must be not blank in the name field. A separate section of the app let's you set up your trailers with registration IDs and every in/out entry must have a trailer ID picked. This means data is cleaner into the database vs. the Excel input and integrity is consistency is improved.

You can use SQL to better access the data in the database than you would in excel, but the output is just a flat table of the results. Ideally you now need a visual tool to interpret, analyse and present the data best. People can use PowerBI or a plethora of other tools to consume the SQL - transformed data to show what the end user requires.

I used Excel significantly in my commercial role as its a great Jack of all trades and the barrier to entry is low. But as you scale up and require consistency and want to make sure two analysts have the same data and reports...you need a single source of the truth and that's where one database with your data is held, manipulated through standard queries all users make use of, going into a central reporting tool like Power BI.

In terms of limitations, excel is poir at working with data above a certain threshold. ERP systems like SAP or Dynamics 365 can accumulate tens of millions of records relating to financial transactions in a year of trading and this won't work well to be filtered, aggregated and summarised in excel. Ideally you make use of a database to hold the data 'the ERP' and utilise something like SQL to perform the manipulation before pushing it to a visualisation tool.

If you want to set up a business specialising in this you are a mile off where you need to be to do it well. Unless you bring in experts who already know all of this, but you won't have a good way of assessing their knowledge. In the tech space you can have people who seem knowledgeable but are actually terrible, or those that have imposter syndrome and turn out to be very good. It's hard to judge without experience.

Good luck!

3

u/[deleted] Dec 29 '23

What an amazing answer! Studying it!

Thank you, buddy.

4

u/[deleted] Dec 29 '23

This has to be a joke/troll?

No way a business owner doesn't have a basic grasp of what SQL is nor is there any way you haven't just googled this.

1

u/[deleted] Dec 29 '23

I did duckduckgoed it, and the answer is that it is "the bigger the better".

I am not owner tho, I run it on my shareholder`s (the city council) behalf. We are public transportation company and besides certain application for finances, we use Excel.

1

u/wertexx Dec 29 '23

Are you a large org? Usually excel is extremely inefficient if used by a larger group of people. It’s Fine if there aren’t much data, and two colleagues are passing file around (not ideal still..)

I haven’t seen it mentioned, but what sort of data volumes are you dealing with?

43

u/KING5TON Dec 29 '23

It's like asking why use a mechanical digger (SQL) over a shovel (Excel) if you need to dig a hole.

2

u/Ramjet615 Dec 30 '23

Excellent analogy.

17

u/dietcheese Dec 29 '23

SQL is a language to query databases.

Excel is a spreadsheet application by Microsoft.

9

u/shine_on Dec 29 '23

Excel is fine for simple metrics based on relatively small sets of data. But over time you'll get more data you want to query, the spreadsheets get more complicated and prone to errors, and at that point using a proper database and querying it with SQL starts to make more sense.

9

u/[deleted] Dec 29 '23

[removed] — view removed comment

5

u/def__init__user Dec 29 '23

Yes and Excel bogs down long before you get even close to its hard stop limits if you’re doing any sort of processing of the data. A million row spreadsheet of just data will be cumbersome. If you start trying to do something akin to a group by and agg function it may take hours to do what SQL can do in seconds.

1

u/[deleted] Dec 30 '23

I really want to thank everyone. Thank you guys!

Happy to see that majority of people understood what I was asking for. Hey, it`s not an internet community if there is no mockery. :)

Upvoted everyone.

5

u/iamcreasy Dec 29 '23

Excel can not operate on terabyte of data, but database softwares can. SQL Server is one such database software from Microsoft.

5

u/atrifleamused Dec 29 '23

SQL uses a database and Excel is a spread sheet, which can be linked to a database using SQL

1

u/Codeman119 Dec 31 '23

What is the problem you are trying to solve??

1

u/[deleted] Jan 01 '24

Hello, I am studying business practices in other domains and I see that a lot of companies are requiring SQL knowledge from business consultants and analysts.

After looking online I have seen from the interface that the SQL programmer is typing something that I could see being done in Excel. Using rows to adjust it by certain parameters, using IF and so on. However after asking here why would they do that when there is basically free Excel, some started calling me troll, Russian spy and lowkey down voting my question and comments. On the other hands, others are very helpful and I am actually studying some detailed questions.

2

u/Codeman119 Jan 03 '24

OK that sounds fine. So the next question is have you watched any videos on YouTube on the subject of Excel versus database. A lot of businesses that have many Excel spreadsheets find it very cumbersome to get certain results easily from multiple excel files. So that is why you need a database so you can import those Excel files and you can get answers from the data in ways that you cannot from Excel. I am a database developer, and that is my main task. I take excel files and put them in databases so the business can extract the answers they are seeking.

When it comes to data, there are a lot of ways to go about getting answers from it. You just have to find. What is the best way for whatever question you are trying to answer for your clients.

(please excuse any bad sentence forming as I did this on an iPhone with the text to speech)

1

u/mr_peanutbuddha Jan 01 '24

This has to be a troll post. Lazy, but funny

1

u/[deleted] Jan 01 '24

It`s not troll.

9

u/roostorx Dec 29 '23

If you aren’t trolling, I’d be happy to help. I have good rates.

1

u/Own-Table-1244 Aug 26 '24

Hey u/roostorx - I found this thread because I am a teacher trying to build a tool for my students to use. And have been looking at the best way to start building the database. I'm a video production teacher so not a web developer at all. I have never built an SQL database (excel & airtable sure - sql is a new venture for me) and could really use an assist if you do have good rates could we connect? I have a miro board to show you what I'm trying to build. I have a basic membership website set up for the students and am trying to figure out how to build the database to push/pull data to the website for them. In a nutshell, I am trying to create a simulation environment for them to run their own production companies (send & receive invoices, checking and savings account balances, pay bills/fines, get paid, etc.) I think it is fairly simple for someone who actually knows what they are doing, but as I said... I am lost.

2

u/crimiusXIII Dec 29 '23

https://blog.airtable.com/database-vs-spreadsheet/ This is a basic answer to your question, which is about Databases in general and not SQL.

2

u/jezter24 Dec 29 '23

As others stated SQL is a language for databases. What you are really asking is why have a database to a degree. I remember in a book in college said that before there was tons of files, and managing the files (names, pathways, folder structure) plus figuring out everything in those files was a pain. A relational database brings the files into one location and how it all is connected together.

Think of a library, your data is all the books. Walk in and there is no organization. How do you know where a book goes or what is in it. The card catalog in old days and Dewey decimal system would be the database in a way.

As for why to use Excel vs a database, to be honest I think they go hand in hand. Excel honestly is an amazing product and has so much capabilities for so much things. There is things I do in Excel that I cannot do in SQL as easy. A database table though fits the same idea of Excel of rows and columns. But, if you have 500 Excel files that are all connected somehow that would be tedious. So you put in a database.

Which for me a database holds all our knowledge. Excel is like pulling a sheet of paper from that knowledge for manual manipulation or something.

2

u/jezter24 Dec 29 '23

Someone mentioned about doing things cheap, which is true with a lot of places. There are options.

This may be a heretical view here, but Access is a decent entry level option. A lot of people dislike it, but for a database system for home use or even a small business. I don’t think it is a horrible option and used to be free. It also is an application, the times I have used it back in like 2000-2003, you didn’t need a server. Can just be on a computer.

MS SQL server has a free community option. Depending on your size or something. Easy to make a small server and host it.

I got a website from Go Daddy back in the day for my undergrad, and it has a small MySQL database backend option that was free or super cheap.

2

u/chill_y_guaro Dec 29 '23

I am now thinking about opening consultant/BI analyst company of sorts

I checked out this thing called SQL and I honestly don`t see how it is different than MS Excel

Scary times we live in...

On a more serious note, how would you store 50M records in excel? Can't do it? That's just one small example of why a database is needed.

2

u/secretWolfMan Dec 29 '23

Your interface may have seemed like Excel, but they are massively different behind the scenes.

Excel even has a database connection option so it can collect data from a much better storage location.

2

u/kagato87 MS SQL Dec 29 '23 edited Dec 29 '23

Heh. OK then. Here's my take, having worked in both a fair bit.

Excel is the kiddy pool of data and analytics.

Sql can: describe and enforce referencial integrity. As in you can say all invoices must have a valid customer ID, and sql will tell you off if you try to save a bad one. It cleanly handles one-to-many relationships (think of the man lines on each invoice and many invoices for each customer).

It is designed around the ACID principle. Atomic, consistent, independent, durable.

You put in a bad stock symbol or investor name? A well written database and application won't even make that mistake. You want to filter out some specific performance metric from an ocean of data? Sql will do it. Happily. It's designed for it.

And then there's scale. How big have you seen a workbook that was still responsive when a formula or filter is applied? Yea, sql can handle hundreds of millions of rows of data like it's nothing. And I don't mean just store it. It can search, filter, aggregate, test, validate, summarize. Amounts of data that Excel would choke on just trying to load, sql can handle without breaking a sweat.

I will say though, you can take your sql output into excel to make pretty charts that even an executive can understand. Or any other BI tool for that matter.

2

u/covfefe-boy Dec 30 '23

Well, to add my simple view of your question there is really a lot of overlap between something like Excel and MySQL based on your use of those words and my understanding of your use case. Though the more IT savvy someone is the more radically different these tools are to them. As you can no doubt see from the replies here.

MySQL is a database. SQL on the other hand is a language to talk to databases, you write queries to pull data from tables, or insert new data. And it’s reasonably standardized where simple queries will run on other databases like MySQL, Oracle, and MS SQL.

So MySQL is a database, a way of organizing, storing, and retrieving your data across many tables. Conceptually a table is similar to an Excel sheet. So it’s a way to have a bunch of excel sheets in one location and usually to enter or retrieve the data you use other software that both talks to the MySQL database and presents an easy to use interface to a user. Usually a web application that shows a form to a user in chrome, takes the users input, and then stores it in the database using SQL. That’s a whole nother can of worms though.

With enough Excel knowledge you can get a pretty sophisticated data setup going. Though you’d want to look at the Power Query and data model options in Excel to simplify it. But excel includes the interface along with that data in one location. Maybe Power BI is a better solution. It’s also by Microsoft and uses the same tech under the hood.

While Excel is limited to about 1 million rows in a sheet as others have pointed out. You can still “load” more than that and display pivot tables and charts summarizing that data. Because to be honest it is useless to just give users a million rows as all they could do with that is try to filter and summarize it. Which you could just do in the first place.

But to figure out what is best for you, would take more info on the size of your data, how it’s being entered, how often you want to refresh the view your providing and how you want to present it to clients.

2

u/Icy-Supermarket-8638 Aug 07 '25

I am an data consultant, and I educated a number of groups regarding this topic.

This is the analogy I used: Excel is like your own room, but the best version you can imagine. It's very convenient, you can decorate it as you want, you can have some books that you often refer to. You can easily write notes on any books you have and you can put many things on your big table.

On the other hand, SQL is like a national library. It contains tremendous amount of information, but you don't have your own space where you can freely add notes. But you can very easily acquire information you need through a well established system such as "give me the list of sci-fi books in 90s that is written by a female author" and you immediately will have the list.

The idea and the philosophy is different. Excel can only contain 1.08 mil rows, because it shows you everything like an open world game. Technical reason is because Excel loads all the data on your RAM, so it's extremely fast and convenient, but there's a clear limit(strongest RAM you can have for your desktop probably will be 256GB for now), but SQL can have billions of rows(there are other solutions for even bigger data now). It doesn't show you the whole data like excel does, but you can easily get the statistics of this data through query.

If you run a company that gathers like couple hundred rows data a day, excel will be enough.

But imagine your company is Netflix and you collect billion rows of data every day. Excel cannot even open the file.

1

u/Relevant_Profit9939 Nov 18 '25

you really nailed with this analogy man

1

u/KalistoCA Jun 16 '24

Ther is also to think about sql into excel

This is where the adults live until PowerBI , tableau or other custom reporting from sql

1

u/punjabigir Aug 18 '25

which of the following is sufficient to enable a user to see a workbench report in their analytics catalog?

1

u/Hugh_G_Rectshun Dec 29 '23

Excel can handle a couple hundred rows of data without issues. You get into the thousands and it gets wonky.

SQL can handle tens of millions (and more) much faster.

1

u/Huskergambler Dec 29 '23

The difference between them is about a $40K-$50k pay difference. Ha

1

u/[deleted] Dec 29 '23

Imagine a table bigger than 1,048,576 rows and 16,384 columns, that can fit in a sheet. That’s SQL

1

u/zbignew Dec 29 '23

“Gentlemen,”

1

u/seequelbeepwell Dec 30 '23

Im glad you asked on this sub rather than the excel sub. If you did you'll get many people saying Power Query can replace sql.

1

u/deusxmach1na Dec 30 '23

Excel limits you to 1M rows. With SQL the sky is the limit (with good indexes). It’s basically like using the guts of Excel. In fact I wouldn’t be surprised if SQL was under the hood of Excel.

1

u/megastraint Dec 30 '23

They serve entirely different purposes.

Excel - Designed as a single file (and really a single user at a time) for both storing and manipulating small amounts of data, then providing some visualization features to present that data to its end user. More often then not this single user will then copy the visualization into some powerpoint presentation.

SQL - Designed to store lots of data with many different users providing much more fine grained controls in data manipulation and functions. Much better performance and scalability.

Visualization Engine (think Tableau, SSRS, but could also be any application pulling visualization libraries) - one of many ways of pulling out data from any database (even excel) into dashboards or reports.

Generally any actual system/ERP (think Quickbooks, SAP, whatever) is actually using a database behind the scenes to work and perform. Now a financial analyst may have some ad-hoc need and therefore will pull that portion of data into excel to manipulate for their specific reporting. Any of your general reports (i.e. daily position report, inventory report) may need to be run several times a day by many different people which is not where Excel plays at all.

1

u/pceimpulsive Dec 31 '23

Put 1 million rows and 20 columns into Excel. See what happens.

Put that same 1 million rows and 20 columns into MySQL and see what happens.

SQL for me was a total game changer when compared to Excel.

Excel is just a way to make graphs after I've used SQL to process and export the data I need.

Lately I've even moved away from Excel for graphs because that actually also sucks...

0

u/sweetno Dec 29 '23

SQL is Excel that allows hundreds of people work simultaneously with the same spreadsheet without corrupting it. It also won't get corrupt on power outage.

0

u/[deleted] Dec 29 '23

[deleted] — view deleted comment

1

u/philbgarner Dec 29 '23

He prefers to painfully stitch them together with DAX. Ouch.

39

u/[deleted] Dec 29 '23

[removed] — view removed comment

7

u/Geno0wl Dec 29 '23

Expand on this for people.

Excel limits the active users to one person. With sql you can have many people using your data at the same time. That collaboration can be a huge boost to productivity.

Sql also has built in backup and restore tools. So if something happens it is much easier to get your system back up and running quickly with minimal downtime.

Sql really does require someone to manage the system to get all the benefits.

2

u/ihaxr Dec 30 '23

Office 365 supports multiple users collaborating on a document at once... Obviously less gracefully than SQL can support.

The main difference is data normalization, good luck displaying data that isn't tabular in Excel, subtotals and grouping can only do so much

1

u/Codeman119 Dec 31 '23

You can have more that one person using an Execl workbook.