• Replies 15 replies
  • Subscribers 338 subscribers
  • Views 262 views
  • Users 0 members are here
Related

Test Database

Former Member
Former Member $organization

I am curious, would there be a sample or 'test' database of Tess available for our developers to work with? It would be nice to have a small data set to work with rather than our large 'real' dataset. Are there other organizations that have created there own sample dataset for development?

Thanks!

Stuart Cotts

OSF

  • Former Member
    Former Member $organization

    Hi Stuart

    I think most, if not all, of us work from Test databases that are just copies of Live.

    I've occasionally tossed around the idea of writing a script that would strip (for example) old performance data out of the db when Test is refreshed from Live, mostly to save some space, since ours is begining to get a bit awkwardly large, but the work required to do that, and then to prove that what's been stripped out doesn't materially affect the system doesn't seem justified. (What if the size of T_PERF becomes a critical performance issue for your code, and you've been developing against a shrunken table? What if your script has inadvertently introduced referential integrity issues?... and so on...)

    We run three test environments, and since we work in a consortium context, we have five independent org websites, each with its own development team, plus a variety of people doing custom work, pointing their dev at one or other environment. The size of the db doesn't seem to introduce any problems for developers, and I don't know that I can see much advantage in providing any of those in a cut-down version, to justify the resource commitment (and potential for confusion).

    Ken

     

  • Former Member
    Former Member $organization in reply to Former Member

    I realize this is an old thread.  Has anyone in Tessitura Land created scripts to anonymize your test data?  We need to be able to face our test/qa server out toward the public for testing.  We want it to contain the same amount of data our LIVE server contains, but we wouldn't want to expose any info about our patrons in so doing.  Wondering if anyone else has worked on this issue. 

  • $organization in reply to Former Member

    Hi Karen,

    We've not done what you are suggesting, but could you use some security to minimize the data which is visible to the web? User Groups/Control Groups/Constituencies?

    We have a bunch of records which all use the Theatre address and a series of Mr Dev Test, Mrs Finance Test etc. Could you leave your customer name but change the address to your Theatre? A name without an address, email or phone is effectively anonymous.

    Debbie

  • $organization in reply to Former Member

    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.

  • $organization in reply to Kevin Holmes

    Hi Kevin - we automate our production to test refreshes and do many of these things, but we do not do #1. I'd be interested in a copy of your script as well if possible. Thanks!

  • $organization

    Hi Kevin,

     

    We  would love to see what you’ve put together if you don’t mind. We have about ½ of the refresh scripted now and this could most definitely help speed up the process!

     

    Scott Eckner

    Cincinnati Symphony Orchestra

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of David Frederick
    Sent: Wednesday, November 30, 2016 2:10 PM
    To: Scott Eckner <SEckner@cincinnatisymphony.org>
    Subject: Re: [Tessitura Technical Forum] Test Database

     

    Hi Kevin - we automate our production to test refreshes and do many of these things, but we do not do #1. I'd be interested in a copy of your script as well if possible. Thanks!

    From: Kevin Holmes <bounce-kevinholmes9908@tessituranetwork.com>
    Sent: 11/29/2016 11:51:18 AM

    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!

  • $organization in reply to Scott Eckner

    Hi all,

    You can download our script from the link below.  I've also included some documentation to describe the settings we use.

    https://smithsonianassociates.org/k-ho/Tessitura-TEST-QA-DB-Sanitizer.zip

    If you have any questions about it, let me know!

    Kevin.

     



    [edited by: Kevin Holmes at 10:04 AM (GMT -6) on 1 Dec 2016] Fixed link to zip file
  • $organization
    Thank you Kevin!

    On 12/1/2016 10:16 AM, Kevin Holmes wrote:

    Hi all,

    You can download our script from the link below.  I've also included some documentation to describe the settings we use.

    https://smithsonianassociates.org/k-ho/Tessitura-DEV-QA-DB-Sanitizer.zip

    If you have any questions about it, let me know!

    Kevin.

     

    From: Scott Eckner <bounce-scotteckner5007@tessituranetwork.com>
    Sent: 11/30/2016 9:37:27 PM

    Hi Kevin,

     

    We  would love to see what you’ve put together if you don’t mind. We have about ½ of the refresh scripted now and this could most definitely help speed up the process!

     

    Scott Eckner

    Cincinnati Symphony Orchestra

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of David Frederick
    Sent: Wednesday, November 30, 2016 2:10 PM
    To: Scott Eckner <SEckner@cincinnatisymphony.org>
    Subject: Re: [Tessitura Technical Forum] Test Database

     

    Hi Kevin - we automate our production to test refreshes and do many of these things, but we do not do #1. I'd be interested in a copy of your script as well if possible. Thanks!

    From: Kevin Holmes <bounce-kevinholmes9908@tessituranetwork.com>
    Sent: 11/29/2016 11:51:18 AM

    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!




    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!

    cgoodwin.vcf
  • $organization

    Hi Kevin – small problem – in following the link I get a 404 error.

     

    Scott Eckner

    Cincinnati Symphony Orchestra

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Kevin Holmes
    Sent: Thursday, December 01, 2016 10:17 AM
    To: Scott Eckner <SEckner@cincinnatisymphony.org>
    Subject: RE: [Tessitura Technical Forum] Test Database

     

    Hi all,

    You can download our script from the link below.  I've also included some documentation to describe the settings we use.

    https://smithsonianassociates.org/k-ho/Tessitura-DEV-QA-DB-Sanitizer.zip

    If you have any questions about it, let me know!

    Kevin.

     

    From: Scott Eckner <bounce-scotteckner5007@tessituranetwork.com>
    Sent: 11/30/2016 9:37:27 PM

    Hi Kevin,

     

    We  would love to see what you’ve put together if you don’t mind. We have about ½ of the refresh scripted now and this could most definitely help speed up the process!

     

    Scott Eckner

    Cincinnati Symphony Orchestra

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of David Frederick
    Sent: Wednesday, November 30, 2016 2:10 PM
    To: Scott Eckner <SEckner@cincinnatisymphony.org>
    Subject: Re: [Tessitura Technical Forum] Test Database

     

    Hi Kevin - we automate our production to test refreshes and do many of these things, but we do not do #1. I'd be interested in a copy of your script as well if possible. Thanks!

    From: Kevin Holmes <bounce-kevinholmes9908@tessituranetwork.com>
    Sent: 11/29/2016 11:51:18 AM

    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!




    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!

  • $organization

    Hi Scott,

     

    I corrected that already in the post but I guess it didn’t send out the update!

     

    Correct link:
    https://smithsonianassociates.org/k-ho/Tessitura-TEST-QA-DB-Sanitizer.zip

     

    Kevin.

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Scott Eckner
    Sent: Thursday, December 1, 2016 10:33 AM
    To: Holmes, Kevin <HolmeKe@si.edu>
    Subject: RE: [Tessitura Technical Forum] Test Database

     

    Hi Kevin – small problem – in following the link I get a 404 error.

     

    Scott Eckner

    Cincinnati Symphony Orchestra

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Kevin Holmes
    Sent: Thursday, December 01, 2016 10:17 AM
    To: Scott Eckner <SEckner@cincinnatisymphony.org>
    Subject: RE: [Tessitura Technical Forum] Test Database

     

    Hi all,

    You can download our script from the link below.  I've also included some documentation to describe the settings we use.

    https://smithsonianassociates.org/k-ho/Tessitura-DEV-QA-DB-Sanitizer.zip

    If you have any questions about it, let me know!

    Kevin.

     

    From: Scott Eckner <bounce-scotteckner5007@tessituranetwork.com>
    Sent: 11/30/2016 9:37:27 PM

    Hi Kevin,

     

    We  would love to see what you’ve put together if you don’t mind. We have about ½ of the refresh scripted now and this could most definitely help speed up the process!

     

    Scott Eckner

    Cincinnati Symphony Orchestra

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of David Frederick
    Sent: Wednesday, November 30, 2016 2:10 PM
    To: Scott Eckner <SEckner@cincinnatisymphony.org>
    Subject: Re: [Tessitura Technical Forum] Test Database

     

    Hi Kevin - we automate our production to test refreshes and do many of these things, but we do not do #1. I'd be interested in a copy of your script as well if possible. Thanks!

    From: Kevin Holmes <bounce-kevinholmes9908@tessituranetwork.com>
    Sent: 11/29/2016 11:51:18 AM

    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!




    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!




    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!

  • $organization
    Hello Kevin,

    I tried to open the link, I am getting error.



    Thank You,
    Malek

    On 12/1/2016 10:17 AM, Kevin Holmes wrote:

    Hi all,

    You can download our script from the link below.  I've also included some documentation to describe the settings we use.

    https://smithsonianassociates.org/k-ho/Tessitura-DEV-QA-DB-Sanitizer.zip

    If you have any questions about it, let me know!

    Kevin.

     

    From: Scott Eckner <bounce-scotteckner5007@tessituranetwork.com>
    Sent: 11/30/2016 9:37:27 PM

    Hi Kevin,

     

    We  would love to see what you’ve put together if you don’t mind. We have about ½ of the refresh scripted now and this could most definitely help speed up the process!

     

    Scott Eckner

    Cincinnati Symphony Orchestra

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of David Frederick
    Sent: Wednesday, November 30, 2016 2:10 PM
    To: Scott Eckner <SEckner@cincinnatisymphony.org>
    Subject: Re: [Tessitura Technical Forum] Test Database

     

    Hi Kevin - we automate our production to test refreshes and do many of these things, but we do not do #1. I'd be interested in a copy of your script as well if possible. Thanks!

    From: Kevin Holmes <bounce-kevinholmes9908@tessituranetwork.com>
    Sent: 11/29/2016 11:51:18 AM

    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!




    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!

  • $organization

    Perfect! Thank you!!

     

    Scott Eckner

    Cincinnati Symphony Orchestra

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Kevin Holmes
    Sent: Thursday, December 01, 2016 10:44 AM
    To: Scott Eckner <SEckner@cincinnatisymphony.org>
    Subject: RE: [Tessitura Technical Forum] Test Database

     

    Hi Scott,

     

    I corrected that already in the post but I guess it didn’t send out the update!

     

    Correct link:
    https://smithsonianassociates.org/k-ho/Tessitura-TEST-QA-DB-Sanitizer.zip

     

    Kevin.

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Scott Eckner
    Sent: Thursday, December 1, 2016 10:33 AM
    To: Holmes, Kevin <HolmeKe@si.edu>
    Subject: RE: [Tessitura Technical Forum] Test Database

     

    Hi Kevin – small problem – in following the link I get a 404 error.

     

    Scott Eckner

    Cincinnati Symphony Orchestra

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Kevin Holmes
    Sent: Thursday, December 01, 2016 10:17 AM
    To: Scott Eckner <SEckner@cincinnatisymphony.org>
    Subject: RE: [Tessitura Technical Forum] Test Database

     

    Hi all,

    You can download our script from the link below.  I've also included some documentation to describe the settings we use.

    https://smithsonianassociates.org/k-ho/Tessitura-DEV-QA-DB-Sanitizer.zip

    If you have any questions about it, let me know!

    Kevin.

     

    From: Scott Eckner <bounce-scotteckner5007@tessituranetwork.com>
    Sent: 11/30/2016 9:37:27 PM

    Hi Kevin,

     

    We  would love to see what you’ve put together if you don’t mind. We have about ½ of the refresh scripted now and this could most definitely help speed up the process!

     

    Scott Eckner

    Cincinnati Symphony Orchestra

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of David Frederick
    Sent: Wednesday, November 30, 2016 2:10 PM
    To: Scott Eckner <SEckner@cincinnatisymphony.org>
    Subject: Re: [Tessitura Technical Forum] Test Database

     

    Hi Kevin - we automate our production to test refreshes and do many of these things, but we do not do #1. I'd be interested in a copy of your script as well if possible. Thanks!

    From: Kevin Holmes <bounce-kevinholmes9908@tessituranetwork.com>
    Sent: 11/29/2016 11:51:18 AM

    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!




    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!




    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!




    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!

  • $organization
    Hello Kevin,
    I have downloaded the file.

    Thank You,
    Malek

    On 12/1/2016 10:44 AM, Kevin Holmes wrote:

    Hi Scott,

     

    I corrected that already in the post but I guess it didn’t send out the update!

     

    Correct link:
    https://smithsonianassociates.org/k-ho/Tessitura-TEST-QA-DB-Sanitizer.zip

     

    Kevin.

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Scott Eckner
    Sent: Thursday, December 1, 2016 10:33 AM
    To: Holmes, Kevin <HolmeKe@si.edu>
    Subject: RE: [Tessitura Technical Forum] Test Database

     

    Hi Kevin – small problem – in following the link I get a 404 error.

     

    Scott Eckner

    Cincinnati Symphony Orchestra

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Kevin Holmes
    Sent: Thursday, December 01, 2016 10:17 AM
    To: Scott Eckner <SEckner@cincinnatisymphony.org>
    Subject: RE: [Tessitura Technical Forum] Test Database

     

    Hi all,

    You can download our script from the link below.  I've also included some documentation to describe the settings we use.

    https://smithsonianassociates.org/k-ho/Tessitura-DEV-QA-DB-Sanitizer.zip

    If you have any questions about it, let me know!

    Kevin.

     

    From: Scott Eckner <bounce-scotteckner5007@tessituranetwork.com>
    Sent: 11/30/2016 9:37:27 PM

    Hi Kevin,

     

    We  would love to see what you’ve put together if you don’t mind. We have about ½ of the refresh scripted now and this could most definitely help speed up the process!

     

    Scott Eckner

    Cincinnati Symphony Orchestra

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of David Frederick
    Sent: Wednesday, November 30, 2016 2:10 PM
    To: Scott Eckner <SEckner@cincinnatisymphony.org>
    Subject: Re: [Tessitura Technical Forum] Test Database

     

    Hi Kevin - we automate our production to test refreshes and do many of these things, but we do not do #1. I'd be interested in a copy of your script as well if possible. Thanks!

    From: Kevin Holmes <bounce-kevinholmes9908@tessituranetwork.com>
    Sent: 11/29/2016 11:51:18 AM

    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!




    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!




    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!




    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!

  • $organization

    Reviving an old thread. Anyone have this script below or a compact test database?