DocsICP FilingConsole
官方文档
首页

Restart an instance

更新时间：
复制 MD 格式
产品详情
我的收藏

Restart your RDS SQL Server instance to resolve issues such as exhausted connections or degraded performance.

When to restart

Restart an instance when you need to:

  • Resolve issues such as exhausted connections or poor performance.

  • Apply changes to parameters that require a restart.

  • Free TempDB space to unblock a failed storage upgrade.

    Note

    TempDB stores temporary objects and row versions. It is rebuilt on each restart.

  • Temporarily mitigate issues caused by an outdated minor engine version. To resolve them permanently, upgrade the minor engine version.

  • Temporarily mitigate a memory leak in some versions running in database mirroring mode. To resolve it permanently, upgrade the major version.

Prerequisites

Before you begin, ensure that:

  • The instance is in the Running state

Impact

  • Restart duration depends on instance performance, dirty page count, and long-running transactions. In ~90% of cases, connections are interrupted for about 30 seconds. Ensure your application supports automatic reconnection.

    Note

    RDS Basic Edition instances have a single node with no hot standby, so restarts, configuration changes, and version upgrades can cause extended downtime. For high availability, use another edition such as the High-availability Edition. Some Basic Edition instances support an upgrade to the High-availability Edition.

  • Restarting a primary instance does not restart its read-only instances. Replication resumes automatically after the restart.

  • After you initiate a restart, the instance state changes to Restarting, which interrupts connections.

Procedure

  1. Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.

  2. In the upper-right corner of the page, click Restart Instance.

  3. In the confirmation dialog box, click OK.

  4. Complete SMS or MFA verification as prompted.

Related API

To restart an instance programmatically, call RestartRDSInstance.

FAQ

  • Q: For a High-availability Edition instance, does restarting the primary instance trigger a failover?

    A: Restarting reboots both the primary and secondary nodes but does not trigger a failover. Availability zones remain unchanged.

  • Q: Do endpoints and IP addresses change after a restart?

    A: No. Endpoints and IP addresses remain unchanged.

  • Q: What affects restart duration, and how can I reduce it?

    A: A restart has two phases:

    • Shutdown: Duration depends on host and instance performance and dirty page count.

    • Startup: Duration depends on host and instance performance and recovery log size, which correlates with dirty pages and long-running transactions. The recovery interval parameter also affects startup time. Use the default unless you have specific requirements. Configure the recovery interval.

    To reduce restart time, minimize long-running transactions or adjust the recovery interval parameter.

Previous：Auto-renewalNext：Stop and start an RDS SQL Server instance