I have the need to change passwords in over 80+ databases when the user
changes it in one. Any suggestions on an effieient method. I would prefer
some type of "batch" method where it's not done online. Just wondering how
others
might take care of this!!

Thanks!

--

Jim Douglas

If these 80 databases are all on the same server, you don't have to do
anything as the login/password is server wide, if you're talking about
different servers, you can always use bcp to move logins from one server to
another.

"Jim Douglas" <james.douglas (AT) genesis-software (DOT) com> wrote

Good idea, but works ONLY if all users have the same suid on all systems.

Otherwise, you may need a combination of a shell script and SQL file to do
the following steps (assuming that you have the same SSO userid and password
on all of the servers):
1) Obtain SSO userid and password and the user id and revised password from
terminal input
2) IN A SECURE DIRECTORY (700 permission), create the SQL file to change the
passwords of the specified accounts
3) run ISQL on each server (maybe file input) to perform the password
changes
4) delete all working script files.

If the intent of all the userids is to permit users to access data from
multiple servers, have you thought about using proxies?

If things get really weird, it might be a time to suggest to the applicaiton
owners that it might be a good time to redesign the application and to
rethink the implementation.

Best of luck!

----- Original Message -----
From: "Germano" <gsilva3891 (AT) yahoo (DOT) com>
Newsgroups: comp.databases.sybase
Sent: Wednesday, August 25, 2004 7:27 AM
Subject: Re: User Login/Passwords

1. Create a view having (select name, password from syslogins where
"logins only" )
2 then bcp out this view,
3 then create a table xxx having (name,password).
4. create a trigger in the table xxx that compares it to syslogins,
then update syslogins (with allow updates) for any changed in the
password.

5 bcp-in this view to a table xxx


"Byrocat" <strikemaster2000 (AT) yahoo (DOT) ca> wrote

Jim Douglas wrote:
On the off chance you have Repserver ... you could use Repserver to
replicate the passwords for you.

Rob's (www.sypron.nl) got a copy of an old Techwave presentation I gave on
replicating logins/passwords/groups/users/blah-blah-blah. The link to the
copy of the presentation is
http://members.chello.nl/r.verschoor4/markaparsons.zip.

At first glance this may be overkill for what you want to do ... but RS's
store-n-forward capability comes in handy when you find that some of those
target servers aren't up and running ... so ya gotta go back at a later
date to apply those password changes. 'course, over time it could get a
little ugly if you have to remember which servers were up/down and when, so
that you can keep everything in sync ... *yuck*.

--
Mark A. Parsons

Iron Horse, Inc.
iron_horse (AT) NOSPAM (DOT) compuserve.com