请问ziggler，PL/SQL Developer怎么export出数据？

ziggler

给你个图。TOOL/EXPORT TABLES

选择要导出的表，打开SQL INSERT标签。

如果需要我给你把MANUAL发上来，在131页。

[ 本帖最后由 ziggler 于 2009-9-2 16:52 编辑 ]

ziggler

This export method creates a standard SQL script with insert statements and (optionally) DDL
statements to recreate the table definition. The tab page contains the following options:
· Drop tables – The generated SQL script contains statements to drop the tables before they are
recreated and loaded. The Create tables, Truncate tables, and Delete records options are disabled
in this situation, and have an implicit value.
· Create tables – The generated SQL script contains statements to create the tables before they are
loaded. This includes constraints, indexes and grants.
· Truncate tables – The generated SQL script uses truncate table statements to empty the tables
before they are loaded. This option is faster than the Delete tables, but cannot be used if foreign
key constraints exist.
· Delete records – The generated SQL script uses delete statements to empty the tables before they
are loaded.
· Disable triggers – The generated SQL script disables all triggers of the tables before they are
loaded, and enables them afterwards. This can improve performance, and can sometimes be
necessary if the triggers contain checks that are not applicable to the import process.
· Disable foreign key constraints – The generated SQL script disables all foreign keys of the tables
before they are loaded, and enables them afterwards. This can be necessary for self-referencing
foreign keys. Foreign keys between different tables will not lead to conflicts, because the tables
are exported in a correct order. Disabling foreign keys can also improve performance.
· Include storage – The generated SQL includes the original storage information such as tablespace
names and initial sizes for table creation statements. These may differ across databases, so this
may not always be appropriate.
· Include privileges – The generated SQL includes the grants of the object privileges to other users
and roles. When the objects are recreated in a different database, these users and roles need to
exist for obvious reasons.
· Commit every – Controls how many records will be inserted in the generated SQL script before a
commit is executed. If this value is zero, all inserts will be committed at once at the end of the
SQL script. For large export files and small rollback segments it will be necessary to supply an
appropriate value here.
· Where clause – Only records that match the where claus

ziggler

This export method creates a standard SQL script with insert statements and (optionally) DDL
statements to recreate the table definition. The tab page contains the following options:
· Drop tables – The generated SQL script contains statements to drop the tables before they are
recreated and loaded. The Create tables, Truncate tables, and Delete records options are disabled
in this situation, and have an implicit value.
· Create tables – The generated SQL script contains statements to create the tables before they are
loaded. This includes constraints, indexes and grants.
· Truncate tables – The generated SQL script uses truncate table statements to empty the tables
before they are loaded. This option is faster than the Delete tables, but cannot be used if foreign
key constraints exist.
· Delete records – The generated SQL script uses delete statements to empty the tables before they
are loaded.
· Disable triggers – The generated SQL script disables all triggers of the tables before they are
loaded, and enables them afterwards. This can improve performance, and can sometimes be
necessary if the triggers contain checks that are not applicable to the import process.
· Disable foreign key constraints – The generated SQL script disables all foreign keys of the tables
before they are loaded, and enables them afterwards. This can be necessary for self-referencing
foreign keys. Foreign keys between different tables will not lead to conflicts, because the tables
are exported in a correct order. Disabling foreign keys can also improve performance.
· Include storage – The generated SQL includes the original storage information such as tablespace
names and initial sizes for table creation statements. These may differ across databases, so this
may not always be appropriate.
· Include privileges – The generated SQL includes the grants of the object privileges to other users
and roles. When the objects are recreated in a different database, these users and roles need to
exist for obvious reasons.
· Commit every – Controls how many records will be inserted in the generated SQL script before a
commit is executed. If this value is zero, all inserts will be committed at once at the end of the
SQL script. For large export files and small rollback segments it will be necessary to supply an
appropriate value here.
· Where clause – Only records that match the where clause will be exported. The where clause must
%0

ziggler

我一般数据量少喜欢用这种方式，尤其是代码表这样的东西。

我总觉的SQL脚本比较可靠。

ziggler

如果是生产系统的话，数据库的补丁都应该搞成SQL语句，这样最好。

ziggler

有点发散。^_^

ziggler

SQL脚本，我喜欢。