選取您的 Cookie 偏好設定

我們使用提供自身網站和服務所需的基本 Cookie 和類似工具。我們使用效能 Cookie 收集匿名統計資料,以便了解客戶如何使用我們的網站並進行改進。基本 Cookie 無法停用,但可以按一下「自訂」或「拒絕」以拒絕效能 Cookie。

如果您同意,AWS 與經核准的第三方也會使用 Cookie 提供實用的網站功能、記住您的偏好設定,並顯示相關內容,包括相關廣告。若要接受或拒絕所有非必要 Cookie,請按一下「接受」或「拒絕」。若要進行更詳細的選擇,請按一下「自訂」。

Importing the database

焦點模式
Importing the database - AMS Advanced Application Developer's Guide
此頁面尚未翻譯為您的語言。 請求翻譯

To import the database (DB), follow these steps.

  1. Back up your source on-premises database using MS SQL Native backup and restore (see Support for native backup and restore in SQL Server). As the result of running that operation, you should have a .bak (backup) file.

  2. Upload the .bak file to and existing transit S3 bucket using the AWS S3 CLI or AWS S3 console. For information on transit S3 buckets, see Protecting data using encryption.

  3. Import the .bak file into a new DB on your target RDS for SQL Server MS SQL instance (for details on types, see Amazon RDS for MySQL instance types):

    1. Log into the EC2 instance (on-premises workstation) and open MS SQL Management Studio

    2. Connect to the target RDS instance created as prerequisite in step #1. Follow this procedure to connect: Connecting to a DB Instance Running the Microsoft SQL Server Database Engine

    3. Start the import (restore) job with a new Structured Query Language (SQL) query (for details on SQL queries, see Introduction to SQL). The target database name must be new (do not use the same name as the database that you previously created). Example without encryption:

      exec msdb.dbo.rds_restore_database @restore_db_name=TARGET_DB_NAME, @s3_arn_to_restore_from='arn:aws:s3:::BUCKET_NAME/FILENAME.bak';
    4. Periodically check the status of the import job by running this query in a separate window:

      exec msdb.dbo.rds_task_status;

      If the status changes to Failed, look for the failure details in the message.

下一個主題:

Cleanup

上一個主題:

Setting up
隱私權網站條款Cookie 偏好設定
© 2025, Amazon Web Services, Inc.或其附屬公司。保留所有權利。