Re: ODBC Connection - read/write access

From: Alan Brewer [MS] (alanbr@microsoft.com)
Date: 12/05/02 

From: "Alan Brewer [MS]" <alanbr@microsoft.com>
Date: Wed, 4 Dec 2002 19:45:48 -0800

SQL Server will not accept a connection from any API unless that connection
supplies valid login credentials. If your instance of SQL Server only has an
sa account, then anyone connecting to that instance will have to specify the
sa login credentials, and when they are in they will have full
administrative priviledges and can do anything they want.

You have to specifically add logins to SQL Server before other people can
log in to the instance. If you are only using SQL authentication, then you
have to add SQL Server logins and tell the other people what login ID and
password to use. If you are using Windows authentication, you can specify
those Windows accounts which can make connections to your instance of SQL
Server.

Once you have given other people logins, then you create user accounts in
the user databases you want them to access, and associate their logins with
those user accounts. You control their access to objects in the user
databases by assigning permissions to the user accounts. Basically,
individuals only have the permissions assigned to their user account, a role
their account is in, or the public role.

For more information, see these sections in the SQL Server 2000 Books Online
Table of Contents:

SQL Server Architecture
     Relational Database Components
         Logins

SQL Server Architecture
    Database Architecture
       Logical Database Components
           Logins, Users, Roles, and Groups 

--
Alan Brewer
Writer
SQL Server Documentation Team

Relevant Pages

  • Re: System Administrator Implied Permissions
    ... >> Hi Dan, ... >> Now, given this, why does SQL Server ... However, these logins were not ... Other sysadmin role members have the ...
    (microsoft.public.sqlserver.security)
  • Re: SQL Server 2005 Login Problem
    ... There are two authentication method in SQL Server. ... 1- Windows Authentication ... Only creating Logins is not the complete solution of course, then you'll need to map those users to the appropriate databases and assign them roles and grant them permissons. ...
    (microsoft.public.sqlserver.clients)
  • Re: Windows permissions to run Jet OLEDB 4.0
    ... in SQL Server or not when you have to go outside of the server to the ... Actually I was talking about Windows logins. ... There is no security whatsoever implemented on the mdb ...
    (microsoft.public.data.oledb)
  • Re: Logins & Permissions
    ... At server level, we use "Logins" to connect to a SQL Server Instance and perform server level jobs. ... "Users" are used and these users are mapped to Logins. ... I am using SQL Server 2005 on a Windows NT Network ...
    (microsoft.public.sqlserver.security)
  • No Application Logins Allowed - SOX
    ... I'm trying to work through an issue regarding our MS SQL Server logins. ... "Customer" application uses a login to SQL Server called "Customer" and the ... Grant our users Windows Authentication access to SQL Server. ...
    (microsoft.public.sqlserver.security)