ddlgen

A Java-based tool that generates definitions for server- and database-level objects in Adaptive Server.

The command-line version of ddlgen is located in:

(UNIX) $SYBASE/$SYBASE_ASE/bin.
(Windows) %SYBASE%\%SYBASE_ASE%\bin.

Syntax

ddlgen 
	-Ulogin
	-Ppassword
	-S[[ssl:]server | host_name : port_number]
	[-I interfaces_file]
	[-Tobject_type]
	[-Nobject_name]
	[-Ddbname]
	[-Cproperty_name=property_value]
	[-Xextended_object_type]
	[-Ooutput_file]
	[-Eerror_file]
	[-Lprogress_log_file]
	[-Jclient_charset]
	[-LC -N logical_cluster_name
	-F[ % | SGM | GRP | USR | R | D | UDD | U | V | 
		P | XP | I | RI | KC | TR | PC ]

ddlgen -v

Parameters

-U login – specifies a login name, and is case-sensitive.
-P password – specifies your password.
If you do not include the -P parameter in your ddlgen statement, ddlgen prompts you to specify a password.
-S [[ssl:] server | host_name : port_number] – specifies the name of the Adaptive Server. ddlgen looks this name up in the interfaces file or LDAP configuration file. If you specify:
- [ssl:] – allows you to generate DDL for objects in SSL-enabled servers. This parameter is optional.
- -S[host_name:port_number] – ddlgen uses the host_name and port_number provided, and neither interfaces nor LDAP configuration files are read or parsed.
- -S[server] -I – ddlgen parses the interfaces file specified at the user location for the server name (see the -I parameter description).
- -S[server] – without specifying an interfaces file, ddlgen does:
  1. ddlgen first tries to read the LDAP configuration file from the standard location
  2. If the LDAP file does not exist, or exists but does not contain an Adaptive Server entry, then the interfaces file is parsed at its standard location for the server name
  3. If the LDAP file exists, then ddlgen uses it to search the server name. The interfaces file is not parsed, and the LDAP configuration file is parsed.
Note: You must use the -S option because ddlgen does not connect to a default server.
-I – specifies the interfaces file name, and corresponds to $SYBASE/interfaces for UNIX, and %SYBASE%\ini\sql.ini for Windows. Use this optional parameter with -S.
-Tobject_type – specifies the type of object you are creating. If you do not use -T, ddlgen generates DDL for the default database of login. The object types for -T are:
- C – cache
- D – default
- DB – database
- DBD – database device
- DPD – dump device
- EC – execution class
- EG – engine group
- EK – encrypted keys
- GRP – group
- I – index
- IT – instead of trigger for views
- KC – key constraints
- L – login
- LK – logical key
- P – stored procedure
- PN – partition name
- R – rule
- RI – referential integrity
- RO – role
- RS – remote server
- SGM – segment
- TR – trigger
- U – table
- UDD – user-defined datatype
- USR – user
- V – view
- WS – user-defined Web service
- WSC – Web service consumer
- XOD – local caches
- XOU – global caches
- XP – extended stored procedure
-Nobject_name – specifies the fully qualified name of the object you are creating, such as -Ndb_name.owner_name.table_name.object_name. The -N option:
- Is required if you specify any object_type other than DB (database) in the -T parameter.
- Accepts wildcards with the use of %.
- Generates DDL for a trigger for a table, using the -Ndb_name.table_owner.table_name.trigger_name format.
  
  To generate all triggers for a table, substitute trigger_name with % using the -Ndb_name.table_owner.table_name.% format.
- Generates DDL for an encrypted key with -Ndb_name.owner.key_name.
- Generates DDL for all items of a specific object type on your server.
- Enforces strict order in which it parses the names in the -Ndb_name.owner_name.table_name.object_name format. If you only provide three arguments, ddlgen assumes they are owner_name, table_name, and object_name, in that order. Alternatively, you can also use -Nowner_name.table_name -Ddb_name. ddlgen does not impose this restriction if object_name is an index (I).
-Ddbname – specifies the name of the database for the object you specify in the -N option. The default is the user’s default database.
You cannot use the -D parameter when generating DDL for all triggers of a table.
-Cproperty_name=property_value – allows you to set connection properties. You can set multiple properties; separate them with commas, such as:
```
-Cproperty_value1=property_value1,property_name2=property_value2
```
-Xextended_object_type – differentiates:
- User tables (OU) from proxy tables (OD) when you specify a table as your object type (-TU)
- Temporary databases (OD) from normal databases (OU) or archive databases (OA) when you specify database as your object type (-TDB)
- SQLJ procedures (OD) from stored procedures (OU) when you specify procedure as your object type (-TP).
If object_type (-T) is U (table) and -X is not specified, ddlgen generates DDL for both user tables and proxy tables. To generate DDL only for:
- user tables – use the OU extended object type with the -X option.
- proxy tables – use the OD extended object type with the -X option.
- in-memory databases, caches, and devices – use the OI extended object type with the -X option.
- in-memory temporary databases – use the OIT extended object type with the -X option.
Note: ddlgen does not support schema generation for system tables.

Use extended_object_type DE (-XDE), with the database object type (-TDB) to generate a database and all of its objects in correct dependent order.
-Ooutput_file – specifies an output file for the generated DDL. If you do not specify -O, the DDL you create appears in a console window.
-Eerror_file – specifies a log file for recording errors. If you do not specify -E, the generated errors appear in a console window.
-Lprogress_log_file – specifies a log file for recording the progress of ddlgen. If you do not specify -L, the progress is not recorded.
-Jclient_charset – specifies the character set to use on the client. -Jclient_charset requests that Adaptive Server convert to and from client_charset, the character set used on the client. A filter converts input between client_charset and the Adaptive Server character set.
Omitting -J sets the character set to a default for the platform. The default may not necessarily be the character set that the client is using.

Note: For HP platforms – you must use -Jiso_1 to specify the correct character set.
-LC – generate DDL for one or all logical clusters on a server.
-F – filters out indexes, triggers, and constraints out of table and database definitions in the DDL of table- and database-level objects. The valid filters are:
- For tables – [ % | I | RI | KC | TR | PC ]
- For databases – [ % | SGM | GRP | USR | R | D | UDD | U | V | P | XP | I | RI | KC | TR]
The filter options are:
- % – everything. Retrieves the schema-only definition of a database or table.
- SGM – segments
- GRP – groups
- USR – users
- R – rules
- D – defaults
- UDD – uer-defined datatypes
- U – user tables
- V – views
- P – stored procedures
- PC – partition condition
- XP – extended stored procedures
- I – indexes
- RI – referential integrity constraints
- KC – primary- and unique-key constraints
- TR – triggers
If you use an invalid filter parameter, ddlgen generates a warning, ignores that parameter, and continues with the rest of the valid parameters you specify.

If you specify % along with other filter parameters, ddlgen ignores all other filterable parameters, and only shows schema-only definitions. ddlgen then continues to evaluate the dependencies within the subset of the applied as the filterable parameters for the database.
-v – displays the version and copyright message of ddlgen and returns to the operating system.

Examples

Archive database – To generate DDL for all archive databases, use the extended filter option “OA.”
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TDB -N% -XOA
```
To generate DDL for a single archive database, use the syntax for normal databases. This example creates DDL for the archive database adb1.
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TDB -Nadb1
```
Caches – Generates DDL for a cache called default data cache on a machine named HARBOR using port 1955:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TC -N"default data cache"
```
To generate DDL for all caches:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TC -N%
```
Connection properties –
Generates DDL for a database that uses an encrypted password for its connection:
```
ddlgen -Usa -Psybase -Sbjrhx64:7710 -Tdb -Nmodel -CENCRYPT_PASSWORD=true
```
Databases – Generates DDL for a database called pubs2 on a machine named HARBOR using port 1955:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TDB -Npubs2
```
If you do not specify a dbname, ddlgen generates DDL for the default database of login:
```
ddlgen -Ulogin -Ppassword -Sserver:port
```
If you do not use the -T parameter, ddlgen generates DDL for a default-type database:
```
ddlgen -Ulogin -Ppassword -Sserver:port -Ndbname
```
To generate DDL for all databases:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TDB -N%
```
Defaults – Generates DDL for a default called “phondflt” owned by jones in the pubs2 database on a machine named HARBOR using port 1955:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TD -Njones.phonedflt -Dpubs2
```
Alternatively, because ddlgen allows you to use a fully qualified name in the -N flag, omit the -Ddbname and include the database name in the -N option:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TD -Ndbname.owner.defaultname
```
To generate DDL for all defaults in a database owned by “owner”:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TD -Nowner.% -Ddbname
```
Database devices – Generates DDL for a database device called master running on a machine named HARBOR using port 1955:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TDBD -Nmaster
```
To generate DDL for all database devices:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TDBD -N%
```
Dump devices – Generates DDL for a dump device called tapedump1 running on a machine named HARBOR using port 1955:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TDPD -Ntapedump1
```
To generate DDL for all dump devices:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TDPD -N%
```
Encrypted keys – Generates DDL for all encryption keys in the accounts database on a machine named “HARBOR” using port 1955:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TEK
    -Naccounts.dbo.%
```
Alternatively, you use the -D option to specify the database name.
Encrypted keys – Generate DDL for an encryption key “ssn_key” in a the SampleKeysDB database:
```
ddlgen -Usa -P -Sserver -TEK -NSampleKeysDB.dbo.ssn_key
```
Add -FEKC to avoid creating DDL for key copies when generating DDL for the “ssn_key” encryption key:
```
ddlgen -Usa -P -Sserver -TEK -NSampleKeysDB.dbo.ssn_key      -FEKC
```
Encrypted passwords – Generates system encryption passwords along with DDLs for encryption keys when you include the extended option -XOD. The output generates the sp_encryption statement followed by DDL statements for all encrypted keys. This generates DDL for the login “george” on a machine named HARBOR using port 1955:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TEK -Ngeorge -XOD
```
To generate DDL for all the encrypted keys in the authors database on a machine named HARBOR using port 1955:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TEK -Nauthors.dbo.%
```
Engine groups – Generates DDL for an engine group called LASTONLINE running on a machine named HARBOR using port 1955:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TEG -NLASTONLINE
```
To generate DDL for all engine groups:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TEG -N%
```
Execution class – Generates DDL for an execution class called EC2 running on a machine named HARBOR using port 1955:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TEC -NEC2
```
To generate DDL for all execution classes:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TEC -N%
```

Extended object type –

The example uses the following:

create database tdb on default = '20M'

use tdb

create table test ( 
fid varchar(10) 
) 

create view View_A as select * from test 

create view View_B as select * from View_A 
CREATE FUNCTION  Func_C(@ID VARCHAR(10)) 
RETURNS varchar(8000) 
AS 
BEGIN 
declare @ret varchar(8000) 
select @ret = (select  fid from View_B) 
 return @ret 

END 
go 

create view View_D as 
select * from test where fid>dbo.Func_C('111') 
go 

CREATE FUNCTION  Func_no_depend(@ID VARCHAR(10)) 
RETURNS varchar(8000) 
AS 
BEGIN 
declare @ret varchar(8000) 
 return @ret 
END 
go

Issuing ddlgen returns all objects of database tdb in correct dependent order:

ddlgen –S –U –P –TDB –Ntdb –XDE

Segment
Group
User
Rules
Defaults
UDDs
Encrypted Keys
User Tables
Proxy Tables
Triggers
Functions and Views
1. All functions without any dependency
2. All views without any dependency
3. All functions and all views with any dependency on any objects
Instead of trigger
Stored Procedures
Extended Stored Procedures
PRS
User Defined Web Services

Extended stored procedures – Generates DDL for the xp_cmdshell extended stored procedure in the pubs2 database, owned by Jones and running on a machine named HARBOR using port 1955, by using the fully qualified dbname.owner.extendedstoredprocedure format with the -N option:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TXP -Npubs2.jones.xp_cmdshell
```
Alternatively, use the -D option instead of using the fully qualified name:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TXP 
    -Nowner.extendedstoredprocedure -Ddbname
```
To generate DDL for all extended stored procedures:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TXP -Ndbname.owner.%
```
Filters – Generates DDL for the authors table in the pubs2 database, filtering for all indexes (I), and referential integrity constraints (RI), primary and unique key constraints (KC), triggers (TR), and partition condition (PC) from the DDL of a table:
```
ddlgen -Uroy -Proy123 -TU -Nauthors -Dpubs2 -F%
```
Alternatively, specify each of the filters individually:
```
ddlgen -Ulogin -Ppassword -TU -Ndbname.owner.table
    -FI,RI,KC,TR
```
This generates the definition of table_name while filtering out foreign keys and primary-unique keys:
```
ddlgen -Ulogin -Ppassword -TU -Ntable_name -Ddbname 
    -FRI,KC
```
Both of these generate foreign keys for a specified user in the entire database:
```
ddlgen -Ulogin -Ppassword -TRI -N%.%.% -Ddbname
```
Or:
```
ddlgen -Ulogin -Ppassword -TRI -Ndbname%.%.%
```
Both of these generate DDL for the primary and unique keys of all the tables in a database that begin with “PK”:
```
ddlgen -Ulogin -Ppassword -TKC -Ndbname.%.%.PK%
```
Or:
```
ddlgen -Ulogin -Ppassword -TKC -N%.%.PK% -Ddbname
```
This generates schema-only definition of a database:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TF -Ndbname -F%
```
Alternatively, specify each of the filters individually:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TDB -Ndbname 
    -FSGM,GRP,USR,R,D,UDD,V,P,XP,I,RI,KC,TR
```
This generates the database DDL skipping the compiled object:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TDB -Ndbname 
    -FTR,D,XP,V,R
```
This generates database definition without a table definition:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TDB -Ndbname 
    -FU
```
Groups – Generates DDL for a group called “public” in the pubs2 database, running on a machine named HARBOR using port 1955, by using the fully qualified dbname.groupname format in the -N option:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TGRP -Npubs2.public
```
Alternatively, use the -D option to specify the dbname:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TGRP -Ngroupname -Ddbname
```
To generate DDL for all groups:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TGRP -Ndbname.%
```
In-memory database – Generates DDL for an in-memory database:
```
 ddlgen -Uroy -Proy123 -SHARBOR:1955 -TDB -Nimdb_1
```
Use the same syntax to generate DDL for an in-memory temporary database:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TDB -Nimdb_temp1
```
Indexes – Generates DDL for an index called au_lname for the table authors owned by dbo, in the pubs2 database:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TI -Ndbo.authors.au_lname -Dpubs2
```
Alternatively, because ddlgen allows you to use a fully qualified name in the -N flag, omit the -Ddbname and include the database name in the -N option:
```
ddlgen -Ulogin -Ppassword -Sserver:port
    -TI -Ndbname.owner.tablename.indexname
```
If you use a fully qualified name, you may omit the -D option.
To generate DDL for all indexes for a single table:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TI 
    -Ndbname.owner.tablename.%
```
To generate DDL for all indexes of all tables in a database:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TI 
    -Ndbname.%.%.%
```
For example, this generates DDL for all indexes for all tables in the pubs2 database:
```
ddlgen -Usa -P -SHARBOR:1955 -TI -Npubs2.%.%.%
```
Instead of triggers – Generates one view and its (instead of) trigger, and next view and its (instead of) trigger:
```
ddlgen -S -U -P -TV -Ndbname.ownername.viewname
```
Generates triggers only for tables:
```
ddlgen -S -U -P -TTR
```
Generates instead of triggers for views:
```
ddlgen -S -U -P -TIT
```
Keys – Both of these generate DDL for the primary and unique keys of all the tables in a database that begin with “PK”:
```
ddlgen -Usa -P -TKC -Ndbname.%.%.PK%
```
Or:
```
ddlgen -Usa -P -TKC -N%.%.PK% -Ddbname
```
Logical cluster – Generates DDL for “my_lcluster” on server “ase1”, enter:
```
ddlgen -Usa -P -Sase1 -TLC -Nmy_lcluster
```
Logical cluster – Generates DDL for all logical clusters on server “ase1”, enter:
```
ddlgen -Usa -P -Sase1 -TLC -N%
```
Logical keys – LK generates logical keys of table defined by sp_primarykey, sp_commonkey, sp_foreignkey statements. Since these keys do not have a name, the name of the object in this case would be the name of the table. This example generate a DDL for logical keys of table authors in database pubs2 running on a machine named HARBOR using port 1955:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TLK -Npubs2.dbo.authors
```
To generate DDL for all logical keys in database pub2 use:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TLK -Npubs2.%.%
```
To filter out logical keys definition from DDL of table authors use LK in -F argument, use:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TLK -Npubs2.dbo.authors -FLK
```
Logins – TL generates DDL for one or all logins. This example generates DDL for all logins on a machine named HARBOR using port 1955:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TL -N%
```
Note: The password in the DDL generated for all logins is “password”.
Alternatively, specify an individual login by using -Nusername instead of -N%:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TL -Nusername
```
If server-wide password complexity options have been specified for the login or logins, all sp_addlogin and sp_loglogin DDL statements are generated first, followed by DDL statements for the password options. This example generates DDL for the login “george” on a machine named HARBOR using port 1955:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TL -Ngeorge
```
Remote servers – Generates DDL for a remote server called ORANGE on a machine named HARBOR using port 1955:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TRS -NORANGE
```
To generate DDL for all remote servers:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TRS -N%
```
Roles – Generates DDL for the sa_role on a machine named HARBOR using port 1955:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TRO -Nsa_role
```
To generate DDL for all roles:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TRO -N%
```
Note: The password in the DDL generated for all roles is “password”.
Rules – Generates DDL for all rules associated with authors on a machine named HARBOR using port 1955:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TR -Nauthors.dbo.%
```
The % symbol tells ddlgen to create DDLs for all rules that exist on the server.
You can also give the fully qualified name of the rule:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TR -Ndbname.owner.rulename
```
Alternatively, also use the -D parameter:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TR -Nowner.rulename -Ddbname
```
Segments – Generates DDL using the fully qualified dbname.segmentname format in the -N option for a segment called logsegment for the pubs2 database, on a machine named HARBOR using port 1955:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TSGM -Npubs2.logsegment
```
Alternatively, specify the dbname using the -D option:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TSGM -Nsegmentname -Ddbname
```
To generate DDL for all segments:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TSGM -Ndbname.%
```

SQLJ functions – Generates DDL for a SQLJ function named region_of owned by dbo in database master:

ddlgen -Uroy -Proy123 -SHARBOR:1955 -TF –Nmaster.dbo.region_of

Alternatively also use the -D parameter:

ddlgen -Ulogin -Ppassword -Sserver:port -TF –Ndbo.region_of –Dmaster

To generate DDL for all SQLJ functions in a database, use object type F:

ddlgen -Ulogin -Ppassword -Sserver:port -TF –Ndbname.owner.%

SQLJ procedures – A kind of stored procedure, you generate DDL for SQL procedures along with DDL for stored procedures. This generates DDL for all stored procedures—including SQLJ procedures—owned by dbo in the master database:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TP –Nmaster.dbo.% 
```
To generate DDL for all SQLJ procedures that are only owned by dbo in the master database, use this, where the extended type OD refers to SQLJ procedures:
```
ddlgen -Ulogin -Ppassword-Sserver:port -TP –Nmaster.dbo.% -XOD
```
To generate DDL for all procedures except SQLJ procedures owned by dbo in the master database, use this, where the extended type OU refers to all stored procedures except SQLJ procedures:
```
ddlgen -Ulogin -Ppassword-Sserver:port -TP –Nmaster.dbo.% -XOU
```
Stored procedures – Generates DDL for the sp_monitor stored procedure for the pubs2 database on a machine named HARBOR using port 1955, using the fully qualified dbname.owner.procedure_name format for the -N option:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TP -Npubs2.dbo.sp_monitor
```
Alternatively, specify the dbname using the -D option:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TP -Nowner.procedurename -Ddbname
```
To generate DDL for all stored procedures:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TP -Ndbname.owner.%
```
SSL-enabled servers – Generates DDL for objects in the pubs2 database for an SSL-enabled Adaptive Server running on a machine named HARBOR using port 1955:
```
ddlgen -Uroy -Proy123 -Sssl:HARBOR:1955 -TDB -Npubs2
```
Tables – Generates DDL for all user tables in the pubs2 database owned by “dbo” and running on a machine named HARBOR using port 1955:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TU -Ndbo.% -Dpubs2
```
You can also use the -N parameter to give the fully qualified name of the table:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TU
    -Ndbname.tableowner.tablename
```
Alternatively, also use the -D parameter to specify the database:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TU
    -Ntableowner.tablename -Ddbname
```
To generate DDL for all proxy tables, which uses the value OD, use -XOD instead, where X is the extended type, and OD denotes proxy tables:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TU 
    -Ntableowner.% -Ddbname -XOD
```
To generate DDL for all user tables, which uses the value OU, use -XOU instead, where X is the extended type, and OU denotes user tables:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TU 
    -Ntableowner.% -Ddbname -XOU
```
To generate DDL for all tables, including user tables and proxy tables:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TU -Ndbname.tableowner.%
```
Temporary databases – Generates DDL for all databases, including tempdb:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TDB -N%
```
To generate DDL for all temporary databases, use the OD extended database type:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TDB -XOD -N%
```
Although you can use the OD extended type in Adaptive Server versions 12.5.0.3 and later, versions earlier than 12.5.0.3 issue warning messages. Safely ignore this message; ddlgen continues processing the command.To generate DDL for all databases except temporary databases, use the OU extended type:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TDB -XOU -N%
```
This generates DDL for a temporary database named tempdb1:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TDB -Ntempdb1
```
The output includes:
- A create temporary database statement:
```
create temporary database tempdb1 on master = 4, 
    asdas = 2
go
```
- An sp_tempdb bind statement where the isql application is bound to tempdb1:
```
sp_tempdb 'bind','ap', 'isql', 'DB', 'tempdb1'
go
```
Note: DDL for objects such as views, stored procedures, and tables is not generated along with DDL for a temporary database because these objects are temporary, and are re-created when the server restarts.
When you use the -F parameter to filter a table while generating DDL for a database object, then indexes, referential integrity, key constraints and triggers automatically get filtered, as they are a subset of the table object.
Triggers – Generates DDL for the trigger checksum for the pubs2 database on a machine named HARBOR using port 1955, using the fully qualified dbname.owner.trigger_name format for the -N option:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TTR -Npubs2.dbo.checksum
```
Alternatively, specify the database_name using the -D option:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TTR 
    -Nowner.triggername -Ddbname
```
You can also generate DDL for a trigger for a table, using:
```
-Ndb_name.table_owner.table_name.trigger_name
```
To generate DDL for all triggers of a database:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TTR -Ndbname.owner.%
```
You can also use this format to generate DDL for all triggers of a table:
```
-Ndb_name.table_owner.table_name.%
```
Note: You cannot use the -D parameter when generating DDL for all triggers of a table.
User-defined datatypes – Generates DDL for the user-defined datatype “Identype” for the pubs2 database on a machine named HARBOR using port 1955 using the fully qualified dbname.userdefined_datatype format for the -N option:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TUDD -Npubs2.Identype
```
Alternatively, use the -D option to specify the dbname:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TUDD 
    -Nuserdefined_datatype -Ddbname
```
To generate DDL for all user-defined datatypes:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TUDD -Nbname.%
```
Views – Generates DDL for a view named retail owned by Miller in the pubs2 database running on a machine named HARBOR using port 1955, by using the fully qualified dbname.owner.viewname format with the -N option:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TV -Npubs2.miller.retail
```
Alternatively, use the -D option instead of using the fully qualified name:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TV -Nowner.viewname -Ddbname
```
To generate DDL for all views:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TV -Ndbname.owner.%
```
User-defined Web services – Generates DDL for a named user-defined Web service, sp_who_service, in the pubs2 database running on a machine named HARBOR using port 1995, by using a fully qualified dbname.username.webservice_name format with the -N and -T options:
```
ddlgen -Uroy -Proy123 -SHARBOR:1995 -TWS 
    -Npubs2.dbo.sp_who_service
```
The syntax for generating DDL for a named user-defined Web service is:
```
ddlgen -Ulogin -Ppassword -Shost_name:port -TWS -Ndbname.owner.webservice_name
```
To generate DDL for all user-defined Web services owned by all users in database dbname:
```
ddlgen -Ulogin -Ppassword -Shost_name:port -TWS -Ndbname.%.%
```
Note: An sp_webservices 'addalias' statement is only generated if the DDL is to be generated for all user-defined web services or for a database.
Users – Generates DDL for a user named Smith in the pubs2 database running on a machine named HARBOR using port 1955, by using a fully qualified dbname.username format with the -N option:
```
ddlgen -Uroy -Proy123 -SHARBOR:1955 -TUSR -Npubs2.smith
```
Alternatively, use both the -N and -D options instead of using a fully qualified name in -N:
```
ddlgen -Ulogin -Ppassword -Shost_name:port -TUSR -Nusername -Ddbname
```
To generate DDL for all users:
```
ddlgen -Ulogin -Ppassword -Sserver:port -TUSR -Ndbname.%
```

Permissions

Users must have either sa_role or sso_role to generate DDL for:

Encryption keys
Logins
Roles

For all other objects, users do not need any specific permissions or roles to generate DDL.