BI Architect and Developer in Zagreb, Croatia

This project required knowledge of a wide technology stack (Excel/VBA, Access, SQL database, Salesforce, and Qlik) and analysis of the existing business process.

My role, as part of the reporting department, was to get myself up to date with the existing setup, propose improvements, and develop modules that would support new requirements of the marketing and sales departments. The work focused on updating the reporting/database solutions and to remove the use of Excel, as much as possible in daily business operations.

This project required the creation of migration scripts from an existing SQL Server database to a new installation of SQL Server database. As users on the other side were not very familiar with this technology, the project included very detailed documentation so that they can do some easier modifications on their own without any specialized support. Also created a proof-of-concept on how to use Azure PowerBI instead of Excel reporting.

On this project, my role was as the data warehousing expert—working on the SQL Server and I was ultimately responsible for designing data warehouse tables. I also implemented the ETL processes using SSIS and SQL and optimized the existing data warehouse loading procedures.

I wrote a software development lifecycle guide (SDLC) for a software company that needed to map its development processes in a formal document.

For this project, I worked on the migration of an existing web application. My tasks were making sure that the Oracle database was properly migrated to a new SQL Server to support a newly purchased solution. I did everything from analysis, implementation, testing, and finally cutover procedures.

While often overlooked, the data warehouse enables companies to reveal valuable insights concealed within their vast data troves. In this article, as a domain expert, I share foundational principles and applications that are essential knowledge for all modern managers.

Data is a key asset of any company, particularly transactional data which holds business secrets such as financial or health records. Data is most vulnerable in transit between the server that stores it and that client that requests it.

The standard approach to ensuring security is to encrypt data on the server and use the SSL-enabled HTTPS protocol to secure data in transport. However, what if we could increase the level of security even further, by using HTTPS and sending data in an encrypted format over the communication line, only to decrypt data on clients who have valid certificates? That approach would make a traditional man-in-the-middle (MITM) attack much more difficult.

Microsoft’s solution to this problem is Always Encrypted, a way to send encrypted data over the pipeline and decrypt it only by users with access to valid certificates. So, even if the attacker gets the data, without a proper certificate stored on the client machine, the data would be useless.
This article describes how to set up and use Always Encrypted, and it’s recommended reading for anyone who is sending important data over the public communication lines, even if they are secured with SSL.