Change Default database Confirm password required

I have recently added SP3a to my SQL 2000 system and every time I detach a
database and then reattach I lose all my default database settings for my SQL
login/users. when I go to change the default database and select OK it
requires me to confirm the password.
How to I get around this so I do not have to always retype the password.
Jacci
Why not to use BACKUP/RESTORE ?
"Jacci" <Jacci@.discussions.microsoft.com> wrote in message
news:84BD75D1-B541-4F33-BA63-FFACE2006D63@.microsoft.com...
> I have recently added SP3a to my SQL 2000 system and every time I detach a
> database and then reattach I lose all my default database settings for my
SQL
> login/users. when I go to change the default database and select OK it
> requires me to confirm the password.
> How to I get around this so I do not have to always retype the password.
|||There are three version of the MS03-031 "Slammer Worm" virus hot fix. The
first messed up the DTSGUI.dll, the second, to fix this, messed up the login
password issue you are discribing. The latest is 8.00.819, you are probably
running build 818. Severice Pack 3a is build 760.
However, as far as the default databases goes, you can not fix this issue
since logins are assigned default databases by DBID. Once that database is
attached, there is no corresponding DBID to default to. Moreover, those ids,
although incremental, are reused. So, if you were to bring another database
online before you reattached the original, the logins may be assigned to the
new database instead.
Here is the KB for the password issue:
http://support.microsoft.com/default...b;en-us;826161
http://support.microsoft.com/default...b;en-us;821277
Sincerely,
Anthony Thomas
"Jacci" wrote:

> I have recently added SP3a to my SQL 2000 system and every time I detach a
> database and then reattach I lose all my default database settings for my SQL
> login/users. when I go to change the default database and select OK it
> requires me to confirm the password.
> How to I get around this so I do not have to always retype the password.
|||Thank You - this worked ;-)
"AnthonyThomas" wrote:
[vbcol=seagreen]
> There are three version of the MS03-031 "Slammer Worm" virus hot fix. The
> first messed up the DTSGUI.dll, the second, to fix this, messed up the login
> password issue you are discribing. The latest is 8.00.819, you are probably
> running build 818. Severice Pack 3a is build 760.
> However, as far as the default databases goes, you can not fix this issue
> since logins are assigned default databases by DBID. Once that database is
> attached, there is no corresponding DBID to default to. Moreover, those ids,
> although incremental, are reused. So, if you were to bring another database
> online before you reattached the original, the logins may be assigned to the
> new database instead.
> Here is the KB for the password issue:
> http://support.microsoft.com/default...b;en-us;826161
> http://support.microsoft.com/default...b;en-us;821277
> Sincerely,
>
> Anthony Thomas
>
> "Jacci" wrote:
sql

Change Default database Confirm password required

I have recently added SP3a to my SQL 2000 system and every time I detach a
database and then reattach I lose all my default database settings for my SQ
L
login/users. when I go to change the default database and select OK it
requires me to confirm the password.
How to I get around this so I do not have to always retype the password.Jacci
Why not to use BACKUP/RESTORE ?
"Jacci" <Jacci@.discussions.microsoft.com> wrote in message
news:84BD75D1-B541-4F33-BA63-FFACE2006D63@.microsoft.com...
> I have recently added SP3a to my SQL 2000 system and every time I detach a
> database and then reattach I lose all my default database settings for my
SQL
> login/users. when I go to change the default database and select OK it
> requires me to confirm the password.
> How to I get around this so I do not have to always retype the password.|||There are three version of the MS03-031 "Slammer Worm" virus hot fix. The
first messed up the DTSGUI.dll, the second, to fix this, messed up the login
password issue you are discribing. The latest is 8.00.819, you are probably
running build 818. Severice Pack 3a is build 760.
However, as far as the default databases goes, you can not fix this issue
since logins are assigned default databases by DBID. Once that database is
attached, there is no corresponding DBID to default to. Moreover, those ids
,
although incremental, are reused. So, if you were to bring another database
online before you reattached the original, the logins may be assigned to the
new database instead.
Here is the KB for the password issue:
http://support.microsoft.com/defaul...kb;en-us;826161
http://support.microsoft.com/defaul...kb;en-us;821277
Sincerely,
Anthony Thomas
"Jacci" wrote:

