What you are asking for is possible but a very large undertaking. It also relies on the person having decent SQL and Remedy ITSM skills. The suggestions from others in this post are worth considering.
I have performed the data cleanse a few times in the past and it is not a pretty job. It involves performing thorough in-depth analysis of every single form using SQL (to identify test data both for main forms and their supporting ones) and documenting what exactly will be removed and what needs to stay. Forms which have a customer facing Ticket ID (e.g. Incident, Problem, Change etc) would have their counters reset to a value of “1” in the arschema table but the rest would not. You would also need to take a full backup of the database before any data is deleted (obviously). Foundation and Configuration forms should not have any data removed. Please note that even if you did perform the above, it takes days to do. The analysis itself is probably 2-3 days. The cleansing is also a further 1-2 days. Most of it also needs to be done via the User Tool/Mid-Tier. This allows for any workflow to fire that keeps referential integrity. What you should have done, and is the recommended best practise, is to backup the database when it was ready for testing, perform testing, remediate defects, test remediations, export workflow/data, restore database, apply fixes, backup database, shake test, cancel shake test tickets, backup database, move on to next testing phase. This way you would always have had a database which contain very few tickets but all config, fixes. customisation etc. It's a little cumbersome, but it prevents the issue you are facing now. Cheers, J _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
