Full Storage of RDS for SQL Server Instances

1. In the instance list, choose More > Scale Storage Space.
2. On the displayed page, the system determines the minimum space required.
   Figure 1 Scaling up storage space
   
3. After the scale-up is successful, check that the instance status becomes Available.
   Figure 2 Checking the instance status
   

For details, see Shrinking Databases.

Figure 3 Checking the LDF file size

1. Query the tempdb database size.

   SELECT name AS FileName,
   size*1.0/128 AS FileSizeInMB,
   CASE max_size
   WHEN 0 THEN 'Autogrowth is off.'
   WHEN -1 THEN 'Autogrowth is on.'
   ELSE 'Log file grows to a maximum size of 2 TB.'
   END,
   growth AS 'GrowthValue',
   'GrowthIncrement' =
   CASE
   WHEN growth = 0 THEN 'Size is fixed.'
   WHEN growth > 0 AND is_percent_growth = 0
   THEN 'Growth value is in 8-KB pages.'
   ELSE 'Growth value is a percentage.'
   END
   FROM tempdb.sys.database_files;

2. Shrink the tempdb database by referring to Shrinking Databases. If the tempdb database is frequently used, the storage usage cannot be effectively reduced.
3. In the instance list, choose More > Reboot to reboot the instance. In this way, the free space of tempdb will be released.
   After the reboot, the instance status becomes Available.

   

   An instance reboot can resolve the full storage problem caused by tempdb. But if the full storage is caused by large LDF files in some databases, a reboot does not work. It may cause databases with large transaction logs to enter the inRecovery state, in which the databases cannot be accessed for a long time. For higher security, you are advised to scale up storage.