Steps

To copy an existing site from a (source) application database into another (target) application database:
Note: Tables that do not have a primary key or any unique key will not have their data copied. These tables are skipped.
  1. Disable any replication to the source site for the duration of the copy process. Prevent users from accessing or making any changes in the source and target databases during the copy.
  2. Turn off audit logging in the target database.
  3. The CopySite utility requires a SyteLine configuration that uses valid views of the objects database. Review the target configuration and regenerate the views of the objects database:
    1. Run the Configuration Manager utility as an administrator.
    2. Select the configuration that points to the target application database.
    3. Click Edit.
    4. In the Objects Metadata tab, click Set Objects DB Specification.
    5. Specify values for the User, Password, Server and Database Name for the objects database associated with the target application database.
    6. Click OK.
      A message is displayed to indicate that views to the objects metadata database were updated in the application database.
  4. Open the CopySite utility. The CopySite utility is found on the machine where your system was installed here - C:\Program Files\CSI\Tools\CopySite.exe.
    The CopySite utility is displayed.
  5. In the Source Database section of the utility, specify:
    • SQL Server Name: This is the source server name for the site to be copied.
    • SQL Database: This is the source database name for the site to be copied.
    • Authentication: Specify either Windows Authentication or SQL Server Authentication. If you choose SQL Server Authentication, the SQL User Name becomes enabled and the SQL Password field become enabled, and you will have to specify information in those fields.
    • Site ID: This is the source site ID to copy.
    • Always On: When selected, this enables faster reconnection for clustered source servers after failover. It accomplishes this by appending “multisubnetfailover=true” and “Connect Timeout=30” to the server’s connection string. You should select this check box if your SQL Server is in an AlwaysOn Availability Group.
  6. In the Target Database section of the utility, specify:
    • SQL Server Name: This is the target server name.
    • SQL Database: This is the target database name.
    • SQL Server Time Zone: The time zone is automatically selected to match the source site’s time zone setting upon selecting a database. If you are copying a site from a different time zone, set the copied site’s time zone appropriately.
    • Authentication: Specify either Windows Authentication or SQL Server Authentication. If you choose SQL Server Authentication, the SQL User Name becomes enabled and the SQL Password field become enabled, and you will have to specify information in those fields.
    • Always On: When selected, this enables faster reconnection for clustered target servers after failover. It accomplishes this by appending “multisubnetfailover=true” and “Connect Timeout=30” to the server’s connection string.
    • Analyze Only: Select this check box to compare the two databases (source and target) to identify any problems that might occur during the copy. See for a list of possible problems to be addressed. If you select this check box, you can not also select the Delete Target Database Data check box.
    • Delete Target Database Data: Select this check box only if you want to empty the data from the specified target database. This is only necessary if you copy a site within a non-partitioned application database that contains installed, upgraded add-ons, third-party applications, or other customizations to a target application database that contains no sites, in order to create a partitioned target application database. If you select this check box, you can not also select the Analyze Only check box.
  7. Click Copy Site and then click Finish. Review the log file for analysis results.
  8. After any problems are resolved, repeat the steps above and clear Analyze Only so the copy can be performed. See for a list of the types of information that is copied, and exceptions that are not copied.
  9. Click Next and then Commit to complete the process.
  10. The utility copies replication document metadata from the source to the target only if the target database does not currently contain any replication document metadata. Otherwise, use the App Document Metadata Sync utility on the utility server to export replication document metadata from the source database and import it into the target database. In the first screen, select both the Base SyteLine and Core Access As values. In the second screen, select Replication Documents. Password parameters are copied from the source database to the target database if the target database is empty (and therefore does not include password parameters).
  11. Redefine any Full Text Indexes on tables in the target database.
  12. Verify that the site in the target database is working properly and all data was copied correctly. Then you can delete or archive the source database. Note: This step assumes that the source database contains only one site. If the source database has multiple sites, you cannot delete or archive one site from the database.
  13. After you perform this procedure, you might need to re-license the target database, depending on how the source site was originally licensed. Here are some examples where re-licensing might be required:

    • If Intranet Shared Licensing is used, the target database looks to the master site for licensing. If the master site is being moved into the target database, the target database must now be licensed.

    • Named user licensing was used at the source site, but concurrent licensing is used in the target database.

    • The source was defined as an "entity" database, but the target database currently contains only "sites" and is not licensed for "entities.”

    If on-premises, see the Infor SyteLine Licensing Administration Guide for more information about licensing setup.