> I have recently added SP3a to my SQL 2000 system and every time I detach a
> database and then reattach I lose all my default database settings for my
SQL
> login/users. when I go to change the default database and select OK it
> requires me to confirm the password.
> How to I get around this so I do not have to always retype the password.|||Thank You - this worked ;-)
"AnthonyThomas" wrote:
[vbcol=seagreen]
> There are three version of the MS03-031 "Slammer Worm" virus hot fix. The
> first messed up the DTSGUI.dll, the second, to fix this, messed up the log
in
> password issue you are discribing. The latest is 8.00.819, you are probab
ly
> running build 818. Severice Pack 3a is build 760.
> However, as far as the default databases goes, you can not fix this issue
> since logins are assigned default databases by DBID. Once that database i
s
> attached, there is no corresponding DBID to default to. Moreover, those i
ds,
> although incremental, are reused. So, if you were to bring another databa
se
> online before you reattached the original, the logins may be assigned to t
he
> new database instead.
> Here is the KB for the password issue:
> http://support.microsoft.com/defaul...kb;en-us;826161
> http://support.microsoft.com/defaul...kb;en-us;821277
> Sincerely,
>
> Anthony Thomas
>
> "Jacci" wrote:
>

Change dbowner on database

We recently renamed the local administrator account on our server from
administrator to boaadmin. And now we need to change dbo owner for a
database becauase the dbase is still using the name administrator for
the dbo.
I ran the process :
sp_changedbowner boaadmin
but it gives the following error. Am I doing something wrong, since I'm
a bit new to SQL...
Server: Msg 15007, Level 16, State 1, Procedure sp_changedbowner, Line
33 The login 'boaaladmin' does not exist.
When I ran the process in Query Analyzer I'm using the id boaadmin to
login...
I finally managed to execute the command without errors I had to add
the machine domain in front of the it servername\boaadmin.
After executing the command it returned "aliases were mapped to the new
database owner. database owner changed".
But when I look inside the dbase user's the dbo doesn't have a login
name associated with it. Previously it was servername\administrator and
now its just blank.
I've ran the sp_changedbowner twice and it still doesn't allocate the
id servername\boaadmin to dbo.
I even tried recreating the database using boaadmin, but find that the
dbowner is still the servername\administrator account.
Can'tr figure out why....Hi
If you renamed the account then the SID has not changed, the probably means
that sysxlogins has not be changed. You may want to try calling sp_grantlogi
n
for boaadmin and sp_revokelogin for administrator.
What does sp_change_users_login 'report' give on the database?
I also noticed that the error message for sp_changedbowner refers to
'boaaladmin'
John
"Zeno" wrote:

> We recently renamed the local administrator account on our server from
> administrator to boaadmin. And now we need to change dbo owner for a
> database becauase the dbase is still using the name administrator for
> the dbo.
>
> I ran the process :
> sp_changedbowner boaadmin
>
> but it gives the following error. Am I doing something wrong, since I'm
> a bit new to SQL...
>
> Server: Msg 15007, Level 16, State 1, Procedure sp_changedbowner, Line
> 33 The login 'boaaladmin' does not exist.
>
> When I ran the process in Query Analyzer I'm using the id boaadmin to
> login...
> I finally managed to execute the command without errors I had to add
> the machine domain in front of the it servername\boaadmin.
>
> After executing the command it returned "aliases were mapped to the new
> database owner. database owner changed".
>
> But when I look inside the dbase user's the dbo doesn't have a login
> name associated with it. Previously it was servername\administrator and
> now its just blank.
>
> I've ran the sp_changedbowner twice and it still doesn't allocate the
> id servername\boaadmin to dbo.
>
> I even tried recreating the database using boaadmin, but find that the
> dbowner is still the servername\administrator account.
> Can'tr figure out why....
>|||Zeno,
Does 'machinename\boaaladmin' have a login in SQL Server? Create the login
and try again. I see no reason why it shouldn't work.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
"Zeno" wrote:

> We recently renamed the local administrator account on our server from
> administrator to boaadmin. And now we need to change dbo owner for a
> database becauase the dbase is still using the name administrator for
> the dbo.
>
> I ran the process :
> sp_changedbowner boaadmin
>
> but it gives the following error. Am I doing something wrong, since I'm
> a bit new to SQL...
>
> Server: Msg 15007, Level 16, State 1, Procedure sp_changedbowner, Line
> 33 The login 'boaaladmin' does not exist.
>
> When I ran the process in Query Analyzer I'm using the id boaadmin to
> login...
> I finally managed to execute the command without errors I had to add
> the machine domain in front of the it servername\boaadmin.
>
> After executing the command it returned "aliases were mapped to the new
> database owner. database owner changed".
>
> But when I look inside the dbase user's the dbo doesn't have a login
> name associated with it. Previously it was servername\administrator and
> now its just blank.
>
> I've ran the sp_changedbowner twice and it still doesn't allocate the
> id servername\boaadmin to dbo.
>
> I even tried recreating the database using boaadmin, but find that the
> dbowner is still the servername\administrator account.
> Can'tr figure out why....
>|||Zeno
Is there a speciffic reason why you don't want your database and objects
owned by SA. With any other owner you will find some utilities and commands
will not run as you expect. I have in the past inherited databases not owned
by sa and they can be a right pain.
You need to limit access to sa, but generally your life will be much easier.
Regards
John
"Mark Allison" wrote:
[vbcol=seagreen]
> Zeno,
> Does 'machinename\boaaladmin' have a login in SQL Server? Create the login
> and try again. I see no reason why it shouldn't work.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> "Zeno" wrote:
>

