I wrote a stored procedure to export a list of various database objects, but it doesn't seem to work with anything under Configuration.

PROCEDURE "ExportDatabaseObjectList" ()
BEGIN       
  -- List of tables
  EXECUTE IMMEDIATE 'EXPORT TABLE Information.Tables
     TO "TableList.txt"
     IN STORE Backups
     (Name)';

  -- List of views
  EXECUTE IMMEDIATE 'EXPORT TABLE Information.Views
     TO "Views.txt"
     IN STORE Backups
     (Name)';

  -- List of stored procedures
  EXECUTE IMMEDIATE 'EXPORT TABLE Information.Procedures
     TO "ProcedureList.txt"
     IN STORE Backups
     (Name)';

  -- List of functions
  EXECUTE IMMEDIATE 'EXPORT TABLE Information.Functions
     TO "FunctionList.txt"
     IN STORE Backups
     (Name)';

  -- List of roles
  EXECUTE IMMEDIATE 'EXPORT TABLE Configuration.Roles
     TO "RolesList.txt"
     IN STORE Backups
     (Name)';

  -- List of users
  EXECUTE IMMEDIATE 'EXPORT TABLE Configuration.Users
     TO "UserList.txt"
     IN STORE Backups
     (Name)';

  -- List of stores
  EXECUTE IMMEDIATE 'EXPORT TABLE Configuration.Tables
     TO "StoresList.txt"
     IN STORE Backups
     (Name)';

  -- List of jobs
  EXECUTE IMMEDIATE 'EXPORT TABLE Configuration.Jobs
     TO "JobsList.txt"
     IN STORE Backups
     (Name)';

END


Is it only possible to export Information tables?

Regards,

Steve

Steve,

<< I wrote a stored procedure to export a list of various database objects,
but it doesn't seem to work with anything under Configuration. >>

It's an issue with specifying the database name in an IMPORT or EXPORT TABLE
statement.  A fix will be in the next build or release, but for now you can
work around this by using a script instead and prefacing the EXPORT calls
for the Configuration database with this statement:

USE Configuration;

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" wrote:

<< It's an issue with specifying the database name in an IMPORT or EXPORT TABLE
statement.  A fix will be in the next build or release, but for now you can
work around this by using a script instead and prefacing the EXPORT calls
for the Configuration database with this statement:

USE Configuration; >>

Great, thanks Tim.

Regards,

Steve