dbo's Login Name is blank and can't be edited from Enterprise Manager

We are using SQL Server 2000 SP4. I just created a new database from the EM
but found that in the Users folder under this new db name the Login Name for
dbo was blank. I double-clicked the dbo line and it showed <None> in the
properities dialog box which could not be edited. Is it okay to exe
sp_changedbowner 'sa' sepcially for this new database? Or any better idea?
Thanks,
Eli
> Is it okay to exe sp_changedbowner 'sa' sepcially for this new database?
Yes, sp_changedbowner will fix the database owner. I think it's odd that a
new database would have a NULL owner, though. I usually see that only when
the Windows account that was the database owner is deleted.
Hope this helps.
Dan Guzman
SQL Server MVP
"Eli" <efeng@.kerisys.com> wrote in message
news:%233Pa1LmIIHA.4196@.TK2MSFTNGP04.phx.gbl...
> We are using SQL Server 2000 SP4. I just created a new database from the
> EM
> but found that in the Users folder under this new db name the Login Name
> for
> dbo was blank. I double-clicked the dbo line and it showed <None> in the
> properities dialog box which could not be edited. Is it okay to exe
> sp_changedbowner 'sa' sepcially for this new database? Or any better idea?
> Thanks,
> Eli
>
|||Thanks Dan. It works. Appreciate your meesage.
Regards,
Eli
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:8849D3CB-78AA-42C8-8AA5-9E646991CDFC@.microsoft.com...
> Yes, sp_changedbowner will fix the database owner. I think it's odd that
a
> new database would have a NULL owner, though. I usually see that only
when[vbcol=seagreen]
> the Windows account that was the database owner is deleted.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Eli" <efeng@.kerisys.com> wrote in message
> news:%233Pa1LmIIHA.4196@.TK2MSFTNGP04.phx.gbl...
idea?
>
|||I'm glad I was able to help. Thanks for taking the time to confirm.
Dan Guzman
SQL Server MVP
"Eli" <efeng@.kerisys.com> wrote in message
news:uZ80fLvIIHA.1212@.TK2MSFTNGP05.phx.gbl...
> Thanks Dan. It works. Appreciate your meesage.
> Regards,
> Eli
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:8849D3CB-78AA-42C8-8AA5-9E646991CDFC@.microsoft.com...
> a
> when
> idea?
>

dbo's Login Name is blank and can't be edited from Enterprise Manager

We are using SQL Server 2000 SP4. I just created a new database from the EM
but found that in the Users folder under this new db name the Login Name for
dbo was blank. I double-clicked the dbo line and it showed <None> in the
properities dialog box which could not be edited. Is it okay to exe
sp_changedbowner 'sa' sepcially for this new database? Or any better idea?
Thanks,
Eli> Is it okay to exe sp_changedbowner 'sa' sepcially for this new database?
Yes, sp_changedbowner will fix the database owner. I think it's odd that a
new database would have a NULL owner, though. I usually see that only when
the Windows account that was the database owner is deleted.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Eli" <efeng@.kerisys.com> wrote in message
news:%233Pa1LmIIHA.4196@.TK2MSFTNGP04.phx.gbl...
> We are using SQL Server 2000 SP4. I just created a new database from the
> EM
> but found that in the Users folder under this new db name the Login Name
> for
> dbo was blank. I double-clicked the dbo line and it showed <None> in the
> properities dialog box which could not be edited. Is it okay to exe
> sp_changedbowner 'sa' sepcially for this new database? Or any better idea?
> Thanks,
> Eli
>|||Thanks Dan. It works. Appreciate your meesage.
Regards,
Eli
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:8849D3CB-78AA-42C8-8AA5-9E646991CDFC@.microsoft.com...
> > Is it okay to exe sp_changedbowner 'sa' sepcially for this new database?
> Yes, sp_changedbowner will fix the database owner. I think it's odd that
a
> new database would have a NULL owner, though. I usually see that only
when
> the Windows account that was the database owner is deleted.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Eli" <efeng@.kerisys.com> wrote in message
> news:%233Pa1LmIIHA.4196@.TK2MSFTNGP04.phx.gbl...
> > We are using SQL Server 2000 SP4. I just created a new database from the
> > EM
> > but found that in the Users folder under this new db name the Login Name
> > for
> > dbo was blank. I double-clicked the dbo line and it showed <None> in the
> > properities dialog box which could not be edited. Is it okay to exe
> > sp_changedbowner 'sa' sepcially for this new database? Or any better
idea?
> > Thanks,
> > Eli
> >
> >
>|||I'm glad I was able to help. Thanks for taking the time to confirm.
--
Dan Guzman
SQL Server MVP
"Eli" <efeng@.kerisys.com> wrote in message
news:uZ80fLvIIHA.1212@.TK2MSFTNGP05.phx.gbl...
> Thanks Dan. It works. Appreciate your meesage.
> Regards,
> Eli
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:8849D3CB-78AA-42C8-8AA5-9E646991CDFC@.microsoft.com...
>> > Is it okay to exe sp_changedbowner 'sa' sepcially for this new
>> > database?
>> Yes, sp_changedbowner will fix the database owner. I think it's odd that
> a
>> new database would have a NULL owner, though. I usually see that only
> when
>> the Windows account that was the database owner is deleted.
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Eli" <efeng@.kerisys.com> wrote in message
>> news:%233Pa1LmIIHA.4196@.TK2MSFTNGP04.phx.gbl...
>> > We are using SQL Server 2000 SP4. I just created a new database from
>> > the
>> > EM
>> > but found that in the Users folder under this new db name the Login
>> > Name
>> > for
>> > dbo was blank. I double-clicked the dbo line and it showed <None> in
>> > the
>> > properities dialog box which could not be edited. Is it okay to exe
>> > sp_changedbowner 'sa' sepcially for this new database? Or any better
> idea?
>> > Thanks,
>> > Eli
>> >
>> >
>