Change dbowner on database

We recently renamed the local administrator account on our server from
administrator to boaadmin. And now we need to change dbo owner for a
database becauase the dbase is still using the name administrator for
the dbo.
I ran the process :
sp_changedbowner boaadmin
but it gives the following error. Am I doing something wrong, since I'm
a bit new to SQL...
Server: Msg 15007, Level 16, State 1, Procedure sp_changedbowner, Line
33 The login 'boaaladmin' does not exist.
When I ran the process in Query Analyzer I'm using the id boaadmin to
login...
I finally managed to execute the command without errors I had to add
the machine domain in front of the it servername\boaadmin.
After executing the command it returned "aliases were mapped to the new
database owner. database owner changed".
But when I look inside the dbase user's the dbo doesn't have a login
name associated with it. Previously it was servername\administrator and
now its just blank.
I've ran the sp_changedbowner twice and it still doesn't allocate the
id servername\boaadmin to dbo.
I even tried recreating the database using boaadmin, but find that the
dbowner is still the servername\administrator account.
Can'tr figure out why....
Hi
If you renamed the account then the SID has not changed, the probably means
that sysxlogins has not be changed. You may want to try calling sp_grantlogin
for boaadmin and sp_revokelogin for administrator.
What does sp_change_users_login 'report' give on the database?
I also noticed that the error message for sp_changedbowner refers to
'boaaladmin'
John
"Zeno" wrote:

> We recently renamed the local administrator account on our server from
> administrator to boaadmin. And now we need to change dbo owner for a
> database becauase the dbase is still using the name administrator for
> the dbo.
>
> I ran the process :
> sp_changedbowner boaadmin
>
> but it gives the following error. Am I doing something wrong, since I'm
> a bit new to SQL...
>
> Server: Msg 15007, Level 16, State 1, Procedure sp_changedbowner, Line
> 33 The login 'boaaladmin' does not exist.
>
> When I ran the process in Query Analyzer I'm using the id boaadmin to
> login...
> I finally managed to execute the command without errors I had to add
> the machine domain in front of the it servername\boaadmin.
>
> After executing the command it returned "aliases were mapped to the new
> database owner. database owner changed".
>
> But when I look inside the dbase user's the dbo doesn't have a login
> name associated with it. Previously it was servername\administrator and
> now its just blank.
>
> I've ran the sp_changedbowner twice and it still doesn't allocate the
> id servername\boaadmin to dbo.
>
> I even tried recreating the database using boaadmin, but find that the
> dbowner is still the servername\administrator account.
> Can'tr figure out why....
>
|||Zeno,
Does 'machinename\boaaladmin' have a login in SQL Server? Create the login
and try again. I see no reason why it shouldn't work.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
"Zeno" wrote:

> We recently renamed the local administrator account on our server from
> administrator to boaadmin. And now we need to change dbo owner for a
> database becauase the dbase is still using the name administrator for
> the dbo.
>
> I ran the process :
> sp_changedbowner boaadmin
>
> but it gives the following error. Am I doing something wrong, since I'm
> a bit new to SQL...
>
> Server: Msg 15007, Level 16, State 1, Procedure sp_changedbowner, Line
> 33 The login 'boaaladmin' does not exist.
>
> When I ran the process in Query Analyzer I'm using the id boaadmin to
> login...
> I finally managed to execute the command without errors I had to add
> the machine domain in front of the it servername\boaadmin.
>
> After executing the command it returned "aliases were mapped to the new
> database owner. database owner changed".
>
> But when I look inside the dbase user's the dbo doesn't have a login
> name associated with it. Previously it was servername\administrator and
> now its just blank.
>
> I've ran the sp_changedbowner twice and it still doesn't allocate the
> id servername\boaadmin to dbo.
>
> I even tried recreating the database using boaadmin, but find that the
> dbowner is still the servername\administrator account.
> Can'tr figure out why....
>
|||Zeno
Is there a speciffic reason why you don't want your database and objects
owned by SA. With any other owner you will find some utilities and commands
will not run as you expect. I have in the past inherited databases not owned
by sa and they can be a right pain.
You need to limit access to sa, but generally your life will be much easier.
Regards
John
"Mark Allison" wrote:
[vbcol=seagreen]
> Zeno,
> Does 'machinename\boaaladmin' have a login in SQL Server? Create the login
> and try again. I see no reason why it shouldn't work.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> "Zeno" wrote:

