Maintenance process for Serverless SQL Databases

Overview

To add features, deploy security fixes or corrective patches, we perform regular maintenance operations. Most maintenance operations are transparent to you, and have no impact on your database availability, or performance.

However, some maintenance operations may impact your database availability or require actions on your side. In this case, we will inform you beforehand, so you can follow the recommendations below to ensure that the impact on your application is minimal.

The maintenance operations particularly concern our connection pooler for now, as we are working on making it as transparent as possible in future Serverless SQL Databases updates.

Impact on your application and recommendations

A maintenance operation impacting your SQL client connections to the database will usually:

• Disconnect your SQL connections to the database during less than 1 minute

• Require your SQL client to reconnect afterward

To avoid requiring any manual actions on your side, we recommend you ensure that your applications or SQL clients can reconnect automatically. This is the default behavior with most web application frameworks or software relying on SQL Databases.

Maintenance period and communication delay

We will communicate the maintenance period at least 1 week in advance for low-impact operations, such as unavailability below 1 minute, and up to 1 month in advance for higher-impact operations.

By default, we plan a maintenance period every Tuesday between 14:30 pm and 14:45 pm (CEST), that disconnects SQL clients from your database for at most 1 minute.

Any change to this period or additional maintenance periods will be communicated specifically.