cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
941
Views
0
Helpful
11
Replies

Archiving Strategy for Request Center

Archiving Strategy for Request Center

Our RC tablespace is now over 8 gig and we're interested in any archiving strategies that may exist.  Performance is not an issue, but when it come time to upgrade it makes for an extended process.  Also how is this done without impacting the DATAMART content.

11 Replies 11

Song Bac Toh
Level 1
Level 1

newScale is introducing incremental ETL for the datamart with the 2008 release (later this year). 

Emir is right that you can then reduce the size of your RC (transactional) database while still retrieving some historical information from the datamart.  This functionality will be available after upgrade to 2008.

Emir AmEx (9.1)
Level 1
Level 1

To answer your DataMart question: nS has started doing Deltas nowadays (not sure since which version) so you would have to upgrade to that before you can do archiving ...

I was just going to post about this actually... I'm interested in everyone's archiving of the RequestCenter database (not Datamart).  Our database, with attachments, is pretty large, well over 20 Gb.

We're moving to a custom attachment solution which will slow the rate of growth down significantly, but I'm interested in how people are archiving or managing their Databases:

- Do you use the purge script and erase old reqs?

- Do you delete ServiceLink messages after a certain age?

-

Is any of the 8 gig ServiceLink messages? NCC has two scripts that will delete ServiceLink messages for tasks that have been completed more than 14 days ago.  Have you checked the size of the XtrMessage table?

Ant,

We submitted an enhancement request years ago for a archiving feature...still have not seen anything on the roadmap as of yet.   Our DB is 35GB+

Angelo

Hi Angelo,

Yep, ours just passed 40 Gb when I checked more recently!  Some kind of formal 'product-ised' archiving feature would be awesome.

Cheers,

Ant

There are 2, and soon to be 3, methods available for reducing the size of your DB:

Requisition Purge Utility
This utility is freely available to all customers starting with newScale 2008.1. The same utility applies to 2008.2, 2008.3 and 9.1. The documentation and utility are provided with the software.
 
ServiceLink Purge Utility
This utility is freely available to all customers starting with 2008.1. The same utility applies to 2008.2, 2008.3 and

Howdy Ed,

Thanks for the info, the BEEE clean up looks good also; are there any estimates on the kind of space recovered using that process?  We're looking forward to it.

With regards to a more formal Archiving process, should we submit an enhancement request for this?  To submit one, do we need to propose a strategy/feature or is it something we can leave up to Product Management?

Cheers,

Ant

Hi Ant!

Regarding the BEEE cleanup, our development team has tested it on seveal customer DBs and provided me with the following:

Large Customer DB
Original Size: 170GB
After ServiceLink cleanup: 128GB
After BEEE cleanup: 96GB

The BEEE cleanup will result anywhere between 15% to 40% disk space reduction, depending on workflow complexity and the ratio between open and closed requisitions (the more requisitions that are closed, the more data will be removed).<

Ed, The situation that Fred has stated is the same issue that I have in that I have different services that need to be stored for various number of years.  The biggest challenge is that we also have application teams that have business requirements that range from 1 to 13 years that the data needs to be archived for audit purposes. 

Fred Pitman
Level 1
Level 1

Ed, regarding your request for requirements: the thing that is critical to us is that we be able to precisely control what is archived and what is preserved; primarily by Service ID and by Date Range. For example, we may only keep our Telephone Install work orders for a year, but keep PC orders for three years and keep Accounts Payable Access transactions available for five years for audit trail purposes.

Requisition Status would be another key. Generally, we would only be archiving Completed and C

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: