We plan to migrate Sybase 11.5 (Windows NT) to 12.5 on W2K (on a
seperate server). Can i copy the User-Databases with dump/load?
must be migrated master-DB also with load or can i use a new one?
has someone documents for this task?
I would be grateful for any insight!

Dans news:12feb6ac.0406090454.2732f60 (AT) posting (DOT) google.com,
lutz <luhein (AT) gmx (DOT) net> a écrit:
Yes.

You can use a new one, but you have to recreate the logins
on the new server and be aware with the uid which
needed to be synchronized with the old uid on the
old server.



--
Emmanuel GEORGES

This is the sequence that I followed in migrating from 11.9.2 to sybase
12.0.3.
I assume a similar process will work for you

1. Created a new server using release 12.0.3

2. Defined all databases with "for load" option
(Note: use sysusages to determine the exact sequence and sizes of each data
and log segments.
You may need to create the database for load, then alter the database for
load to make this happen.
Device names do not need to be the same)

3. created a view in the old server for the 11.9.2 syslogins table that
provided null values for the additional columns in the 12.0.3 syslogins
table. Omit users sa and probe.

4. dumped all databases from the 11.9.2 server

5. used bcp specifing the view and '-c' option to extract all login
information.

6. used bcp to load the syslogins table using the output from the
bcp-view, again using the '-c' option

7. loaded all databases into the 12.0.3 server

8. Online each database.

9. used sp_changedbowner (with true option) to adjust the database owner.

The databases that are copied over, maintian the original values for suid
in the sysuser and sysalternate
tables. If I had just used sp_addlogin to readd all the users, chances
would have given some users different
suid values as well as requiring new passwords. Using the bcp method all
suid values in the new server's syslogins table
matched the suid values from the old server. The linkage between each
database's tables (sysuser, sysalternates) and the
master..syslogins table was preserved. The encrypted password from the old
server was stored into the password column,
this allowed the user to connect using his previous password without any
changes.

"lutz" <luhein (AT) gmx (DOT) net> wrote