Choose your database:
AnySQL
MySQL
MS SQL Server
PostgreSQL
SQLite
Firebird
Oracle
SQL Anywhere
DB2
MaxDB

Subscribe to our news:
Partners
Testimonials
Albert Rognan: "Thank you for this quick reply. I must say I am impressed of the number of functions that is available within this tool".
Alex Torin: "Several months ago I downloaded the trial versions of several Microsoft SQL administration tools that I was able to find using google. I had considerable trouble with most of them crashing... but using your product I was able to isolate and solve the problems I was having. I decided to add it to my toolkit and have recommended it to a few others".

More

Add your opinion

Customers
Download Buy

MS SQL Maestro online Help

Prev Return to chapter overview Next

Asymmetric Key login options

Asymmetric Key logins were implemented in Microsoft SQL server 2005.

 

This step of the wizard allows you to specify Asymmetric Key login options according to your needs. The detailed description is given below.

 


 

Name

Specify the name of the Asymmetric Keys login that is created.

Note: the name of the object must be unique among all the object names in the server. You can use any identifier that is allowed by Microsoft SQL server.

 

Enabled

If checked, the login is enabled.

 

Credential

Define here the name of a credential to be mapped to the new SQL Server login. A credential is a record containing the authentication information required for connecting to a resource outside of SQL Server. The credential must already exist in the server.

 

Database

Specify the default database to be assigned to the login. The default database is set to MASTER.

 

Language

Specify the default language to be assigned to the login. The default language is set to the current default language of the server. If the default language of the server is changed in the future, the default language of the login will remain unchanged.

 

Asymmetric Key

Specify the name of an asymmetric key to be associated with this login. This key must already exist in the master database.



Prev Return to chapter overview Next