Generally speaking: yes, this can be done
Caveats:
- ASE 16 and the ASE 15.7 dump must have the same pagesize, and ideally the same character set and sort order.
- if doing a cross platform dump-n-load (eg, little/endian => big/endian; big/endian => little endian) you'll need to run sp_post_xpload once the loaded database has been brought online
================== ASE 16
-- page size
select @@maxpagesize
go
-- character set and sort order
sp_helpsort
go
==================
================== ASE 15.7 dump file (eg, name: ase157.dbdump.file)
-- obtain source database details (pagesize, character set, sort order);
-- does not load the database
load database mydb from "/dump/dir/path/ase157.dbdump.file"
with headeronly
go
-- in case you need to create your ASE 16 data and log segments in the
-- same size and order as on ASE 15.7; does not load the database;
-- cut-n-paste the output to a script file, edit to use ASE 16 server's
-- device name(s) and your target database's name (eg, 'mydb')
load database mydb from "/dump/dir/path/ase157.dbdump.file"
with listonly=create_sql
go
==================