Author: Mats Halfvares, Content Studio development team.

Published: 2008-10-10

Applies to: Content Studio ver. 5

Type: How to

More information

In Content Studio it is possible to dump a site to .DATX - files that can be used when installing a new Content Studio site. This makes it possible for a developer to build the customer's site on a development machine and install it via the Content Studio installation program. Site dumps can also be used as backup and has the advantage over regular SQL-server database backups in that that they are far more easy to restore on a new server. They are of course not a replacement for daily backups particulary not for sites with a lot of security set. The Site Exporter does not export any user or group information and no security information. To create a site dump you log on to the Content Studio server and you must have access to the SQL-server installation that drives the Content Studio site to be dumped. Before running the site dump you must know the name of the SQL-server database that contains the site to dump.


Run the Site Exporter utility that can be found as a shortcut on the Content Studio folder on the program menu. This utility starts by asking you for the name of the SQL-server instance and the database that contains the site. In the main window you need to select a folder in the file system where the DAT-files need to be located. Before running the dump you might need to set some options that affect perfomance and content of your dump.

  • Max file size: This option sets the maximum size that each of the dumped files can have. Setting this value to a low value will create more but smaller installer files and can increase performance when the files are used to install the site.
  • Max binary content: This value limits the size of the binary content in uploaded files that are dumped. If a very large document ex. a video exists on your site that has a content size that exceeds this limit the document will be dumped but its content will be empty. After installation you can manually upload this file again. This is mainly for performance and deployment reasons since both the dump and the installation of that document can take a very long time if the content is very large (> 5 Mb). Currently this size is limited to 20 Mb.
  • Destination compability level
    Between different versions of Content Studio new features are added to the product and by setting the compatibility level you adjust the data exported to the version of Content Studio where it gets installed. For example; you can down grade a site from version 5.2 (the current installation) to version 5.1 (the destination) by setting the compatibility level to Content Studio 5.1 and no features and data that does not exist in the earlier version gets exported. If you set the compatibility level to a value too high for the destination the installation of the web site will fail.
    If you try to dump a site database used with an older version of the product and you set the compatibility level to a higher value that the source, the Site Export utility will fail.
  • Use new DATX packing format
    When Content Studio introduced native 64-bit support the older DAT packing format become outdated. Instead a far more effective packing format DATX was introduced. For older versions of the product DATX cannot be used and for that reason Site Copy utility continues to support the older format but only if the destination is an older version. On 32-bit computers the Content Studio installation program can still read the older DAT format making it is possible to export an older site to a later version of the product.
  • Support Unicode content: This option allows you to preserve documents that have Unicode content ex. Chineese or Korean. Since the site dump will be stored as Unicode the .DAT-files will be double in size and this will also effect performance of the installation. Thus, you should only set this option if your site contains Unicode data. This option is not used with the new DATX format since these dumps are fully Unicode by default.
  • Copy schemas for XML indexes: If this option is selected the XML schemas that is stored with each Edit Template is copied. Normally if your site is based on the EPT technology you should always select this option.
  • Copy xml-index data and definitions: This option will dumpt the content of the entire Content Studio XML index. A large site with a large amount of XML indexed documents can create a vast amount of indexed data that can increase the time of the dumping process and the installation time. Normally if your site is based on the EPT technology you should always set this option.
  • Optimize installation for full-text index destination
    When this option is set a command that turns off the automatic background population of fulltext indexes during site installation and Sql server the does not have to index any documents during installation.
  • Copy Event Actions: Copies the Event Actions that has been defined on your site. For security reasons these will be disabled at the destination. After installation an administrator must manually enable every Event Action that has been defined.
  • Copy workflow definitions and usage: Workflow definitions are not always compatible with the the new location of the site and in these cases it can be more convenient to leave this option unchecked.
  • Copy subscription definitions and subscribers
    This option was added in version 5.2. When this option is selected all Subscription Services related information and subscribers. Only available when Destination compability level is Content Studio 5.2 and later.
The following objects can be exported by the Site Exporter:
Exported object
Object Remarks
Units Always including all properties, except for the system unit
Categories Always including all properties, except for system categories
Documents Always, except for system documents (id < 1000).
MLC definitions Always
Edit template xml schemas Optional
XML index, definitions and content Optional
Workflow definitions and usages Optional
Event actions Optional
Settings Always but limited to StartID, IE_Style, OT_Style, MetaData, EmptyFileContent, InfoURL
Subscription definitions and subscribers Optional (available in version 5.2 and later)
The following objects are not exported
  • Document revisions and queues
  • Document history
  • User information for documents like created by or modified by
  • Notifications and personal mailboxes
  • Registered users and user information
  • Registered groups
  • Security descriptors and permissions
  • User defined group rights for built in groups
  • Workflow status data and logs
  • PDF queues and logs
  • PDF archive information
  • Error logs
  • Settings, except for those listed earlier
  • Document usage statistics