Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

PCR does not automatically refresh Test Systems with Production Data. This is done upon request and is limited to a single data refresh per quarter. Additional requests will be considered on a case-by-case basis. Typically, Test Data refreshes will only be scheduled for a weekday Anchor_GoBack_GoBack. Alternatively, PCR will also release a schedule of available weekend dates for data refreshes, with a limited number of slots. All weekend dates are first-come-first-serve.

...


Licensed Customers of PCR-360 are responsible for all Database Administration. This includes, but is not limited to, backups, modifying database settings, and refreshing Test data with Production data.  Usually, Database Administrators prefer to deal with copying or backing up the data, so PCR does not provide this service to Licensed Customers
 
PCR does have a few requests when it comes to copying Production data to the Test database. Abiding by these requests will help avoid any potential issues caused by the data restoration.

  1. PCR would like to be informed when data is copied from Production to Test or restored from a backup.  If the version of the data in the backup, or from Production does not match the patch installed on the system, the application will not function properly.
  2. If possible, coordinate the copying of Production Data to Test with new Patch Upgrades.  This should reduce the possibility of any unforeseen issues since PCR would be installing the upgrade right after the data is copied. This allows PCR to verify everything is in order after the data transfer.

...

Refreshing Test Data Guidelines

Include Page
Refreshing Test Data Guidelines
Refreshing Test Data Guidelines