sqlserverdump version 1.3
Software created by Daniel Jann, inspired by the mysqldump utility by
Igor Romanenko, Monty, Jani & Sinisa.
This sofware relies on SQL Server Management Objects (SMO) in order to generate
the SQL statements.
This software comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to modify and redistribute it under the GPL license.

When dumping data containing non-ascii base characters, use the --result-file
rather than dumping the command line output to a file, because dumping
the command-line to a file uses a DOS encoding.

The resulting dump can be used in Microsoft's SQL Server Management Studio.

Dumping structure and contents of SQL Server databases and objects.
Usage: sqlserverdump [OPTIONS] database [OBJECT1 [OBJECT2 [...]]]
OR sqlserverdump [OPTIONS] --databases [OPTIONS] DB1 [DB2 [DB3 [...]]]
OR sqlserverdump [OPTIONS] --all-databases [OPTIONS]

The following options may be given:

--all-databases
Dump all the databases. This will be same as --databases
with all databases selected.

--databases
Dump several databases. Note the difference in usage; in
this case no objects names are given. All name arguments
are regarded as database names. 'USE db_name;' will be
included in the output.

--result-file=name
Direct output to a given file. If omitted, result will be
directed to standard output.

--server-name=instancename
Connect to the local instance instancename. If this
option is omitted, it will try to connect to the local
instance. If there is more than one local instance, an
error message will be output. It is recommended to
always use this option (with this syntax or the one
below) as detecting the local instance doesn't always
work.

--server-name=host\instancename
Connect to the instance instancename on host. If this
option is omitted, it will try to connect to the local
instance. If there is more than one local instance, an
error message will be output. It is recommended to
always use this option (with this syntax or the one
above) as detecting the local instance doesn't always
work.

--server-name=host
This option requires the sql-engine option to be used.
server-name specifies to which host connect when
connecting to a sql engine rather than a named instance.

--sql-engine
Use sql engine rather than named instance. The
server-name will be used as the host to which connect. If
server-name is omitted, it will try to connect on the
local host (127.0.0.1)

--username=username
Connect using specified username

--password[=password]
Connect using specified password. If password is
omitted, it will be prompted on stdin without
echoing (good security practice on a command line as the
password will not show on the screen nor in the command
line history).

--system-databases
Include system databases. Not included by default.

--system-objects
Include system objects (except for sysdiagrams table
which is always included). Not included by default.

--no-data
Do not write any table row information (that is, do not
dump table contents).

--no-schema
Do not write schema information (create table).

--no-tables
Do not dump tables (neither schema, nor data).

--no-indexes
Do not dump indexes.

--no-checks
Do not dump column specific dependency relationships as
defined in check constraints with enforced declarative
referential integrity

--no-primary-key
Do not dump dependency relationships that are defined in
primary keys which have enforced declarative referential
integrity

--no-foreign-keys
Do not dump dependency relationships defined in foreign
keys with enforced declarative referential integrity

--no-unique-keys
Do not dump dependency relationships that are defined in
unique keys which have enforced declarative referential
integrity

--no-views
Do not dump views definitions.

--no-triggers
Do not dump triggers definitions.

--no-synonyms
Do not dump synonyms definitions.

--no-stored-procedures
Do not dump stored procedures definitions.

--no-user-defined-functions
Do not dump user defined functions definitions.

Last edited Jan 18, 2013 at 1:15 PM by helvartis, version 1

Comments

No comments yet.