Test Database

Hi Karen,

We do that.  We refresh our dev database about once a month, so  I have a script that we run after bringing over our Production database to Dev that does the following and keeps us PCI compliant:

1. Anonymizes the constituent records;
2. Removes all constituent emails and logins, except my own and the guest account login (otherwise we create our own in dev if we need them);
3. Removes all Production audit data;
4. Removes all Production web session data;
5. Updates the IP addresses in T_DEFAULTS to the test servers;
6. Updates the title bar text to indicate it's the test environment when you're in the client;
7. Updates the pointers on any custom tabs we have;
8. Clears out all CSI's (as that also can contain PII information);
9. Fixes the database logins so that people with accounts in test can log in;
10. Compacts and takes a backup of the database;

I can also specify a "cleanse level" so that I can keep some data that would normally be removed if I need to use it for testing.  The highest level clears out even more data.

I can send it to you if you're interested in checking it out.

Kevin.

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!