How to login to SQL 2005 using your Domain credentials in "SQL Server Authentication" mode

Hi all. We have several consultants on site that need access to our SQL
server databases. They have accounts in our domain and I would like to use
those accounts in SQL 2005 (actually, as part of a Development group).
Since their machines are not part of our Domain, they cannot use Windows
Authentication to connect. How can I use SQL Server Authentication and
their Domain accounts to allow them to connect to the server?
I have tried using the accounts as Domain\Username in the Login box, but I
always get 'Microsoft SQL Server, Error: 18456' (I can use other non-Domain
accounts to login successfully, so I know the conenctivity is OK).
Any help would be appreciated.
--
Thanks,
TheBurgerMan
at
gmail.com
--TheBurgerMan wrote:
> Hi all. We have several consultants on site that need access to our SQL
> server databases. They have accounts in our domain and I would like to use
> those accounts in SQL 2005 (actually, as part of a Development group).
> Since their machines are not part of our Domain, they cannot use Windows
> Authentication to connect. How can I use SQL Server Authentication and
> their Domain accounts to allow them to connect to the server?
> I have tried using the accounts as Domain\Username in the Login box, but I
> always get 'Microsoft SQL Server, Error: 18456' (I can use other non-Domain
> accounts to login successfully, so I know the conenctivity is OK).
> Any help would be appreciated.
>
When you've tried setting these accounts up as Domain\Username, are you
using your domain name, or theirs? Is your server a member of your domain?|||The Consultant machines are not members of my Domain, but they are using
Domain accounts that I have created. When I created the Consultant
accounts, I added them to the Development Group which has profecient rights
in SQL server to log in and manipulate databases (my account is a member of
this group).
I tried the same test on my laptop! I can login with SQL Server Auth into
an account that I created on the server AND I can login with Windows
Authentication (because my machine is a member of the Domain), but I cannot
login with SQL Server Auth with my Domain account! This is what I want to
do (then I do not have to start creating a pile of seperate accounts in SQL
server as well as AD).
--
Thanks,
TheBurgerMan
at
gmail.com
--
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:OyS%23heUmGHA.5076@.TK2MSFTNGP02.phx.gbl...
> TheBurgerMan wrote:
>> Hi all. We have several consultants on site that need access to our SQL
>> server databases. They have accounts in our domain and I would like to
>> use those accounts in SQL 2005 (actually, as part of a Development
>> group).
>> Since their machines are not part of our Domain, they cannot use Windows
>> Authentication to connect. How can I use SQL Server Authentication and
>> their Domain accounts to allow them to connect to the server?
>> I have tried using the accounts as Domain\Username in the Login box, but
>> I always get 'Microsoft SQL Server, Error: 18456' (I can use other
>> non-Domain accounts to login successfully, so I know the conenctivity is
>> OK).
>> Any help would be appreciated.
> When you've tried setting these accounts up as Domain\Username, are you
> using your domain name, or theirs? Is your server a member of your
> domain?|||You can't do a SQL Server login using a domain account. SQL Server will look for a SQL Server login
with the name of Domain\User, and pass the password you enter. The app need to ask for a Windows
login, and the credentials will be taken from the account system that validated that Windows account
(the local machine, for example).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"TheBurgerMan" <TheBurgerMan@.gmail.com> wrote in message
news:umAcwjUmGHA.1896@.TK2MSFTNGP05.phx.gbl...
> The Consultant machines are not members of my Domain, but they are using Domain accounts that I
> have created. When I created the Consultant accounts, I added them to the Development Group which
> has profecient rights in SQL server to log in and manipulate databases (my account is a member of
> this group).
> I tried the same test on my laptop! I can login with SQL Server Auth into an account that I
> created on the server AND I can login with Windows Authentication (because my machine is a member
> of the Domain), but I cannot login with SQL Server Auth with my Domain account! This is what I
> want to do (then I do not have to start creating a pile of seperate accounts in SQL server as well
> as AD).
> --
> Thanks,
> TheBurgerMan
> at
> gmail.com
> --
> "Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
> news:OyS%23heUmGHA.5076@.TK2MSFTNGP02.phx.gbl...
>> TheBurgerMan wrote:
>> Hi all. We have several consultants on site that need access to our SQL server databases. They
>> have accounts in our domain and I would like to use those accounts in SQL 2005 (actually, as
>> part of a Development group).
>> Since their machines are not part of our Domain, they cannot use Windows Authentication to
>> connect. How can I use SQL Server Authentication and their Domain accounts to allow them to
>> connect to the server?
>> I have tried using the accounts as Domain\Username in the Login box, but I always get 'Microsoft
>> SQL Server, Error: 18456' (I can use other non-Domain accounts to login successfully, so I know
>> the conenctivity is OK).
>> Any help would be appreciated.
>>
>> When you've tried setting these accounts up as Domain\Username, are you using your domain name,
>> or theirs? Is your server a member of your domain?
>|||That seems counter-intuitive given that I can use Domain resources,
authenticating with a Domain username and password, but never be a member of
said Domain!
I only want to use this feature in the SQL Server Management GUI. Is there
a way to pass the Domain credentials using the Windows login (it greys out
the username and password once you select Windows Authentication)?
--
Thanks,
TheBurgerMan
at
gmail.com
--
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23o9fE$UmGHA.5076@.TK2MSFTNGP02.phx.gbl...
> You can't do a SQL Server login using a domain account. SQL Server will
> look for a SQL Server login with the name of Domain\User, and pass the
> password you enter. The app need to ask for a Windows login, and the
> credentials will be taken from the account system that validated that
> Windows account (the local machine, for example).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "TheBurgerMan" <TheBurgerMan@.gmail.com> wrote in message
> news:umAcwjUmGHA.1896@.TK2MSFTNGP05.phx.gbl...
>> The Consultant machines are not members of my Domain, but they are using
>> Domain accounts that I have created. When I created the Consultant
>> accounts, I added them to the Development Group which has profecient
>> rights in SQL server to log in and manipulate databases (my account is a
>> member of this group).
>> I tried the same test on my laptop! I can login with SQL Server Auth
>> into an account that I created on the server AND I can login with Windows
>> Authentication (because my machine is a member of the Domain), but I
>> cannot login with SQL Server Auth with my Domain account! This is what I
>> want to do (then I do not have to start creating a pile of seperate
>> accounts in SQL server as well as AD).
>> --
>> Thanks,
>> TheBurgerMan
>> at
>> gmail.com
>> --
>> "Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
>> news:OyS%23heUmGHA.5076@.TK2MSFTNGP02.phx.gbl...
>> TheBurgerMan wrote:
>> Hi all. We have several consultants on site that need access to our
>> SQL server databases. They have accounts in our domain and I would
>> like to use those accounts in SQL 2005 (actually, as part of a
>> Development group).
>> Since their machines are not part of our Domain, they cannot use
>> Windows Authentication to connect. How can I use SQL Server
>> Authentication and their Domain accounts to allow them to connect to
>> the server?
>> I have tried using the accounts as Domain\Username in the Login box,
>> but I always get 'Microsoft SQL Server, Error: 18456' (I can use other
>> non-Domain accounts to login successfully, so I know the conenctivity
>> is OK).
>> Any help would be appreciated.
>>
>> When you've tried setting these accounts up as Domain\Username, are you
>> using your domain name, or theirs? Is your server a member of your
>> domain?
>>
>|||Try creating a short-cut using the comman runas runas
/user:ComputerName\administrator ?
Change the question mark to the command to be ran as the user after /user:
Tim S
"TheBurgerMan" <TheBurgerMan@.gmail.com> wrote in message
news:%23frHgMVmGHA.3504@.TK2MSFTNGP04.phx.gbl...
> That seems counter-intuitive given that I can use Domain resources,
> authenticating with a Domain username and password, but never be a member
> of said Domain!
> I only want to use this feature in the SQL Server Management GUI. Is
> there a way to pass the Domain credentials using the Windows login (it
> greys out the username and password once you select Windows
> Authentication)?
> --
> Thanks,
> TheBurgerMan
> at
> gmail.com
> --
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:%23o9fE$UmGHA.5076@.TK2MSFTNGP02.phx.gbl...
>> You can't do a SQL Server login using a domain account. SQL Server will
>> look for a SQL Server login with the name of Domain\User, and pass the
>> password you enter. The app need to ask for a Windows login, and the
>> credentials will be taken from the account system that validated that
>> Windows account (the local machine, for example).
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "TheBurgerMan" <TheBurgerMan@.gmail.com> wrote in message
>> news:umAcwjUmGHA.1896@.TK2MSFTNGP05.phx.gbl...
>> The Consultant machines are not members of my Domain, but they are using
>> Domain accounts that I have created. When I created the Consultant
>> accounts, I added them to the Development Group which has profecient
>> rights in SQL server to log in and manipulate databases (my account is a
>> member of this group).
>> I tried the same test on my laptop! I can login with SQL Server Auth
>> into an account that I created on the server AND I can login with
>> Windows Authentication (because my machine is a member of the Domain),
>> but I cannot login with SQL Server Auth with my Domain account! This is
>> what I want to do (then I do not have to start creating a pile of
>> seperate accounts in SQL server as well as AD).
>> --
>> Thanks,
>> TheBurgerMan
>> at
>> gmail.com
>> --
>> "Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
>> news:OyS%23heUmGHA.5076@.TK2MSFTNGP02.phx.gbl...
>> TheBurgerMan wrote:
>> Hi all. We have several consultants on site that need access to our
>> SQL server databases. They have accounts in our domain and I would
>> like to use those accounts in SQL 2005 (actually, as part of a
>> Development group).
>> Since their machines are not part of our Domain, they cannot use
>> Windows Authentication to connect. How can I use SQL Server
>> Authentication and their Domain accounts to allow them to connect to
>> the server?
>> I have tried using the accounts as Domain\Username in the Login box,
>> but I always get 'Microsoft SQL Server, Error: 18456' (I can use other
>> non-Domain accounts to login successfully, so I know the conenctivity
>> is OK).
>> Any help would be appreciated.
>>
>> When you've tried setting these accounts up as Domain\Username, are you
>> using your domain name, or theirs? Is your server a member of your
>> domain?
>>
>sql