dbo's Login Name is blank and can't be edited from Enterprise Manager

We are using SQL Server 2000 SP4. I just created a new database from the EM
but found that in the Users folder under this new db name the Login Name for
dbo was blank. I double-clicked the dbo line and it showed <None> in the
properities dialog box which could not be edited. Is it okay to exe
sp_changedbowner 'sa' sepcially for this new database? Or any better idea?
Thanks,
Eli> Is it okay to exe sp_changedbowner 'sa' sepcially for this new database?
Yes, sp_changedbowner will fix the database owner. I think it's odd that a
new database would have a NULL owner, though. I usually see that only when
the Windows account that was the database owner is deleted.
Hope this helps.
Dan Guzman
SQL Server MVP
"Eli" <efeng@.kerisys.com> wrote in message
news:%233Pa1LmIIHA.4196@.TK2MSFTNGP04.phx.gbl...
> We are using SQL Server 2000 SP4. I just created a new database from the
> EM
> but found that in the Users folder under this new db name the Login Name
> for
> dbo was blank. I double-clicked the dbo line and it showed <None> in the
> properities dialog box which could not be edited. Is it okay to exe
> sp_changedbowner 'sa' sepcially for this new database? Or any better idea?
> Thanks,
> Eli
>|||Thanks Dan. It works. Appreciate your meesage.
Regards,
Eli
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:8849D3CB-78AA-42C8-8AA5-9E646991CDFC@.microsoft.com...
> Yes, sp_changedbowner will fix the database owner. I think it's odd that
a
> new database would have a NULL owner, though. I usually see that only
when
> the Windows account that was the database owner is deleted.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Eli" <efeng@.kerisys.com> wrote in message
> news:%233Pa1LmIIHA.4196@.TK2MSFTNGP04.phx.gbl...
idea?[vbcol=seagreen]
>|||I'm glad I was able to help. Thanks for taking the time to confirm.
Dan Guzman
SQL Server MVP
"Eli" <efeng@.kerisys.com> wrote in message
news:uZ80fLvIIHA.1212@.TK2MSFTNGP05.phx.gbl...
> Thanks Dan. It works. Appreciate your meesage.
> Regards,
> Eli
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:8849D3CB-78AA-42C8-8AA5-9E646991CDFC@.microsoft.com...
> a
> when
> idea?
>

dbo can't bring DB online

I have a user with db_owner status who can take a DB offline, but for some r
eason can't bring it back online. The DB is on a cluster server. Is there an
y way to explicitly script or set this ability for SQL Server 2000? Thanks.Hi Journika
Database role membership is only stored in the database itself. So once the
database is offline, there is no way to know who is in the db_owner role of
the offline database. Bringing the db back online will have to be done by
someone with privilege at the server level, or by the true owner of the
database, as listed in sysdatabses (and viewed through sp_helpdb)
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Journika" <anonymous@.discussions.microsoft.com> wrote in message
news:3CFB7F32-C517-4818-8AEC-7A9B135F3017@.microsoft.com...
> I have a user with db_owner status who can take a DB offline, but for some
reason can't bring it back online. The DB is on a cluster server. Is there
any way to explicitly script or set this ability for SQL Server 2000?
Thanks.

dbnmpipe.exe for MS-DOS

