Does anyone know if there is a way built already to
archive old 4106 data? WBAMC currently has 1184
completed 4106's and it takes over 20 minutes just to
open up the All Routes Completed tab on the Routing
Report.
There is no way to archive old 4106 data without affecting
aggregate responses.
Two questions:
1. Is there are reason your users open the "All Routes
Complete" tree? Typically, they're looking for a past 4106
that was completed and have some pieces of information. It
is infinitely more efficient to search for the criteria than pull up
a list and (manually) search for the session ID. This this
problem be resolved by changing user behavior?
2. Are there data base optimimizations (index tuning wizard)
you use to improve performance?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There is no way to archive old 4106 data without affecting
aggregate responses.
Two questions:
1. Is there are reason your users open the "All Routes
Complete" tree? Typically, they're looking for a past 4106
that was completed and have some pieces of information. It
is infinitely more efficient to search for the criteria than pull up
a list and (manually) search for the session ID. This this
problem be resolved by changing user behavior?
2. Are there data base optimimizations (index tuning wizard)
you use to improve performance?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There is no way to archive old 4106 data without affecting
aggregate responses.
Two questions:
1. Is there are reason your users open the "All Routes
Complete" tree? Typically, they're looking for a past 4106
that was completed and have some pieces of information. It
is infinitely more efficient to search for the criteria than pull up
a list and (manually) search for the session ID. This this
problem be resolved by changing user behavior?
2. Are there data base optimimizations (index tuning wizard)
you use to improve performance?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1. Honestly not sure if that is the way the users are actually
doing it, that is just the way that I knew how. I'll find out from
them to make sure how they are pulling these.
2. I don't think it's a database issue but I will check into that.
I think it's the way the records are pulled into this tree.
Pulling all of the records took 20 minutes and IE went up to
over 100MB of memory usage.
3. I was thinking yesterday that if we broke down the tree
into sections, like month or year then this would help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=97668
There is no way to archive old 4106 data without affecting
aggregate responses.
Two questions:
1. Is there are reason your users open the "All Routes
Complete" tree? Typically, they're looking for a past 4106
that was completed and have some pieces of information. It
is infinitely more efficient to search for the criteria than pull up
a list and (manually) search for the session ID. This this
problem be resolved by changing user behavior?
2. Are there data base optimimizations (index tuning wizard)
you use to improve performance?
Logged In: YES
user_id=97668
There is no way to archive old 4106 data without affecting
aggregate responses.
Two questions:
1. Is there are reason your users open the "All Routes
Complete" tree? Typically, they're looking for a past 4106
that was completed and have some pieces of information. It
is infinitely more efficient to search for the criteria than pull up
a list and (manually) search for the session ID. This this
problem be resolved by changing user behavior?
2. Are there data base optimimizations (index tuning wizard)
you use to improve performance?
Logged In: YES
user_id=97668
There is no way to archive old 4106 data without affecting
aggregate responses.
Two questions:
1. Is there are reason your users open the "All Routes
Complete" tree? Typically, they're looking for a past 4106
that was completed and have some pieces of information. It
is infinitely more efficient to search for the criteria than pull up
a list and (manually) search for the session ID. This this
problem be resolved by changing user behavior?
2. Are there data base optimimizations (index tuning wizard)
you use to improve performance?
Logged In: YES
user_id=1026167
1. Honestly not sure if that is the way the users are actually
doing it, that is just the way that I knew how. I'll find out from
them to make sure how they are pulling these.
2. I don't think it's a database issue but I will check into that.
I think it's the way the records are pulled into this tree.
Pulling all of the records took 20 minutes and IE went up to
over 100MB of memory usage.
3. I was thinking yesterday that if we broke down the tree
into sections, like month or year then this would help.