Suggestions to maintain large number of workitems
Hi JazzExperts,
We have large number of workitems in our setup. As a consequnce, it takes few hours to build indices on a DB recovery or any maintenance activity.
This time is expected to increase along with the growth of the workitems. Running the indices for more than 5 hours will definitely be an impact to the production during a disaster recovery.
I'm trying to find ways to reduce the time it takes to build indices and to run the DW jobs.
I have few suggestions in mind, Please let me know if any of these will help
1) Move the old workitems to a separate project and archive that. Will building indices include the archive project even ?
2) What are the indices that need to be run in a minimum to bring up the system? ( Text indices, workitems ...)
3) Create a repository and move the unwanted workitems to another repository and maintain that separately. But this is a costly approach in terms of maintenance as it would require a dedicated hardware, administration effort and maintenance time.
Any suggestions on bringing down the time to build indices is most welcome.
We have large number of workitems in our setup. As a consequnce, it takes few hours to build indices on a DB recovery or any maintenance activity.
This time is expected to increase along with the growth of the workitems. Running the indices for more than 5 hours will definitely be an impact to the production during a disaster recovery.
I'm trying to find ways to reduce the time it takes to build indices and to run the DW jobs.
I have few suggestions in mind, Please let me know if any of these will help
1) Move the old workitems to a separate project and archive that. Will building indices include the archive project even ?
2) What are the indices that need to be run in a minimum to bring up the system? ( Text indices, workitems ...)
3) Create a repository and move the unwanted workitems to another repository and maintain that separately. But this is a costly approach in terms of maintenance as it would require a dedicated hardware, administration effort and maintenance time.
Any suggestions on bringing down the time to build indices is most welcome.
Comments
Pavithra Kasturirangan
May 14 '13, 7:04 a.m.Hi, Any suggestion to the query above will be greatly appreciated.
Millard Ellingsworth
FORUM ADMINISTRATOR / JAZZ DEVELOPER May 20 '13, 4:21 p.m.What version are you using? Is the index building a recent issue (there is a known issue with incorrect indices in 4.0.1: Technote 1620879: Upgrades to 4.0.1 create a significantly larger, incorrect index).