Access a DB server from outside the cloud

Prev Next

Available in Classic

Using SQL Server Management Studio (SSMS), an MSSQL client, you can connect to an MSSQL server from outside the NAVER Cloud Platform and conveniently perform various database-related tasks through a GUI-based client.

Connect using MSSQL SSMS

You can use SSMS, an MSSQL client, to connect to an MSSQL server from outside the NAVER Cloud Platform and perform tasks. To connect to an MSSQL server through SSMS, you must first configure either NAVER Cloud SSL VPN or a public domain for the MSSQL server.

Connect using SSL VPN

After subscribing to and configuring NAVER Cloud SSL VPN, you can connect through SSMS. SSL VPN provides a private network protected by SSL encryption. By configuring routing and ACG settings, you can restrict access to authorized users only, enabling more secure server access and usage.

To connect to an MSSQL server through SSMS after configuring SSL VPN:

Caution

Additional charges apply when subscribing to SSL VPN. For information about SSL VPN and pricing, see Services > Security > SSL VPN on the NAVER Cloud Platform portal.

  1. See the SSL VPN user guide to complete the subscription and configuration, then connect to SSL VPN.
  2. In the Classic environment of the NAVER Cloud Platform console, navigate to i_menu > Services > Database > Cloud DB for MSSQL.
  3. Click the DB server menu.
  4. Select the MSSQL server you want to connect to, then configure the ACG settings by referring to the ACG configuration.
    • Access source: IP pool of the SSL VPN
    • Allowed port (service): Connection port of the MSSQL server
  5. Navigate to DB management > DB User management, then verify the users who will connect through SSL VPN.
  6. Download SSMS and install it according to the guide.
  7. Run SSMS, then create a new MSSQL connection as shown below:
    clouddbformssql-ssms_01_vpc_ko
    • Server type: Database engine
    • Server name: DNS name and DB connection port (separated by a comma)
      • DNS name: The private domain of the MSSQL server to connect to
      • DB connection port: The connection port of the MSSQL server to connect to
    • Certificate: SQL server certificate
      • Login: The user account name of the MSSQL server to connect to
      • Password: The user account password of the MSSQL server to connect to
  8. Click [Connect] to connect to the MSSQL server.
  9. See the guide for usage instructions.

Connect using a public domain

After configuring a public domain for the MSSQL server, you can connect to the server through an MSSQL client.

To connect to an MSSQL server through SSMS after configuring a public domain:

Caution

Data communicated externally through a public domain is billed as network usage.

  1. In the Classic environment of the NAVER Cloud Platform console, navigate to i_menu > Services > Database > Cloud DB for MSSQL.
  2. Click the DB server menu.
  3. Select the MSSQL server for which you want to configure a public domain, navigate to DB management > Public domain management, and click [Yes] in the configuration popup.
  4. Configure the ACG for the selected MSSQL server by referring to the ACG configuration.
  5. Navigate to DB management > DB User management, then verify the users who will connect through the public domain.
  6. Download SSMS and install it according to the guide.
  7. Run SSMS, then create a new MSSQL connection as shown below:
    clouddbformssql-ssms_01_vpc_ko
    • Server type: Database engine
    • Server name: DNS name and DB connection port (separated by a comma)
      • DNS name: The public domain of the MSSQL server to connect to
      • DB connection port: The connection port of the MSSQL server to connect to
    • Certificate: SQL server certificate
      • Login: The user account name of the MSSQL server to connect to
      • Password: The user account password of the MSSQL server to connect to
  8. Click [Connect] to connect to the MSSQL server.
  9. See the guide for usage instructions.
Caution

  • If you change DB accounts through SSMS, some features in the console may be restricted.

  • If you create users or change passwords directly in SSMS, the permission and password changes are not replicated to the mirrored server. As a result, issues may occur during failover.

  • If you create a database directly in SSMS, you must select the Full recovery model in the options to enable mirroring configuration.