New answers tagged export
I think the most efficient way in your case will be: --uncomment if you are allowed do this: drop table HUGE_TABLE; --uncomment if you are allowed do this: drop table HUGE_TABLE_WITH_BLOBS; create table HUGE_TABLE NOLOGGING PARALLEL 4 as select * from HUGE_TABLE@Distantdb; create table HUGE_TABLE_WITH_BLOBS NOLOGGING PARALLEL 4 as select * from ...
I've created an open source project to create MS SQL Server database documentation. http://jeremykdev.github.io/SqlServerDatabaseDocumentationGenerator
I'm sorry you haven't had a response since yesterday; here's at least a starting point for you. You can try pulling the pieces you need out of. As always, read the discussion threads (I was, regrettably, unable to find a script endorsed by the big names I recognize, so test thoroughly! Schema, object, server, and column level permissions are often ...
You can generate DDL statements using imp/impdp utilities: imp user/passwd file=export.dmp show=y log=export.sql 2> /dev/null impdp user/passwd file=DIR:export.expdp sqlfile=DIR:export2.sql But this method will generate just schema DDL. INSERT statements will not be generated.
Top 50 recent answers are included