Every SQL developer or DBA’s worst nightmare…
“My report is taking ages to load!”
“The figures on my report are wrong!”
“My two reports are showing different revenue figures!”
These were regular comments for the data team at Evolution, from directors and team leaders who were attempting to make business decisions based on outdated, slow performing reports. It led to a reactive team, tending to multiple Helpdesk based questions, as opposed to proactive work like any good development team should strive towards.
This was the chaos before the calm…
The SQL code written to populate and retrieve the data on existing reporting was not particularly bad code. Attempting to add indexes, refactor code and bend the mechanics of SQL Server to improve population and loading speeds was just not going to work. The code was built to serve its purpose over 10 years ago, to a company of no more than 10 consultants, with five KPIs each and maybe a year or two’s worth of data.
Evolution’s rapid upscaling over the years meant that the code was now trying to achieve the same processing and reporting for 100+ consultants, all with 10+ KPIs and 12 years of data. Something drastic needed to change in the code, and it needed to be done quickly in order to provide the business with its core reporting, without which the company would struggle to make key decisions.
The legacy code we ran had multiple issues:
This led to drastic change; a complete re-write of the current ETL methods being used. The task was described as replacing the engine on an aged, slow running and unreliable car. We would worry about the appearance and fancy front-ends later.
After multiple attempts at speeding up the existing code, which would patch up some slower running queries for a short period, the inevitable happened. The reports became unusable, to the point where returning data was taking up to 30 minutes.
It was time for a change… The data needed to be stored in a well-structured, cleansed state, away from the busy transactional databases; a king of truth which everybody understood and could trust. In came BI, a term that is so commonly thrown around in the SQL industry – this was the gateway to our fast reporting to serve the business the data it needed at its finger tips.
Something that the data and development teams at Evolution pride themselves on is the Kanban and Agile methodologies. These processes were absolutely vital to providing continuous integration on the project, delivering the business exactly what it needed in small chunks and, most importantly, in the right order! It allowed us to get value out to stakeholders and consultants fast, with the ability for the users to give us a continuous feedback loop, thus directing the data team on where to develop next.
Replacing the old car’s engine; the details:
The outcome of going through a move to BI methods has made the data team far less reactive and inevitably happier to answer queries on the data. We have restored trust in our reports, and can understand exactly how our figures are produced and maintained. Most importantly, the team rarely receives the dreaded comments mentioned at the beginning, as team leaders and directors have faster loading, regularly updated and trustworthy reports to enjoy using.
We continue to develop and deliver iteratively on the reports, using Kanban to stop starting, and start finishing projects.
As the 13th largest economy around the globe, Australia seems to be thriving in the economic sector...
Surer is a cloud-based, web platform that helps all parties, from insurers to agents to financial...
Data Analysis is a crucial step in the field of Data Science. It involves extracting insights and...