We want to always run Query Statistics so that we can better manage queries. Specifically, we want to identify:

1) which queries are rarely run or haven't been run in a long time - and perhaps delete them

2) which are run most frequently or take a long time to run - and perhaps tune them for better performance

We turned on query statistics, but we have several queries that run upon login for students, and when we had heavy student traffic, Query Statistics was overwhelmed, and slowed our system dramatically, so we've turned it off since then.

I posted a PeopleSoft Idea to improve Query Statistics Performance, and got some great feedback, though no activity from Oracle. I would much appreciate more upvotes and comments.

We want to always run Query Statistics so that we can better manage queries. Specifically, we want to identify:

1) which queries are rarely run or haven't been run in a long time - and perhaps delete them

2) which are run most frequently or take a long time to run - and perhaps tune them for better performance

We turned on query statistics, but we have several queries that run upon login for students, and when we had heavy student traffic, Query Statistics was overwhelmed, and slowed our system dramatically, so we've turned it off since then.

I posted a PeopleSoft Idea to improve Query Statistics Performance, and got some great feedback, though no activity from Oracle. I would much appreciate more upvotes and comments.

We want to always run Query Statistics so that we can better manage queries. Specifically, we want to identify:

1) which queries are rarely run or haven't been run in a long time - and perhaps delete them

2) which are run most frequently or take a long time to run - and perhaps tune them for better performance

We turned on query statistics, but we have several queries that run upon login for students, and when we had heavy student traffic, Query Statistics was overwhelmed, and slowed our system dramatically, so we've turned it off since then.

I posted a PeopleSoft Idea to improve Query Statistics Performance, and got some great feedback, though no activity from Oracle. I would much appreciate more upvotes and comments.

We want to always run Query Statistics so that we can better manage queries. Specifically, we want to identify:

1) which queries are rarely run or haven't been run in a long time - and perhaps delete them

2) which are run most frequently or take a long time to run - and perhaps tune them for better performance

We turned on query statistics, but we have several queries that run upon login for students, and when we had heavy student traffic, Query Statistics was overwhelmed, and slowed our system dramatically, so we've turned it off since then.

I posted a PeopleSoft Idea to improve Query Statistics Performance, and got some great feedback, though no activity from Oracle. I would much appreciate more upvotes and comments.

We want to always run Query Statistics so that we can better manage queries. Specifically, we want to identify:

1) which queries are rarely run or haven't been run in a long time - and perhaps delete them

2) which are run most frequently or take a long time to run - and perhaps tune them for better performance

We turned on query statistics, but we have several queries that run upon login for students, and when we had heavy student traffic, Query Statistics was overwhelmed, and slowed our system dramatically, so we've turned it off since then.

I posted a PeopleSoft Idea to improve Query Statistics Performance, and got some great feedback, though no activity from Oracle. I would much appreciate more upvotes and comments.

We want to always run Query Statistics so that we can better manage queries. Specifically, we want to identify:

1) which queries are rarely run or haven't been run in a long time - and perhaps delete them

2) which are run most frequently or take a long time to run - and perhaps tune them for better performance

We turned on query statistics, but we have several queries that run upon login for students, and when we had heavy student traffic, Query Statistics was overwhelmed, and slowed our system dramatically, so we've turned it off since then.

I posted a PeopleSoft Idea to improve Query Statistics Performance, and got some great feedback, though no activity from Oracle. I would much appreciate more upvotes and comments.

We want to always run Query Statistics so that we can better manage queries. Specifically, we want to identify:

1) which queries are rarely run or haven't been run in a long time - and perhaps delete them

2) which are run most frequently or take a long time to run - and perhaps tune them for better performance

We turned on query statistics, but we have several queries that run upon login for students, and when we had heavy student traffic, Query Statistics was overwhelmed, and slowed our system dramatically, so we've turned it off since then.

I posted a PeopleSoft Idea to improve Query Statistics Performance, and got some great feedback, though no activity from Oracle. I would much appreciate more upvotes and comments.

We want to always run Query Statistics so that we can better manage queries. Specifically, we want to identify:

1) which queries are rarely run or haven't been run in a long time - and perhaps delete them

2) which are run most frequently or take a long time to run - and perhaps tune them for better performance

We turned on query statistics, but we have several queries that run upon login for students, and when we had heavy student traffic, Query Statistics was overwhelmed, and slowed our system dramatically, so we've turned it off since then.

I posted a PeopleSoft Idea to improve Query Statistics Performance, and got some great feedback, though no activity from Oracle. I would much appreciate more upvotes and comments.