login and password administration

Using SS2000. I have two questions. How do adminsremember passwords for
logins. We have several web sites each with its own login and password. I
thought about creating a table somewhere and storing the login, password and
purpose of the login but that doesn't seem so secure.
Second question - I have a login/user who I want to remove. The user owns a
table in a database. I tried changing the owner of the table to 'sa' using
"EXEC sp_changeobjectowner 'tblSVM', 'sa'" but I received this error:
Server: Msg 15001, Level 16, State 1, Procedure sp_changeobjectowner, Line 38
Object 'tblSVM' does not exist or is not a valid object for this operation.
How do I get rid of the login/user?
Thanks,
Dan D.
Hi,
Answer to your seconds question.
Make the owner of the object to DBO and drop the user and then remove the
login. While changing the object you have to give TABLE_OWNER.TABLE_NAME..
EXEC sp_changeobjectowner 'current_table_owner.tblSVM', 'dbo'
After that drop the user
sp_dropuser <user_name>
Drop the login
sp_droplogin <login_name>
Thanks
Hari
MCDBA
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:652F288B-24C3-4D9F-A616-8EA1A6840F46@.microsoft.com...
> Using SS2000. I have two questions. How do adminsremember passwords for
> logins. We have several web sites each with its own login and password. I
> thought about creating a table somewhere and storing the login, password
and
> purpose of the login but that doesn't seem so secure.
> Second question - I have a login/user who I want to remove. The user owns
a
> table in a database. I tried changing the owner of the table to 'sa' using
> "EXEC sp_changeobjectowner 'tblSVM', 'sa'" but I received this error:
> Server: Msg 15001, Level 16, State 1, Procedure sp_changeobjectowner, Line
38
> Object 'tblSVM' does not exist or is not a valid object for this
operation.
> How do I get rid of the login/user?
> Thanks,
> --
> Dan D.
|||After adding the current owner of the object, now I get this error message:
Server: Msg 15410, Level 11, State 1, Procedure sp_changeobjectowner, Line 55
User or role 'sa' does not exist in this database.
If I try to add 'sa' as a user in the database I get this message:
Cannot user the reserved user or role name 'sa'.
I was able to change the owner to another user but why did I have a problem
with changing it to 'sa'?
Thanks,
"Hari Prasad" wrote:

> Hi,
> Answer to your seconds question.
> Make the owner of the object to DBO and drop the user and then remove the
> login. While changing the object you have to give TABLE_OWNER.TABLE_NAME..
> EXEC sp_changeobjectowner 'current_table_owner.tblSVM', 'dbo'
> After that drop the user
> sp_dropuser <user_name>
> Drop the login
> sp_droplogin <login_name>
> Thanks
> Hari
> MCDBA
>
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:652F288B-24C3-4D9F-A616-8EA1A6840F46@.microsoft.com...
> and
> a
> 38
> operation.
>
>
|||You need to use the database user name, not the login name.
Mark.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Dan D. wrote:[vbcol=seagreen]
> After adding the current owner of the object, now I get this error message:
> Server: Msg 15410, Level 11, State 1, Procedure sp_changeobjectowner, Line 55
> User or role 'sa' does not exist in this database.
> If I try to add 'sa' as a user in the database I get this message:
> Cannot user the reserved user or role name 'sa'.
> I was able to change the owner to another user but why did I have a problem
> with changing it to 'sa'?
> Thanks,
> "Hari Prasad" wrote:
>
|||Dan,
Q1. Why not put them in a SQL Server database? You can restrict access
to the data in here easily. What are your security concerns?
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Dan D. wrote:
> Using SS2000. I have two questions. How do adminsremember passwords for
> logins. We have several web sites each with its own login and password. I
> thought about creating a table somewhere and storing the login, password and
> purpose of the login but that doesn't seem so secure.
> Second question - I have a login/user who I want to remove. The user owns a
> table in a database. I tried changing the owner of the table to 'sa' using
> "EXEC sp_changeobjectowner 'tblSVM', 'sa'" but I received this error:
> Server: Msg 15001, Level 16, State 1, Procedure sp_changeobjectowner, Line 38
> Object 'tblSVM' does not exist or is not a valid object for this operation.
> How do I get rid of the login/user?
> Thanks,
|||Dan
In response to your first question. What we do in the team I work in, is
keep all our 'secure' passwords in a password protected Excel spreadsheet. Of
course you still need to know/remember the password for the excel sheet.
Regards
John
"Dan D." wrote:
[vbcol=seagreen]
> After adding the current owner of the object, now I get this error message:
> Server: Msg 15410, Level 11, State 1, Procedure sp_changeobjectowner, Line 55
> User or role 'sa' does not exist in this database.
> If I try to add 'sa' as a user in the database I get this message:
> Cannot user the reserved user or role name 'sa'.
> I was able to change the owner to another user but why did I have a problem
> with changing it to 'sa'?
> Thanks,
> "Hari Prasad" wrote:
|||Well, at least that's only one password instead of many. Thanks for the
suggestion.
"John Bandettini" wrote:
[vbcol=seagreen]
> Dan
> In response to your first question. What we do in the team I work in, is
> keep all our 'secure' passwords in a password protected Excel spreadsheet. Of
> course you still need to know/remember the password for the excel sheet.
> Regards
> John
> "Dan D." wrote:
|||Just the normal concerns that someone from outside could get access to them.
However, none of the logins I'm talking about would have any kind of system
permissions.
"Mark Allison" wrote:

> Dan,
> Q1. Why not put them in a SQL Server database? You can restrict access
> to the data in here easily. What are your security concerns?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Dan D. wrote:
>
|||I'm not sure I know what you mean. I tried to create a user called 'sauser'
in the database using the 'sa' login and I got an error. I'm sure I've seen
'sa' as a user in a database before. How did it get there if I can't add it
as a user?
Thanks,
"Mark Allison" wrote:

> You need to use the database user name, not the login name.
> Mark.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Dan D. wrote:
>