Connect to SQL Server 2012
- On the File menu, select Connect to SQL Server.
If you previously connected to SQL Server, the command name will be Reconnect to SQL Server.
- In the Server name box, enter or select the name of the instance of SQL Server.
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, enter the computer name, a backslash, and the instance name. For example: MyServer\MyInstance.
- To connect to an active user instance of SQL Server Express, connect by using named pipes protocol and specifying the pipe name, such as \\.\pipe\sql\query. For more information, see the SQL Server Express documentation.
- If your instance of SQL Server is configured to accept connections on a non-default port, enter the port number that is used for SQL Server connections in the Server port box. For the default instance of SQL Server, the default port number is 1433. For named instances, SSMA will try to obtain the port number from the SQL Server Browser Service.
- In the Database box, enter the name of the target database for object and data migration.
This option is not available when reconnecting to SQL Server.
The target database name cannot contain spaces or special characters. For example, you can migrate Access databases to a SQL Server database named "abc". But you cannot migrate Access databases to a SQL Server database named "a b-c".
- In the Authentication drop-down menu, select the authentication type to use for the connection. To use the current Windows account, select Windows Authentication. To use a SQL Server login, select SQL Server Authentication, and then provide a user name and password.
- For Secure connection, two controls are added, Encrypt Connection Checkbox and TrustServerCertificate Checkbox. Only when Encrypt Connection Checkbox is checked TrustServerCertificate Checkbox is visible. When Encrypt Connection is checked(true) and TrustServerCertificate is unchecked(false), will validate the SQL Server 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.
- Click Connect.
Higher version compatibility
It is allowed to connect/reconnect to higher versions of SQL Server.
- You will be able to connect to SQL Server 2008 or SQL Server 2012 when the project created is SQL Server 2005.
- You will be able to connect to SQL Server 2012 when the project created is SQL Server 2008 but it is not allowed to connect to lower versions i.e. SQL Server 2005.
- You will be able to connect to only SQL Server 2012 when the project created is SQL Server 2012.
- Higher version compatibility is not valid for SQL Azure.
Conversion of the database objects is carried out as per the project type but not as per the version of the SQL Server connected to. In case of SQL Server 2005 project, Conversion is carried out as per SQL Server 2005 even though you are connected to a higher version of SQL Server (SQL Server 2008/SQL Server 2012/SQL Server 2014/SQL Server 2016).
If SQL Server schemas change after you connect, you can synchronize the metadata with the server.
To synchronize SQL Server metadata
- In SQL Server Metadata Explorer, right click Databases, and then select Synchronize with Database.
Reconnecting to SQL Server
Your connection to SQL Server stays active until you close the project. When you reopen the project, you must reconnect to SQL Server if you want an active connection to the server. You can work offline until you load database objects into SQL Server and migrate data.
The procedure for reconnecting to SQL Server is the same as the procedure for establishing a connection.