Microsoft Workloads for AWS

Optimize your Microsoft Workloads with AWS.

In our permanent search for best in class solutions for our customers, we have developed a specific competency around Microsoft Workloads on AWS. Amazon allows SQL server and Microsoft Workloads license migration to benefit amongst others from the induced cost reduction.

We propose:

  • An initial analysis to validate your actual structure and its associated costs, possible enhancements with expected benefits (your Business Case)
  • A complete migration plan for identified assets.
  • A follow-up to finalize finest sizing base on real usage.


Our customers opting to migrate their Microsoft assets have seen their license costs reduced by over 80% for SQL servers, over 40% for Windows Servers, and over 20% for Microsoft Workloads.

Leverage the power of your Windows Access databases by hosting them on AWS

In order to be able to generate of additional services for Database management (access, extraction, monitoring, reporting…), Schneider Electric decided to host some MS Access databases on AWS, and they asked us to create additional services to maximize benefits of this decision.

Microsoft Workloads AWS

To maximize benefits derived from an AWS hosting, it was necessary to create additional web services to enhance hybrid Data Management (from Oracle to MS Access hosted on AWS) for the customer.

The addition of dedicated webservices shapes a made to measure solution, which blends exiting processes, legacy solutions and hybrid hosting and services, for the benefit of the users.

To create the solution desired by the customer, we :

  • Developed a Webservice to be called from an Oracle Database and to automatically generate MS Access databases Reports, We also provided Support on MS Access DB extractions.
  • Developed a monitoring and reporting system, to do various checks on several Database services, and to send mails in case of failure detections. This system also sends daily html reports on application workflow health and status.

We used Java & windows Shell to write the webservices, and Windows PowerShell to write the monitoring and reporting system.

We also leveraged EC2 servers to support our Windows servers used for this solution. Our approach involved, MS Access and Java on a Windows Server 2012 R2.

MS Access Databases were originally generated and checked manually by a dedicated user daily. We have automated this process to save time and raise overall quality and reliability.

We also took advantage to enhance to Database services’ monitoring, which in turn raises reactivity in case of issues. Daily reports are now sent out to hundreds of customers to share an overview of the application’s workflows status and health.

E-b-trans Group : SQL Server migration to AWS RDS, a fully mastered process

E-b-trans Group uses SQL server bases, 2008 R2 version. AWS announced an automatic migration of RDS instances from SQL Server 2008 to SQL Server 2017 on Jun 1st, 2019.
E-b-trans asked Edifixio to migrate its instances RDS SQL Server 2008 R2 before that date, ensuring services continuity, and with a strict intervention planning.

Early 2019, E-b-trans Group was using several SQL Server 2008 R2 Express Edition on AWS RDS databases for Production applications.

It was therefore necessary to upgrade before Jun 1st, 2019 to avoid automated upgrade during work time on Production applications.

Databases version were upgraded directly on Production bases (no other database on which to test before hand), in a transparent manner, out of working hours, et with no impact for final users. 

The project required a deep involvement from the customer teams, in order to validate application behavior post migration to SQL Server 2017.

Critical Migration Project, considering possible adverse business impacts, which required making sure the whole process was mastered from end to end.


The migration did not pose great technical challenges, but the timeframe to execute was a strong constraint to be managed.

Edifixio’s DBA scripted all control action to be undertaken, while taking all necessary precautions such as:

1.    RDS Instance save before upgrade
2.    Stop RDS instance monitoring
3.    Stop scoped applications
4.    Upgrade RDS Instance to SQL Server 2017
5.    Restart of scoped applications
6.    Restart of RDS Instance monitoring
7.    Application E2E testing

This step by step approach is the guarantee to a successful migration, including for hybrid solutions.