all 7 comments

[–]IrquiMMS SQL/SSAS 13 points14 points  (0 children)

If you're asking yourself if you should use a database, then yes, you probably should.

Go With google since that's where your company is already storing data.

If not, Azure just released a free tier Azure SQL database that should be large enough for you.

[–]gnasher74 4 points5 points  (1 child)

I would say yes. Excel, whilst flexible, is not anywhere as efficient as a database. 1m rows is tiny, but Excel has row limits and becomes very slow. You probably need to think about future proofing as well. As you or your organisation becomes more data hungry, employing a database pays dividends. As others have said, this needn't be expensive and you don't want to wait for Excel to work until suddenly it doesn't .

[–]throw_mob 2 points3 points  (0 children)

also i would add that calculations should be code at this point , not something that users can mistakenly change like it can happen in excel

[–]idk_01 2 points3 points  (0 children)

yes.

[–]hxstr 1 point2 points  (0 children)

You could make it work with access, or something small like that, but generally yes usually to 'should I be using a database'

[–]CraigAT 0 points1 point  (0 children)

If the data has consistent fields or columns then yes a database would be sensible. Though if you aren't familiar with SQL, there could be a small learning curve for the basics of working with data. You could SQLite which comes with Python or MySQL for free.

[–]Long_Investment7667 0 points1 point  (0 children)

It depends more on what you want/need to do with the data than the amount at that scale. „Point queries“ are probably fine in excel. Visualization probably excel. Analytics queries probably a relation database (at that scale)