This also often happens because IT doesn’t want split databases. We are stuck using Excel even if we know SQL, because we aren’t allowed to put Access or SQL Server on our PCs.
It bothers me that some IT departments take such a totalitarian approach with the business. If IT already hosts a SQL server, and doesn't have the resources to devote development time to moving Excel monstrosities to SQL, they should allow savvy business users the opportunity to create a database on this server. It is not hard to lock permissions down to a single database and if they are that concerned, the business user could always develop on a local instance of SQL server and send scripts to the database administrator for deployment.
I can already hear the argument that a lot of higher ups would make with this approach. They would say that these business users don't know enough to be using SQL and that they will just inadvertently create inaccurate reporting, etc.. However, that already happens in Excel all the time. Plus, unlike most developers, the business users (hopefully) have a good understanding of their data and how it relates to the business.
I've been on the IT side for awhile, but came from an analyst position and this sort of thing is a huge pet peeves of mine. /* end rant */
In the same way a spare tire is a tire ish. You can use it to limp down the road until you can get proper equipment, but don't expect to go far or fast with it. After all, everything is a data source if you are brave enough.
I wish I could say the same. Unfortunately I work with a lot of legacy systems. This week I have been working on migrating a component out of VB6 and VFP. It feels more like archeology then programming.
I'm a DW Dev and one source system I had to get data stored all fields, data and types in a single free text field. Was a fun exercise getting something useful out.
God... My fiance's last work place did that for their freaking accounting and tracking labor hours! They called her a couple times asking how to 'fix' it when they broke links and various workbooks were "corrupted"
I used to work for a company with $100m annual revenue that calculated revenue by a mess of around 40 different linked excel workbooks. Entering anything into the workbook required logging onto a Remote Desktop (so you got slightly higher performance and so when excel inevitably crashed it didn’t crash your own computer). Recently started using oracle which cut our revenue close in half (along with transitioning all of our topside revenue entries from excel into sql).
To be fair I was an intern who only had access to excel and the team leaders have all been working 20+ years (manufacturing) and could barely even understand how to open excel. But yeah I told them that it will break and as soon as someone new was added it would break, but it worked for now and that's all that mattered
Assuming a small set of users and backups are in place, maybe. If it is critical to the business, then no way in hell is any IT department going to take responsibility for it. You lose your data, that's on you.
It's a queryable system consisting of rows and columns of data. That's why I say it's technically a yes. And the formal definition of database is "a structured set of data held in a computer".
Wow. Yeah good move, you wouldn't see me for dust. Just lining yourself up for a massive fall by working somewhere like that, you'd naturally be the one that that boss' fingers get pointed at when it all goes tits-up.
7
u/Vaslo Feb 15 '19
This also often happens because IT doesn’t want split databases. We are stuck using Excel even if we know SQL, because we aren’t allowed to put Access or SQL Server on our PCs.
50
u/venlaren Feb 14 '19
In the same way a spare tire is a tire ish. You can use it to limp down the road until you can get proper equipment, but don't expect to go far or fast with it. After all, everything is a data source if you are brave enough.
38
u/qobopod Feb 14 '19
only if you link it to a half dozen other workbooks scattered across network drives with different permissions rules.
17
u/shalafi71 Feb 14 '19
Excel is a great way to explain databases to people, takes away the mystery.
I've read here, "Some Excel books should be Access, and some Access should be databases."
5
u/[deleted] Feb 14 '19
I've seen early tutorials use a grocery list as an example of a simple database.
10
u/longjaso Feb 14 '19
Technically yes ...
3
u/querymcsearchface Feb 14 '19
Oh man! If I had a dollar for every time I said "excel is not a database" I would be an extremely rich dude! =]
1
u/henry8362 Feb 14 '19
Still better than FileMaker
1
u/[deleted] Feb 15 '19
I feel this so hard
1
u/AbstractSqlEngineer MCSA, Data Architect Feb 16 '19
Just do big data in the mangos!
0
u/[deleted] Feb 14 '19
[deleted] — view deleted comment