Angel Mena Sancho

This is a database with more than 100 GB of information for several thousand patients and over the past 15 years, it was often crashing.

After implementing performance optimizations and the maintenance plan, it is now working quite well—supporting about 200 simultaneous users (doctors and finance).

This is a set of performance improvements in some indexes, views, and database triggers that left some programs out of service and was fixed after the improvements. The database is being used by more than 200 simultaneous users and the size is about 300 GB.

I optimized several SQL Server databases in order to search for the root reason, verify the changes in a QA environment and make the corresponding changes in production.

This involved sometimes creating archiving processes or just removing obsolete information. I spent spare my spare time encouraging developers to follow best practices to reduce the workload on the servers. One recent personal win was reworking a C# program that initially took almost 20 minutes to open. After migrating the code to a stored procedure—where it does all of the hard work—it now takes only 15 seconds.

I extracted ad hoc queries from an external Oracle database to import in the main SQL Server database or exporting to Microsoft Access or Excel to give to some power users the possibility to extract the relevant information.

I migrated an existing KPI system in MS Excel into SQL Server. Part of the job was to modify the structure. This was done to normalize it, enable it to be queried from different perspectives, and also to export the summaries into Excel, QlikView, and Power BI to obtain the final dashboards.

I created the main archiving/removal system to move the old data to the archive database and remove definitively the obsolete data (older than five years).

The system is based on SQL Server stored procedures and launched from SQL Server Jobs, giving visibility of the results in audit tables to understand the results for each different database.

I created several programs to get files from FTP, upload them into internal databases, and transform them when required. The information is visible for the users by a Microsoft Access front end so that they can export to Excel to share with third-party teams.

There was a Microsoft Access database that had to make several calculations and took about eight hours. That process was launched once per week and a user had to click to start each different step.

Once it was migrated to SQL Server, I implemented some performance improvements so that the process runs during a database job, overnight and takes about 30 minutes. So, it can be launched automatically every day and nobody has to click and wait anymore.

On this project, I created a very detailed reporting system that reads from an existing database, summarizes the transport incidences, shows the ones pending of payment, and summarizes the ones that are in each different status.

There are two main groups of reports: monthly and quarterly with completely different layouts and filtering criteria. Additionally, for an incidence and per user request, the system prepares an official form (in Excel format) and inserts it in a draft email with also a predefined format in HTML that can be sent to the relevant stakeholders after manual revision if required or just as the system generated it if not.

For a financial model, I created a series of macros to reduce repetitive work and allow the user to focus on analyzing the data to make the best business decisions.

Over the course of 18 years, I've developed and maintained the billing system in Microsoft Access with SQL Server and connected it with the accounting system for finances with Suite CRM (MySQL) to allow the sales department to visualize the bills per customer and also included different data exports to Excel to send bills per EDI or to see sales statistics graphically.