“When I need the most optimal solution that’s well documented and, in case of code, well tested, I turn to you, Arjan.
Quality takes time, I know. So, when I have an immediate production problem that needs to be solved asap, I rather ask someone else on our team. Yes, you are capable of providing a quick analysis and provide a temporary solution, but we have others in our team that are more suitable for this. I will end up with you anyway, for the final constructive and durable solution.

Each in its own strength, together we’re a powerful team.“

Feedback by a teamleader of one of my customers..

Database Optimalisatie specialist

I am an experienced Database expert. Most of my experience, I built in the Business Intelligence area: Data Engineering, Data Analysis, Data Extraction, Data Transformation, Data Storage, transform data further into information, up till information provisioning and visualisation.

The combination of database and Business Inteligence provided a fairly unique experience. For Business Intelligence, fast processing large amounts of data is a very important subject, while almost always being processed by systems outside the database. Hence, it’s crucial to have an optimally running database, optimally running processes that use that database as well as their surroundings like network and servers.

Due to my experience in analysing and visualising data, I have a slightly different view on Database Optimisation, compared to others: The number tell the tale. Meanwhile, the sense for figures, combined with understanding the database and SQL that I see, makes that I often already have a gut feeling on where to find the pain points. As a result, I ofthen find the first and biggest optimisations reasonably fast. In the database, as well as in the processes that use the database and the compontents they rely on.

Developers border area

By working with different applications that use relational databases, I learnt a lot about how an application generates its query. Although there usually are some ways to have control in this, that’s often not enough. Hence, it sometimes is more efficient to have the application query a view, User Defined Function or Stored Procedure that catches the database specific complexity. Since I have experienced both sides of the story, I’m very capable of finding the best balance.

Thanks to these experiences, I’m increasingly approached by application developers. Programming languages like C#, Java, C++, GoLang and Swift have great database connection frameworks that ease up a programmers live to a large extent. Application developers hardly need to know SQL, the framework translates the application code into SQL. Even though these frameworks are surprisingly capable of generating good queries, I still see pretty inefficient queries come by in the database.

By combining my knowledge with the application developers experience, it usually is possible to adjust the application in such a way that an inefficient query is transformed into a very efficient query. Resulting in huge performance gains, thus lower processing costs, faster results and happier users. Sometimes it’s a matter of simply changing the order in which the application code is processed, on other moments  it requires the writing of a database specific Stored Procedure or User Defined Function.

Meanwhile poor performance is often not caused by bad queries but by poor maintenance. Often because the database has been setup by developers rather than a DBA, sometimes due to miscommunication between developers and DBA’s. Since I have experience in both area’s, I can quickly identify the real cause and solve it. Sometimes by setting up proper automated maintenance, often by bridging between developer and DBA.

Core competences

  • Quality, openness and honesty.
  • Good eye for maintainability
  • Extensive ICT knowledge, experience and interests, both on technical and functional level.
  • Extensive industry knowledge and experience
  • Ability to communicate difficult or complex situations in an easy and understandable way
  • Think and work in line with the Agile en Lean principles (Scrum framework)
  • High level of analytical capacities
  • Able to think and work off the beaten track

Minimal risk exposure under the enforcement of the DBA Act

My knowledge and experience may not be unique, but it is certainly not very common in the Netherlands or even Europe. My assignment is almost always temporary. It lasts for the duration of a new-build project, or until all databases run optimally again and the permanent team is sufficiently trained to maintain the system independently.

Furthermore, I have been managing my own appropriate pension plan for years. I hold suitable income protection and liability insurance, build up financial reserves for periods between contracts, and pay my tax correctly and on time. The Dutch tax authorities are fully aware of this through my income tax returns.

With the correct project formulation in the agreement, combined with a truly market-rate tariff that is not unilaterally imposed by the client or an intermediary, my assignment poses absolutely no risk regarding compliance with the DBA Act.