Conventions

Style Conventions

Key	Definition
monospaced(fixed-width)	SQL and program code Commands to be entered exactly as shown File names Directory names
`italic monospaced`	In SQL or program code snippets, placeholders for user-specified values (see example below).
`italic`	File and variable names Cross-references to other topics or documents In text, placeholders for user-specified values (see example below) Glossary terms in text
bold san serif	Command, function, stored procedure, utility, class, and method names Glossary entries (in the Glossary) Menu option paths In numbered task or procedure steps, user-interface (UI) elements that you click, such as buttons, check boxes, icons, and so on

If necessary, an explanation for a placeholder (system- or setup-specific values) follows in text. For example:

Run:

installation directory\start.bat

where installation directory is where the application is installed.

Key	Definition
{ }	Curly braces indicate that you must choose at least one of the enclosed options. Do not type the braces when you enter the command.
[ ]	Brackets mean that choosing one or more of the enclosed options is optional. Do not type the brackets when you enter the command.
( )	Parentheses are to be typed as part of the command.
\|	The vertical bar means you can select only one of the options shown.
,	The comma means you can choose as many of the options shown as you like, separating your choices with commas that you type as part of the command.
...	An ellipsis (three dots) means you may repeat the last unit as many times as you need. Do not include ellipses in the command.

Valid characters for input values are _ , a-z, A-Z, 0-9, -, and :. All other characters must be within quotes. Any input value string that contains a blank space must be within quotes (single or double).
The keyword go is treated as a command terminator.
Use reset to clear the command buffer.
Use “--” or “#” to comment out a single line in the script.

All command syntax and command examples are shown in lowercase. However, Replication Server® Data Assurance Option command names are not case-sensitive. For example, CONFIG, Config, and config are equivalent.
Names of configuration parameters are not case-sensitive. For example, MAX_CONCURRENT_COMPARISONS is the same as max_concurrent_comparisons.

User connection properties are case-sensitive. For example:

alter connection myconn
 with properties
  set you=sybase and set YOU=sybase

Adaptive Server® database objects are case-sensitive. Use the correct case for table names when you specify database objects in your DA configuration.