Skip to content

Latest commit

 

History

History
101 lines (65 loc) · 9.89 KB

connecting-to-sql-server-sybasetosql.md

File metadata and controls

101 lines (65 loc) · 9.89 KB
Raw
title description author ms.author ms.date ms.service ms.subservice ms.topic ms.custom helpviewer_keywords
Connecting to SQL Server (SybaseToSQL)
Connecting to SQL Server (SybaseToSQL)
cpichuka
cpichuka
11/16/2020
sql
ssma
conceptual
sql-migration-content
Connecting to SQL Server

Connecting to SQL Server (SybaseToSQL)

To migrate Sybase Adaptive Server Enterprise (ASE) databases to [!INCLUDEssNoVersion], you must connect to the target instance of the [!INCLUDEssNoVersion]. When you connect, SSMA obtains metadata about all the databases in the instance of [!INCLUDEssNoVersion] and displays database metadata in the SQL Server Metadata Explorer. SSMA stores information about which instance of [!INCLUDEssNoVersion] you are connected to, but does not store passwords.

Your connection to [!INCLUDEssNoVersion] stays active until you close the project. When you reopen the project, you must reconnect to [!INCLUDEssNoVersion] if you want an active connection to the server. You can work offline until you load database objects into [!INCLUDEssNoVersion] and migrate data.

Metadata about the instance of [!INCLUDEssNoVersion] is not automatically synchronized. Instead, if you want to update the metadata in SQL Server Metadata Explorer, you must manually update the [!INCLUDEssNoVersion] metadata, as described in the "Synchronizing SQL Server Metadata" section later in this topic.

Required SQL Server Permissions

The account that is used to connect to [!INCLUDEssNoVersion] requires different permissions depending on the actions that the account performs:

  • To convert ASE objects to [!INCLUDEtsql] syntax, to update metadata from [!INCLUDEssNoVersion], or to save converted syntax to scripts, the account must have permission to log on to the instance of [!INCLUDEssNoVersion].

  • To load database objects into [!INCLUDEssNoVersion], the account must be a member of the db_ddladmin database role.

  • To migrate data to [!INCLUDEssNoVersion], the account must be:

    • A member of the db_owner database role, if using client-side data migration engine.
    • A member of the sysadmin server role, if using server-side data migration engine. This is required to create the CmdExec [!INCLUDEssNoVersion] Agent job step during data migration to run SSMA bulk copy tool.

      [!NOTE] [!INCLUDEssNoVersion] Agent proxy accounts are not supported by the server-side data migration.

  • To run the code that is generated by SSMA, the account must have EXECUTE permissions for all user-defined functions in the ssma_syb schema of the target database. These functions provide equivalent functionality of ASE system functions, and are used by converted objects.

Establishing a SQL Server Connection

Before you convert ASE database objects to [!INCLUDEssNoVersion] syntax, you must establish a connection to the instance of [!INCLUDEssNoVersion] where you want to migrate the ASE database or databases.

When you define the connection properties, you also specify the database where objects and data will be migrated. You can customize this mapping at the ASE schema level after you connect to [!INCLUDEssNoVersion]. For more information, see Mapping Sybase ASE Schemas to SQL Server Schemas (SybaseToSQL).

Important

Before you try to connect to [!INCLUDEssNoVersion], make sure that the instance of [!INCLUDEssNoVersion] is running and can accept connections.

To connect to [!INCLUDEssNoVersion]:

  1. On the File menu, select Connect to SQL Server. If you previously connected to [!INCLUDEssNoVersion], the command name will be Reconnect to SQL Server.

  2. In the connection dialog box, enter or select the name of the instance of [!INCLUDEssNoVersion].

    • If you are connecting to the default instance on the local computer, you can enter localhost or a dot (.).
    • If you are connecting to the default instance on another computer, enter the name of the computer.
    • If you are connecting to a named instance on another computer, enter the computer name followed by a backslash and then the instance name, such as MyServer\MyInstance.

  3. If your instance of [!INCLUDEssNoVersion] is configured to accept connections on a non-default port, enter the port number that is used for [!INCLUDEssNoVersion] connections in the Server port box. For the default instance of [!INCLUDEssNoVersion], the default port number is 1433. For named instances, SSMA will try to obtain the port number from the [!INCLUDEssNoVersion] Browser Service.

  4. In the Database box, enter the name of the target database. This option is not available when reconnecting to [!INCLUDEssNoVersion].

  5. In the Authentication box, select the authentication type to use for the connection. To use the current Windows account, select Windows Authentication. To use a [!INCLUDEssNoVersion] login, select SQL Server Authentication and then provide login name and password.

  6. For Secure connection, two controls are added, the Encrypt Connection and TrustServerCertificate check boxes. Only when Encrypt Connection is checked, the TrustServerCertificate check box is visible. When Encrypt Connection is checked (true) and TrustServerCertificate is unchecked (false), it will validate the [!INCLUDEssNoVersion] SSL certificate. Validating the server certificate is a part of the SSL handshake and ensures that the server is the correct server to connect to. To ensure this, a certificate must be installed on the client side as well as on the server side.

  7. Click Connect.

Important

While you may connect to a higher version of [!INCLUDEssNoVersion], compared to the version chosen when the migration project was created, conversion of the database objects is determined by the target version of the project and not the version of the [!INCLUDEssNoVersion] you are connected to.

Reconnecting to SQL Server

Your connection to [!INCLUDEssNoVersion] stays active until you close the project. When you reopen the project, you must reconnect to [!INCLUDEssNoVersion] if you want an active connection to the server. You can work offline until you update metadata, load database objects into [!INCLUDEssNoVersion], and migrate data.

The procedure for reconnecting to [!INCLUDEssNoVersion] is the same as the procedure for establishing a connection.

Synchronizing SQL Server Metadata

Metadata about the [!INCLUDEssNoVersion] databases is not automatically updated. The metadata in SQL Server Metadata Explorer is a snapshot of the metadata when you first connected to [!INCLUDEssNoVersion], or the last time that you manually updated metadata. You can manually update metadata for all databases, or for any single database or database object. To synchronize metadata:

  1. Make sure that you are connected to [!INCLUDEssNoVersion].

  2. In SQL Server Metadata Explorer, select the check box next to the database or database schema that you want to update. For example, to update the metadata for all databases, select the box next to Databases.

  3. Right-click Databases or the individual database or database schema, and then select Synchronize with Database.

Next Step

The next step in the migration depends on your project needs:

See Also

Migrating Sybase ASE Databases to SQL Server - Azure SQL Database (SybaseToSQL)