How to limit concurrent users when using pooled connections?

Hi,
I've been out of the loop for a while but when I learnt about db access from
VB etc we were told to use the same connection credentials such as username
and password in order to speed up access by recycling connections. Nowadays
I want to host a web site with some sort of database at the back end and I
would like to use MSDE but there is a 25 concurrent users restraint on the
license.
How would I limit the users if I'm using connection pooling? Is this
something I'd have to do in code?
Thanks in advance.
hi,
meadensi wrote:
> Hi,
> I've been out of the loop for a while but when I learnt about db
> access from VB etc we were told to use the same connection
> credentials such as username and password in order to speed up access
> by recycling connections. Nowadays I want to host a web site with
> some sort of database at the back end and I would like to use MSDE
> but there is a 25 concurrent users restraint on the license.
there is no restrincions on licences at all..this 25 magic number is just a
general "guess" about the "potential" limit of MSDE, as it allows up to
32765 theoretical concurrent connections (as all SQL Server editions) but it
has a built in Query Governor ( more at
http://msdn.microsoft.com/library/?u...asp?frame=true )
that kicks in when 8 concurrent workloads (AKA batches and not connections)
are executing, slowing down all active workloads...

> How would I limit the users if I'm using connection pooling? Is this
> something I'd have to do in code?
as you are writing a web base application, probably built on IIS, you can
for sure use the connection pooling features, as the application server
probably uses the very same connection string each time (and this is enougth
for reusing pooled connections), but disabling the pooled connections
(providing the "OLE DB Services = -2" parameter in the connection string,
which disables connection pooling only...) could not increase your
performance/access strategy, as the wall still is at 8 concurrent workloads,
with no regard to the actual connection owner... and querying your
master..sysprocesses table for the actual current count only adds additional
workloads to your (scarce) resources...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea. Very good and helpful answer which has reminded me of why the
MVP programme is a good idea (I once pondered trying to earn MVP status
myself, in Excel!)
Cheers,
meadensi
"Andrea Montanari" wrote:

> hi,
> meadensi wrote:
> there is no restrincions on licences at all..this 25 magic number is just a
> general "guess" about the "potential" limit of MSDE, as it allows up to
> 32765 theoretical concurrent connections (as all SQL Server editions) but it
> has a built in Query Governor ( more at
> http://msdn.microsoft.com/library/?u...asp?frame=true )
> that kicks in when 8 concurrent workloads (AKA batches and not connections)
> are executing, slowing down all active workloads...
>
> as you are writing a web base application, probably built on IIS, you can
> for sure use the connection pooling features, as the application server
> probably uses the very same connection string each time (and this is enougth
> for reusing pooled connections), but disabling the pooled connections
> (providing the "OLE DB Services = -2" parameter in the connection string,
> which disables connection pooling only...) could not increase your
> performance/access strategy, as the wall still is at 8 concurrent workloads,
> with no regard to the actual connection owner... and querying your
> master..sysprocesses table for the actual current count only adds additional
> workloads to your (scarce) resources...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>