Windows is going to require a few more steps if ASE is running as a service.
Update all registry entries containing <servername> with <newservername>:
HKLM\SOFTWARE\SYBASE\Server
HKLM\SYSTEM\CurrentControlSet\Services\SYBSQL_<servername>[ _BS | _XP ]
NOTE: Doing a registry search on <servername> will bring up a ton of other locations, eg, legacy entries, ControlSet00X, etc ... not sure if all of these have to be changed, too ...
NOTE: Haven't installed any of the latest ASE packages in windows so don't know if SAP's gone an changed the HKLM\SOFTWARE sub-branch name from SYBASE to SAP
=========================
In addition to Ryan's notes:
- any other sysservers entries that refer to the old servername (eg, loopback)
- any remote servers would need to update their external/remote logins, remote servers and/or proxy definitions ... as appropriate
- if the ASE is involved in replication then you're looking at whole 'nother can of worms ... off the top of my head ... rs_databases, rs_idnames, rs_repdbs ... and of course any repdefs/subs that include the ASE name ?
- obviously (?) any monitoring/maintenance/operational jobs ... documentation ...