Change DB Owner

Hello,
We have a person leaving us who is the owner of a
database. How can we switch the owner to someone else ?
M
Mia,
Check the sp_changedbowner system sp in Books OnLine.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"Mia" <anonymous@.discussions.microsoft.com> wrote in message
news:2e8001c50a14$8b392950$a501280a@.phx.gbl...
> Hello,
> We have a person leaving us who is the owner of a
> database. How can we switch the owner to someone else ?
> M
|||See sp_changedbowner in SQL Server Books Online.
Anith

Change DB Owner

Hello,
We have a person leaving us who is the owner of a
database. How can we switch the owner to someone else ?
MMia,
Check the sp_changedbowner system sp in Books OnLine.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"Mia" <anonymous@.discussions.microsoft.com> wrote in message
news:2e8001c50a14$8b392950$a501280a@.phx.gbl...
> Hello,
> We have a person leaving us who is the owner of a
> database. How can we switch the owner to someone else ?
> M|||See sp_changedbowner in SQL Server Books Online.
Anith

case-sensitive searching in case-insensitive database

I recall reading about a way to check for a case-sensitive value in a
database that has a case-insensitive collation. Could anyone shed light on
this?
Thanks in advance.
You could convert to binary, or use the COLLATE statement:
CREATE TABLE [dbo].[testCollation] (
[Col1Name] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL
) ON [PRIMARY]
GO
insert into testCollation (Col1Name)
values('FredBloggs')
go
select * from testCollation
where Col1Name = 'fredBloggs' collate latin1_general_ci_as
select * from testCollation
where Col1Name = 'fredBloggs' collate latin1_general_cs_as
HTH,
Paul Ibison
|||"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:O19w0TVVEHA.1152@.TK2MSFTNGP09.phx.gbl...
> You could convert to binary, or use the COLLATE statement:
> CREATE TABLE [dbo].[testCollation] (
> [Col1Name] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL
> ) ON [PRIMARY]
> GO
> insert into testCollation (Col1Name)
> values('FredBloggs')
> go
> select * from testCollation
> where Col1Name = 'fredBloggs' collate latin1_general_ci_as
> select * from testCollation
> where Col1Name = 'fredBloggs' collate latin1_general_cs_as
> HTH,
> Paul Ibison
>
If the table is large and the column indexed you may want to add a search
predicate for case-insensitive collation so you can use the index, and then
narrow it down further with the case-sensitive collation predicate.
select * from testCollation
where col1Name = 'fredBloggs'
and Col1Name = 'fredBloggs' collate latin1_general_cs_as
David

case-sensitive searching in case-insensitive database

I recall reading about a way to check for a case-sensitive value in a
database that has a case-insensitive collation. Could anyone shed light on
this?
Thanks in advance.You could convert to binary, or use the COLLATE statement:
CREATE TABLE [dbo].[testCollation] (
[Col1Name] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL
) ON [PRIMARY]
GO
insert into testCollation (Col1Name)
values('FredBloggs')
go
select * from testCollation
where Col1Name = 'fredBloggs' collate latin1_general_ci_as
select * from testCollation
where Col1Name = 'fredBloggs' collate latin1_general_cs_as
HTH,
Paul Ibison|||"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:O19w0TVVEHA.1152@.TK2MSFTNGP09.phx.gbl...
> You could convert to binary, or use the COLLATE statement:
> CREATE TABLE [dbo].[testCollation] (
> [Col1Name] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NUL
L
> ) ON [PRIMARY]
> GO
> insert into testCollation (Col1Name)
> values('FredBloggs')
> go
> select * from testCollation
> where Col1Name = 'fredBloggs' collate latin1_general_ci_as
> select * from testCollation
> where Col1Name = 'fredBloggs' collate latin1_general_cs_as
> HTH,
> Paul Ibison
>
If the table is large and the column indexed you may want to add a search
predicate for case-insensitive collation so you can use the index, and then
narrow it down further with the case-sensitive collation predicate.
select * from testCollation
where col1Name = 'fredBloggs'
and Col1Name = 'fredBloggs' collate latin1_general_cs_as
David