Malik Rizwan Ashgar

BACKGROUND
An Australian-based healthcare company required a live database migration from Microsoft SQL Server to PostgreSQL. The client's primary goal was to cut operational and maintenance costs with improved performance, making open-source technology the best option.

ROLE AND PROCESS
While leading a team of two senior SQL developers to accomplish this task from end to end, I understood and communicated the business logic of the existing system and guided team members accordingly.

I planned and divided the migration into smaller tasks and distributed them among team members. We started the migration by exporting objects and data into PostgreSQL and then manually carried out dynamic programming objects—stored procedures and functions. I performed all the relevant testing to ensure everything worked perfectly with the same output on the new server. Finally, we handed over the 100% working product in PostgreSQL to the client, which was later integrated smoothly with the application.

RESULTS
The migration helped the client seamlessly shift the application to the new back-end database technology. The change cut costs and improved performance because everything was upgraded during the migration to the new server.

BACKGROUND
A bank in Qatar required the implementation of an AML module for one of its banking applications. The existing system had data scattered in different sources—mostly in Oracle and Sybase with few flat files and reports.

ROLE AND PROCESS
As an SQL consultant, I delivered all the complex data extraction and transformation scripts, including SSIS packages. I remained involved in the data warehouse design and development in Microsoft SQL Server, where the final transformed datasets were loaded. I scheduled nightly jobs to run all the scripts and SSIS packages to extract data from the source technologies and load into the Microsoft SQL Server data warehouse.

RESULTS
I single-handedly developed the end-to-end solution in six months with minimal supervision. The bank implemented the final product, which helped them identify suspicious and fraudulent transactions to minimize money laundering risk.

BACKGROUND
After the database design and development cycle to architect a multitenant healthcare database for a US-based company was complete, we had to transform the existing system from a single-client-based database to a multitenant product. The objective of this new database was to improve performance and provide a self-driven registration system for physicians.

ROLE AND PROCESS
I led a team of two SQL developers to design the database from scratch and develop it into the entire product based on the client's existing system. Once I understood the business logic for all the relevant modules for physicians, patients, hospitals, insurance, and billing, I guided the team members to design the new architecture for the multitenant database. We developed and transformed all the relevant programming objects to deliver more robust and efficient performance. After my team designed the new database, I collaborated with the development teams to integrate it with newly developed interfaces.

RESULT
The final product was responsive, self-driven, and fast.