||Prints out diagnostic information for deadlock prevention.
||Prints out diagnostic information when avoiding deadlock.
||Turn off transaction logging for the entire SQL dataserver.
||Send deadlock detection to the errorlog.
||Stack trace on deadlock.
||Disable lock promotion.
||Use standard disk I/O (i.e. turn off asynchronous I/O).
||Start secondary engines by hand
||Create a debug engine start file. This allows you to start up a debug engine
which can access the server's shared memory for running diagnostics. I'm not sure how
useful this is in a production environment as the debugger often brings down the server.
I'm not sure if Sybase have ported the debug stuff to 10/11. Like most of their debug
tools it started off quite strongly but was never developed.
||Startup only engine 0; use dbcc engine("online") to incrementally
bring up additional engines until the maximum number of configured engines.
||Boot the SQL dataserver with TCP_NODELAY enabled.
||If possible, pin shared memory -- check errorlog for success/failure.
||Set affinity of the SQL dataserver engine's onto particular CPUs -- usually pins
engine 0 to processor 0, engine 1 to processor 1...
||SGI only: turn on recoverability to filesystem devices.
||Linux only: Revert to using cached filesystem I/O. By default, ASE on
Linux (11.9.2 and above) opens filesystem devices using O_SYNC, unlike other Unix based releases,
which means it is safe to use filesystems devices for production systems.
||Prevent dbcc from checking syslogs. Useful when you are constantly getting spurious
||Display each log record that is being processed during recovery. You may wish to
redirect stdout because it can be a lot of information.
||Track checkpointing of databases in errorlog.
||Stack trace when error raised.
||Send dbcc output to screen.
||Send dbcc output to errorlog.
||Do not recover any database, clear behaviour start up checkpoint process.
||Recover master only. Do not clear tempdb or start up checkpoint process.
||Recover all databases. Do not clear tempdb or start up checkpoint process.
||Pre-System 10 behaviour: divide by zero to result in NULL instead of error - also see Q6.2.5.
||Do not kill infected processes.
||Very verbose logging of each login attempt to the errorlog. Includes tons of information.
||Don't spawn chkptproc.
||Place a record in the errorlog for each login to the dataserver.
||Boot without recover.
||Forces all I/O requests to go through engine 0. This removes the contention between
processors but could create a bottleneck if engine 0 becomes busy with non-I/O tasks. For
||Prevents engine 0 from running any non-affinitied tasks. For more information...5101/5102.
||Disable table lock promotion for text columns.
||Display statement and transaction locks on a deadlock error.
||Starting with System 11 these are sp_configure'able