"Pat Kelecy" <pat@mp-m.com> wrote in message
news:eHdkZCOPDHA.3836@tk2msftngp13.phx.gbl...
> I was running an installation (wizard) for an application that, as part of
> the installation process, creates a database in SQL. To to this it
required
> that I provide a username and password. Since SQL2K is configured for
> "mixed mode" authentication, I thought I could provide any valid AD
> adminstrator account and have it work. But it would only accept the
> administrator username and passwork that we orignially set up for it
(SQL) -
> (I had to really dig around to find that!). I'm confused as to why a
valid
> AD administrator account didn't work. Could someone shed some light on
> this? I am very new to SQL2000 an am trying to understand how it works
> (mainly from an application connectivity point of view - getting things to
> work with it). I have a number of applications that use it.
>
> Thanks for any help. I greatly appreciate it. -Pat
>
>

"BJ Freeman" <bfree@free-man.com> wrote in message
news:eengbMQPDHA.2224@TK2MSFTNGP10.phx.gbl...
> the standardard way is to use the SQL db sa account. this is because the
> other accounts may not have SA rights.
>
>
>
> "Pat Kelecy" <pat@mp-m.com> wrote in message
> news:eHdkZCOPDHA.3836@tk2msftngp13.phx.gbl...
> > I was running an installation (wizard) for an application that, as part
of
> > the installation process, creates a database in SQL. To to this it
> required
> > that I provide a username and password. Since SQL2K is configured for
> > "mixed mode" authentication, I thought I could provide any valid AD
> > adminstrator account and have it work. But it would only accept the
> > administrator username and passwork that we orignially set up for it
> (SQL) -
> > (I had to really dig around to find that!). I'm confused as to why a
> valid
> > AD administrator account didn't work. Could someone shed some light on
> > this? I am very new to SQL2000 an am trying to understand how it works
> > (mainly from an application connectivity point of view - getting things
to
> > work with it). I have a number of applications that use it.
> >
> > Thanks for any help. I greatly appreciate it. -Pat
> >
> >
>
>

"Pat Kelecy" <pat@mp-m.com> wrote in message
news:uK1SwwRPDHA.304@tk2msftngp13.phx.gbl...
> ok. - So it depends on whether SA (Sql Administrator?) rights have been
> assigned a user's account or not. So I take it the"sa" account is a
built
> in administrator account in SQL that always provides this (like the
> Administrator account in Win2K). Right?
>
> Thanks for the clarification. I appreciate it. -Pat
>
>
> "BJ Freeman" <bfree@free-man.com> wrote in message
> news:eengbMQPDHA.2224@TK2MSFTNGP10.phx.gbl...
> > the standardard way is to use the SQL db sa account. this is because the
> > other accounts may not have SA rights.
> >
> >
> >
> > "Pat Kelecy" <pat@mp-m.com> wrote in message
> > news:eHdkZCOPDHA.3836@tk2msftngp13.phx.gbl...
> > > I was running an installation (wizard) for an application that, as
part
> of
> > > the installation process, creates a database in SQL. To to this it
> > required
> > > that I provide a username and password. Since SQL2K is configured for
> > > "mixed mode" authentication, I thought I could provide any valid AD
> > > adminstrator account and have it work. But it would only accept the
> > > administrator username and passwork that we orignially set up for it
> > (SQL) -
> > > (I had to really dig around to find that!). I'm confused as to why a
> > valid
> > > AD administrator account didn't work. Could someone shed some light
on
> > > this? I am very new to SQL2000 an am trying to understand how it
works
> > > (mainly from an application connectivity point of view - getting
things
> to
> > > work with it). I have a number of applications that use it.
> > >
> > > Thanks for any help. I greatly appreciate it. -Pat
> > >
> > >
> >
> >
>
>

> I was running an installation (wizard) for an application that, as part
> of the installation process, creates a database in SQL. To to this it
> required that I provide a username and password. Since SQL2K is
> configured for "mixed mode" authentication, I thought I could provide
> any valid AD adminstrator account and have it work. But it would only
> accept the administrator username and passwork that we orignially set up
> for it (SQL) - (I had to really dig around to find that!). I'm confused
> as to why a valid AD administrator account didn't work. Could someone
> shed some light on this? I am very new to SQL2000 an am trying to
> understand how it works (mainly from an application connectivity point
> of view - getting things to work with it). I have a number of
> applications that use it.