I recently purchased sql 2000.
I need connectivity for an old DOS program.
I see that I need the file DBNMPIPE.EXE
I can't find this file anywhere on my CD's or on
Microsofts website.
Where can I get it?
"Cash Woodward" <cash@.grandtarghee.com> wrote in message
news:1f67801c457c1$bfc79810$a501280a@.phx.gbl...
> I recently purchased sql 2000.
> I need connectivity for an old DOS program.
> I see that I need the file DBNMPIPE.EXE
> I can't find this file anywhere on my CD's or on
> Microsofts website.
> Where can I get it?
I believe you are in non-supported territory here (from the SQL Server web
site):
Client Support:
.. Windows 955, Windows 98, Windows Me, Windows NT Workstation 4.0, Windows
2000 Professional, Windows XP Professional, and Windows XP Home Edition are
supported.
Steve
|||Actually it states that older clients will still work with sql 2000.
"Steve Thompson" wrote:

> "Cash Woodward" <cash@.grandtarghee.com> wrote in message
> news:1f67801c457c1$bfc79810$a501280a@.phx.gbl...
> I believe you are in non-supported territory here (from the SQL Server web
> site):
> Client Support:
> .. Windows 955, Windows 98, Windows Me, Windows NT Workstation 4.0, Windows
> 2000 Professional, Windows XP Professional, and Windows XP Home Edition are
> supported.
> Steve
>
>
|||Sent by email
Neil Pike MVP/MCSE. Protech Computing Ltd
Reply here - no email
SQL FAQ (484 entries) see
http://forumsb.compuserve.com/gvforu...?SRV=MSDevApps
(faqxxx.zip in lib 7)
or http://www.ntfaq.com/Articles/Index...partmentID=800
or www.sqlserverfaq.com
or www.mssqlserver.com/faq
|||Older DOS based clients? Can you send a reference?
Thanks, Steve
"Cash Woodward" <Cash Woodward@.discussions.microsoft.com> wrote in message
news:7ECE2A36-195D-4120-9D4F-A94142E311A0@.microsoft.com...[vbcol=seagreen]
> Actually it states that older clients will still work with sql 2000.
> "Steve Thompson" wrote:
web[vbcol=seagreen]
Windows[vbcol=seagreen]
are[vbcol=seagreen]
|||See the reply #4 from Neil Pike.
This is from archive file SQL7DBLIBSUPPORT.TXT
This is what I have read from Microsofts website also.
Q. Does SQL 7/2000 support DB-Library? What about 16-bit clients - DOS
etc.?
A. Yes it does, but DB-Library is functionally stabilised at the 6.5
level. Therefore if a DB-Library client on whatever platform worked
against a 6.5 database it should work against the same database migrated
to SQL 7.0/2000.
None of the SQL 7.0 features like unicode, character columns greater
than 255 characters etc. are in DB-Library though. So if you utilise
any SQL 7.0 features then these can only be accessed by ODBC 3.7 or
OLE-DB clients.
Similarly for 16-bit clients. These are supported, but only with the
6.5 levels of ODBC/DB-Library code. 16-bit clients cannot access new
SQL 7.0 features either.
The 16-bit client code is not supplied with 7.0/2000 - you will have to
get it from the 6.5 CD-ROM. This includes DOS and Win 3.x drivers.
===
v1.03 2000.04.28
Applies to SQL Server versions : 7.0, 2000
FAQ Categories : Connectivity
Related FAQ articles : n/a
Related Microsoft Kb articles : n/a
Other related information : n/a
Authors : Neil Pike
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!
|||Thank you Cash -- very interesting!
"Cash Woodward" <cash@.grandtarghee.com> wrote in message
news:%23ggDDuSWEHA.1164@.tk2msftngp13.phx.gbl...
> See the reply #4 from Neil Pike.
> This is from archive file SQL7DBLIBSUPPORT.TXT
> This is what I have read from Microsofts website also.
> Q. Does SQL 7/2000 support DB-Library? What about 16-bit clients - DOS
> etc.?
> A. Yes it does, but DB-Library is functionally stabilised at the 6.5
> level. Therefore if a DB-Library client on whatever platform worked
> against a 6.5 database it should work against the same database migrated
> to SQL 7.0/2000.
> None of the SQL 7.0 features like unicode, character columns greater
> than 255 characters etc. are in DB-Library though. So if you utilise
> any SQL 7.0 features then these can only be accessed by ODBC 3.7 or
> OLE-DB clients.
> Similarly for 16-bit clients. These are supported, but only with the
> 6.5 levels of ODBC/DB-Library code. 16-bit clients cannot access new
> SQL 7.0 features either.
> The 16-bit client code is not supplied with 7.0/2000 - you will have to
> get it from the 6.5 CD-ROM. This includes DOS and Win 3.x drivers.
> ===
> v1.03 2000.04.28
> Applies to SQL Server versions : 7.0, 2000
> FAQ Categories : Connectivity
> Related FAQ articles : n/a
> Related Microsoft Kb articles : n/a
> Other related information : n/a
> Authors : Neil Pike
>
>
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!