Parameters

-c config_file_for_server – specifies the full path name of an SAP ASE configuration file. Use this
parameter to start an SAP ASE server with the configuration values in
the specified configuration file.If you specify a configuration file
with the sqlsrvr -c parameter, make
sure all the parameters in this configuration file are compatible before
you boot the server. If some of the configuration parameters are
incompatible, the server may not start. To avoid this, do not specify a
configuration file when you build the master device. The build phase
uses all default settings when you do not specify a configuration
file.For more information, see the System
Administration Guide: Volume 1.

-ddevice_name – is the full path name of the device for the master database. The master database device must be
writable by the user who starts the SAP ASE server. The default master database device name is d_master.

-eerrorlogfile – is the full path name of the error log file for SAP ASE system-level error
messages.

-f – forces initialization of a device or database. You must use both -b and
-w to use -f.

-G – specifies the name of the event log server.

-g – turns off event-logging.

-H – starts the high availability (HA) server, if you have the HA feature
installed on your SAP ASE server.

-iinterfaces_file_directory – specifies the directory location of the interfaces file to search
when connecting an SAP ASE server. If -i is omitted, sqlsrvr
looks for a file named interfaces
in the directory pointed to by your SYBASE environment variable.

-h – prints this help message, then exists.

-Kkeytab_file – specifies the path to the keytab file used for authentication in DCE.

-Lconfig_file_name_for_connectivity – specifies the name the configuration file for connectivity.

-M
sharedmem_directory – places shared memory files in the specified directory instead of in the default
location, %SYBASE%. If sharedmem_directory
starts with “\”, the directory name is assumed to be absolute. Otherwise, the
directory name is interpreted relative to %SYBASE%.

-m – starts an SAP ASE server in single-user mode.

--master_key_password
[=password] – specifies the master key password when you provide the password on the command line or prompts
for a master key password during SAP ASE startup. The password
characters do not appear, and the password is not validated until later
in the SAP ASE startup sequence.

If you include the password on the command line, it is visible until the memory is
read and used.

-psso_login_name – specifies the login name of a system security officer when
starting an SAP ASE server, for the purposes of getting a new password
for that account. The SAP ASE server generates a random password,
displays it, encrypts it, and saves it in master..syslogins as that account’s new password.

-q – treats quiesced databases as “in recovery.”

-rmastermirror – starts the mirror of the master device. Use this parameter to
start the SAP ASE server if the master device has been damaged.

-sservername – specifies the name of the SAP ASE server to start. If -s is omitted, a server named SYBASE is
started.

-Ttrace_flag –

-usa/sso_name – specifies the system administrator or system security officer’s name you want to
unlock.

-v – prints the version number and copyright message
for sqlsrvr and
then exits.

-y
[password] – allows you to assign a password for the encrypted
private key, so that the server prompt the user for a password.
This password should match the password you used to encrypt the
private key when it was created. You cannot use this parameter
when you are running the server in the background.

Note: Although you can a password with -y,
for security reasons Sybase strongly discourages you from doing
so.

A private key is included with your server’s digital
certificate. By default, the certificate file located:

%SYBASE%\%SYBASE_ASE%\certificates\servername.crt

The location of the certificate file changes if you invoke
the sp_ssladmin addcert command.

-z
page_size – specifies the page size of the server. Use -b and -w to
use this flag, and name an even power of two between 2k and 16k,
or else the server does not boot.

Examples

Create new installation – Creates a new installation with a 100MB master device
and a 4k page:

sqlsrvr -d d_master -z 4k -b 100.02M

The spaces between options and their following arguments are
optional and acceptable. This example specifies “100.02M” for a 100MB master device because the server
requires 16KB of overhead
for its configuration area.

Rewrite a corrupt master – Rewrites a corrupt model database:

sqlsrvr -d d_master -w model

To rewrite a corrupt master database
specifying device size:

sqlsrvr -d d_master -w master -z 4k

To rewrite a corrupt master database,
specifying device and page sizes, forcing the server to accept these
values in preference to what it may find in the config block:

sqlsrvr -d d_master -w master -z 4k -b 100.02M -f

To rewrite a corrupt master database, specifying a page size that does not match
what the server finds in its config block, which produces a failure:

sqlsrvr -d d_master -w master -z 8k
00:00000:00000:2001/01/19 12:01:26.94 server The
configured server page size does not match that
specified on the command line. To use the configured
size, omit the command line size; to use the command
line size, specify 'force' (-f).

To rewrite a corrupt master database, specifying an incorrect page size, even in
a normal boot, which produces a failure:

sqlsrvr -d d_master -z4000
sqlsrvr: the 'z' flag may not be used without 'b' or
'w'. sqlsrvr: server will ignore the 'z' flag. sqlsrvr:
the 'z' flag contained an invalid page size. sqlsrvr:
the page size must be an even power of two between 2048
and 16384 bytes, inclusive.

Permissions

Anyone with execute permission on the binary, and who has
read/write access to all the files.