SEO

#1 (**permalink**) 04-29-2008, 08:28 PM

Is there any way of migrating master.syslogins from a Sybase Unix
(Solaris 9) to windows (Server 2003) environment ?
I have used bcp to move syslogins between sybase on Unix server - no
problem. The bcp in appears to work fine onto the windows server, but
the user login fails.
Various readings tell me that this may fails due to the fact the the
passwords are encrypted and do not migrate between different OS
platforms. Just wondering is anyone has found a way around this.
Since we are migrating a production server with many users, would
rather passwords were preserved.
Thanks in advance.
Peter

#2 (**permalink**) 05-02-2008, 05:05 AM

Hello,

I think your understanding is correct. From this old technote:
http://www.sybase.com/detail?id=20269

WARNING!
Sybase recommends you restrict access of this file only to system
administrators because it contains passwords.

Using a script

1. Create a script, loginscript.txt, of user logins and passwords.
For
example:

sp_addlogin "loginame1", "password1"
go
sp_addlogin "loginame2", "password2"
go

2. Log into the new server and run the login script. For example:

isql -Usa -P -i loginscript.txt

Note: This script resets passwords to the original password. Remember
to
alert users that their passwords were reset.

#3 (**permalink**) 05-10-2008, 02:04 PM

SybaseNeal wrote:
> Hello,
>
> I think your understanding is correct. From this old technote:
> http://www.sybase.com/detail?id=20269
>
> WARNING!
> Sybase recommends you restrict access of this file only to system
> administrators because it contains passwords.
>
> Using a script
>
> 1. Create a script, loginscript.txt, of user logins and passwords.
> For
> example:
>
> sp_addlogin "loginame1", "password1"
> go
> sp_addlogin "loginame2", "password2"
> go
>
> 2. Log into the new server and run the login script. For example:
>
> isql -Usa -P -i loginscript.txt
>
> Note: This script resets passwords to the original password. Remember
> to
> alert users that their passwords were reset.

can you prepare the reverse engineered sql statements from the syslogins
table? then it will be really easy for you.

sp_configure "allow updates", 1
go

insert into syslogins ....
insert into syslogins ....

<remember, you need to prefix '0x' in the password field for the insert
statements, so that the passwords inserted are not again encrypted.

If not, no bcp nothing, if you can connect to the remote server using
'connect server' and 'disconnect', then get the syslogins table from the
remote server into the sandbox on the local dataserver.

and then its all simple that you insert into the master..syslogins as
select * from sandbox..syslogins where name <> sa or name <> probe
go

I guess, for the above, you do not need to prefix '0x' in the password
field, which apparently had worked for me.
(although for me both the dataservers happened to be on Unix, no Windows)

Guess, you could give a try?

Regards,
Nikhil

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Migrating syslogins from Unix to Windows - how to preserve passwords