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

Subscribe to our news:
Partners
Testimonials
Jim Salmons: "That is excellent news! I will look forward to a future update with these features. It will be attention to such details that further distinguishes your excellent products from the competition.

As always, I appreciate your great products and your demonstrated customer service is equal to the high quality of your products".
Paolo Benjamin T. Briones: "I just downloaded the trial and its great! IMHO, its a lot better than the Enterprise Manager from SQL Server".

More

Add your opinion

Customers
Download Buy

MS SQL Maestro online Help

Prev Return to chapter overview Next

Logins

A user passes through two stages of security when working in Microsoft® SQL Server™: authentication and authorization (permissions validation). The authentication stage identifies the user by a login account and verifies only the ability to connect to an instance of SQL Server. If authentication is successful, the user connects to an instance of SQL Server. The user then needs permissions to access databases on the server  done by granting access to an account in each database mapped to the user login.

 

To give permissions for changing server objects to a login, you should include the login into the appropriate server role.

 

There are four types of logins: Windows Authentication, SQL Server Authentication, and also Certificate, and Asymmetric Key for Microsoft SQL Server 2005.

 

•It is recommended to you use Windows Authentication for security reasons because the users who connect through a Microsoft Windows NT® 4.0 or Windows® 2000 user account can make use of trusted connections. Trusted connections are those validated by Windows NT 4.0 or Windows 2000.

 

•It is also possible to connect using SQL Server Authentication. When a user connects with a specified login name and password from a nontrusted connection, SQL Server performs the authentication itself by checking to see if a SQL Server login account has been set up and whether the specified password matches the one previously recorded. If SQL Server does not have a login account set, authentication fails and the user receives an error.

 

•To enable encrypted connections, create login from a Certificate or from an Asymmetric Key.

 

 

New logins are created within Create Login Wizard. In order to run the wizard you should either

 

•select the Logins list or any object from that list and then use the Create New Login item from the popup menu

or

•open the server in Server Editor and the Logins tab there and press Insert or select the Create New Login item from the popup menu (Alternatively, use the corresponding link of the Navigation Bar).

 

 

 

Logins are edited within Login Editor. In order to open the editor you should either

 

•select the login for editing in the explorer tree (type the first letters of the login name for quick search);
•select the Edit Login item from the popup menu

or

•open the server in Server Editor and the Logins tab there;
•select the login to edit;
•press the Enter key or select the Edit Login item from the popup menu (alternatively, you can use the corresponding link of the Navigation Bar).

 

 

 

To drop the existing login:

 

•select the login to drop in the explorer tree;
•select the Drop Login item from the popup menu

or

•open the server in Server Editor and the Logins tab there;
•select the login to drop;
•press the Delete key or select the Drop Login item from the popup menu (alternatively, you may use the corresponding link of the Navigation Bar)

 

and confirm dropping in the dialog window.

 


Prev Return to chapter overview Next