SQL Server Authentication Question (easy I think)

From: James (anonymous_at_discussions.microsoft.com)
Date: 02/23/05


Date: Wed, 23 Feb 2005 12:55:05 -0800

What do you mean by;
'I assigned a domain user as the SQL username as
well.......'

You can not have both 'DOMAIN1\User1' domain account
and 'User1' SQL Server account. It is one or the other. If
you only use 'DOMAIN1\User1' account and put this account
into a local administrators group of the SQL Server
computer, the account will have automatic admin access to
the SQL Server unless some one removes
the 'BUILTIN\Administrators' account from the SQL Server.

You can also pull this domain account from the SQL Server
(Enterprise Manager-->Security-->Logins...New Login...name)
and give it a sysadmin role in Enterprise manager.

If you use 'User1' SQL server account, then give it a
sysadmin priviladges in SQL Server if you want to......

>-----Original Message-----
>I don't know if I have the authentication setup correctly
on my SQL server.
>I set the authentication to use SQL and Windows (instead
of just Windows).
>
>I assigned a domain user as the SQL username as well, and
belongs to the
>administrators group.
>
>I have an application which is supposed to offer a
connection string to the
>SQL server and modify a table. However, each time I
attempt to connect - I
>get a logon failure in the event viewer. UNLESS I leave
the user ID and
>password blank - then it connect perfectly well. I look
in event viewer and
>see that when the UID and PWD fields are left blank, it
is logging on as
>administrator.
>
>What am I missing?
>
>How can I setup UserA on the SQL server, and have ONLY
UserA be able to
>access the database from the network? What could I be
missing which is
>causing valid usernames to be declined, yet allows the
admin to logon
>(default when UserID and Password fields are left blank
in my connection
>string?)
>
>Any help would be greatly appreciated.
>
>I am new to SQL and it is entirely possible that I set
something up
>incorrectly during install or something.
>
>Thanks.
>.
>



Relevant Pages

  • Re: SQL account rights
    ... Please advice what is the best, suitable rights rather than domain admin ... Warren Brunk - MCITP - SQL 2005, ... Add it as a login to the SQL Server ... files, or backups, make sure that the service account has Full ...
    (microsoft.public.sqlserver.security)
  • Re: User authentication
    ... There are 2 SQL Server 2005 ... 1 SQL Server 2000 installed on another server ... Windows account instead to run backup jobs. ...
    (microsoft.public.sqlserver.clients)
  • Re: SQL 2000 Server gets hacked
    ... Thank you Beth. ... > placed a strong password on the 'sa' account?) ... Your SQl Service itself shouldn't be running as a ... (SQL Agent requires more, but not SQL Server). ...
    (microsoft.public.sqlserver.security)
  • Re: SQL 2000 Server gets hacked
    ... Thank you Beth. ... > placed a strong password on the 'sa' account?) ... Your SQl Service itself shouldn't be running as a ... (SQL Agent requires more, but not SQL Server). ...
    (microsoft.public.sqlserver.security)
  • Re: Microsoft Search service cannot be administered under the present user error SP3
    ... - Have not modified Administrator account, but i ran the SQL script anyway. ... SQL account is not a local administrator. ... > has this server ever been upgrade from SQL Server 7.0 or is this SQL ...
    (microsoft.public.sqlserver.fulltext)