Microsoft Access. Two words guaranteed to bring any data analyst or IT professional out in a cold sweat but is the somewhat tarnished reputation justified and is there any real place for MS Access in your analytical arsenal?
“Serious” analysts claim to not touch Access with a twenty foot barge pole. It’s more uncool than your dad dancing at a family wedding. It’s been uncool for so long I keep waiting for hipster analysts to adopt it and start to wear using it as a badge of honour against the entrenched snobbish establishment. I’m still waiting.
In certain circles mentioning that you use MS Access is akin to saying you never want to work professionally in the data world again.
They say it’s too slow. They say it’s not able to handle high volumes of data. They say it’s not fit for more than one user. It’s a toy. It’s too “easy” to use. It’s not secure. It’s too easy to corrupt. It’s not suitable for enterprise applications.
And in many cases those complaints are justified. That’s not to say that it doesn’t have it’s place underpinning both daily workplace tasks and as a quick, easy way to pull some data together and give it a rudimentary once over.
All of the things people use as arguments against using MS Access turn out to be reasons for others to use it.
It’s super easy to use – hell yes it is. Setting up tables, queries, forms and reports is a veritable walk in the park. You can import data from spreadsheets, text files or other more suitable data sources like SQL Server and not be afraid of Janey from Accounts overwriting chunks of the production tables with an ill-advised UPDATE statement in Management Studio.
It’s not big enough and my database just kept growing – over time you will eventually max out it’s size limits (somewhere around 2GB from personal observation) but for small scale datasets and quick analysis jobs this will give you more than enough space for very little server space overhead and all you need is MS Access installed on your machine. This should come as standard with most MS Office installs so no fighting with the IT Department to install unwelcome 3rd party software.
It’s not secure enough – well don’t keep business critical or top secret secure data on it in a publicly accessible place then. You don’t need a full user access infrastructure to get started, load it up, fire in your data, run your queries or VBA and it’s all there in front of you.
Slow down cowboy/cowgirl. It’s horses for courses and both sides of the debate are technically correct (yes, my rear end does hurt from splinters from sitting on the fence).
Access is never a suitable database system for business critical processes or for something that should be housed in an enterprise level DBMS. Using it to suck in large volumes of data from your main data warehouse will make you want to cry and stamp your feet in frustration. It’s not worth it, trust me, I have the feet stamping scars to prove it over many, many years.
If you have a need to turn some numbers around quickly or investigate a sub-section of a data table then I do recommend having MS Access as part of your toolkit. It’s ease of use and shallow learning curve belie it’s ability to get some vital, if unsung, jobs done in any size of business. It’s not for no reason that MS Access remains the most used desktop database solution in the world.
By all means, know it’s limitations but that doesn’t mean that you should throw the baby out with the bath water. When options are limited, as they often are in highly secure, locked down corporate environments, you’d be surprised just how far you can push this much maligned black sheep of the data analysis family and just what you can get out of it, if you approach the job in a realistic fashion.