|
 This
page contains the most generic (and DBMS-independent) settings that
determine how the produced SQL would look:
Delimiter
on a new line - usually checked when
the delimiter is a word (like "go"). The SQL looks better when "go"
is placed on its own line.
Indentation
step - used
when generating CREATE TABLE statements and other similar
code.
Align
column types - when generating CREATE
TABLE statement, the program can check the lengths of all column
names in the table and pad them with blanks so that all data type
would start at the same column. With
fixed padding modifier adds additional
padding, if necessary, to align the data types to a specific
column.
Align
NULL etc - similar to column
alignment above, but aligns everything that goes in a column
definition after
the data type
(NULL, NOT NULL, IDENTITY, column constraints).
Put
column constraints on a new line - puts each such
constraint on a new line, indenting it against the start of the
column definition. If this is not checked, all constraints for a
column go on the same line.
Statement
separator (since 1.98 Build 102). Although MS SQL Server
doesn't require explicit ';' separators between SQL statements, the
server documentation recommends using them. This option enables
scripting of the trailing ';' in SQL commands. Before version 1.98,
the Diff didn't script the semicolon delimiter. This option
is enabled by default, so if you prefer the old way, you'll have to
turn the feature off. NOTE that regardless of the setting,
the semicolon is never appended to any of the schema objects whose
SQL code is stored at the server "as is": procedures, triggers,
functions, views, DEFAULTs and RULEs.
Note that, unlike
optional the ';' separator, the GO
batch
separator is not configurable. It is always scripted between
statements or certain statement groups, but is never passed to the
server. Instead, the SQL Editor
window splits the script on each GO
and
separately sends each part to the server.
Character
case options. Specifies whether the
resulting SQL should be in lowercase, in upper case, with
capitalized first letter in each word or just left unchanged. You
can specify this option separately for the reserved SQL keywords,
identifiers and data types.
Uppercase/lowercase
for side-by-side view... As of AdeptSQL
Diff 1.97 Build 100, this option has been
moved elsewhere, replaced
with this hot link to follow.
|
