Creating a login in SQL Server 2000 Enterprise Manager

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT SQL Server Security The keys to database backup protection for SQL Server Understanding transparent data encryption in SQL Server 2008 The fine line between not encrypting your databases and breach notification Securing SQL Server with access control, login monitoring and DDL triggers SQL Server security: Controlling access via database roles Implementing security audit in SQL Server 2008 New security features in SQL Server 2008 leave some work for you Can I encrypt and restore a database backup in SQL Server 2005? FAQ: How to troubleshoot and grant SQL Server permissions Secure SQL Server from SQL injection attacks Archive: Security Creating a SQL Server user authentication schema Could a join of encrypted SQL Server data have a problem? SQL Server connection lost when SA password is changed How to set SQL Server password for SA login Code to connect SQL Server 7.0 to Visual Basic 6.0 Set SQL Server password on database in version 7.0 Solve SQL Server permissions and authentication problems Create username and password for new SQL Server database Recover password in SQL Server 2000 Protect against SQL Injection by whitelisting

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary data corruption  (SearchSQLServer.com) data hiding  (SearchSQLServer.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

In SQL Server 2000, there are two concepts: a "login" which allows connection to the SQL Server itself, and a "user" which allows connection to a particular database. They may seem to be redundant, but they serve two different purposes. In most cases, there is a 1:1 relationship between a login and a user, just to keep things simple. To create a login, expand out the "Security" folder underneath your SQL Server object in the left window pane. Beneath this folder, you will find an object called "Logins." Right-click "Logins" and select "New Login." Enter the name of the new login and select either Windows-based (more secure) or SQL-based (more compatible) authentication. Enter a password and select a default database for this new login.

Now flip over to the "Database Access" tab. Place a checkbox next to the database that this login should have access. Further down below, under database roles, you will probably want to enable the "db_owner" role, so that this login has full access to the database. When you're done developing or troubleshooting, you'll want to revisit this role and perhaps grant it less rights for increased security.