sqlsrvr

Description

Syntax

sqlserver [-f] [-g] [-G] [-h] [-H] [-m] [-P] [-q] [-v] [-X]
	[-a path_to_CAPs_directive_file]
	[-b master_device_size] [k | K | m | M | g | G | t | T ]
	[-c config_file_for_server]
	[-d device_name]
	[-e path_to_error_log]
	[-i interfaces_file_directory]
	[-K keytab_file]
	[-L config_file_name_for_connectivity]
	[-M shared_memory_repository_directory]
	[-p sa_login_name]
	[-r mirror_disk_name]
	[-s server_name]
	[-T trace_flag]
	[-u sa/sso_name]
	[-w master | model database]
	[-y [password] ]
	[-z page_size [ k | K ] ]

Parameters

Examples

Example 1

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.

Example 2

Rewrites a corrupt model database:

sqlsrvr -d d_master -w model

Example 3

Rewrites a corrupt master database, specifying device size:

sqlsrvr -d d_master -w master -z 4k

Example 4

Rewrites 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

Example 5

Rewrites a corrupt master database, specifying a page size that does not match what the server finds in its config block. This 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).

Example 6

Rewrites a corrupt master database, specifying an incorrect page size, even in a normal boot. This 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.

Usage

• The sqlsrvr utility is referred to as dataserver in other Sybase documents.

• Start Adaptive Server using the services manager utility rather than by executing the sqlsrvr program directly. If you need to change any of the default parameters, edit the Adaptive Server’s Registry keys. See the configuration guide for your platform for details.

• Adaptive Server derives its running environment from values in the sysconfigures system table. Run sp_configure to see the configuration values; use sp_configure and reconfigure to change the configuration.

• Because Adaptive Server passwords are encrypted, you cannot recover forgotten passwords. If all System Security Officers lose their passwords, the -p parameter generates a new password for a System Security Officer’s account. Start Adaptive Server with -p, immediately log in to Adaptive Server with the new random password, and execute sp_password to reset your password to a more secure one.

• By default, Adaptive Server logs error messages in both the local error log file and the local Windows event log. You can disable Windows event logging by including the -g parameter and specifying a different event-logging machine with -G machine_name. Use standard Windows conventions when entering the machine_name. For example, to designate a PC named “LOGSITE”, substitute “\\LOGSITE” for the machine_name. See the configuration guide for your platform for details on logging error messages.

• After you have finished running the installer, set the file permissions on the sqlsrvr executable to limit who can execute it.

• If you do not specify an Adaptive Server name with the -s parameter, and you have not set the DSLISTEN environment variable, sqlsrvr uses the default Adaptive Server name SYBASE. The value of the DSLISTEN environment variable overrides this default value, and the -s parameter overrides both the default and the DSLISTEN environment variable.

• Automatic login lockouts can cause a site to end up in a situation in which all accounts capable of unlocking logins (System Administrators and System Security Officers) are locked. If this occurs, use the sqlsrvr utility with the -u parameter to check the specified login for System Administrator or System Security Officer authorization, unlock the account, and reset the value of the current failed logins counter to zero.

• -f is only valid when used with -b and/or -w. The server fails to boot if you use -f without either -b or -w. -f forces the server in different ways, depending whether -w is present. See -b and -w below.

Use either of the following methods to start Adaptive Server with a specified configuration file:

• Use Server Config to configure the server to have the -c parameter. In the Configure Adaptive Server window, select the Command Line option, and in the Command Line Parameters window, enter:

  -Cconfiguration_file_pathname
  

  For example, entering “-chaze.cfg “ starts the server using the haze.cfg configuration file.

• Start Adaptive Server from the command line and provide the -c parameter.

The effect of -b changes depending on whether -w is present:

• -b without -w creates a new master device as named by -d (the default is d_master) and with the page size as specified by -z (the default is 2048):

  • If the named device already exists as an OS file, the attempt fails, and you must remove the existing file and try again.

  • If the named device names an existing raw partition, the attempt fails unless you include the -f flag. This reinitializes the raw partition as a server master device.

• -b with -w master tells dataserver to use the size specified in -z for the master device when recreating the master database. It implies nothing about creating a new device.

-w may or may not require additional flags:

• If you use -w model, the -z and -b flags are accepted but ignored.

• If you use -w master for new installations, -z and -b are not required because the device size information is stored in the config_block.

• If you use -w master to upgrade older installations:

  • The server requires -b and/or -z if the config_block does not contain a valid entry for the associated size(s). The command fails if it can't get valid data for the page size or device size.

  • You may provide -b and/or -z when the config_block contains valid entries for the size(s) they represent. However if the sizes do not match what is in the config_block, you must add -f to force your new size preferences.

  • -f may appear without either -b or -z, because -f also instructs the server to accept damaged allocation pages as belonging to the master database. This is useful for restoring badly corrupted databases. If you specify -w master -f, the server assigns to the master database every allocation page on the named master device that does not belong to some other database than master.

Permissions

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

Tables used

sysconfigures

See also