Retrieving logs takes forever
Takes forever to pull logs.
The logging is based on msg_id, msg_ts, msg fields
It takes forever to retrieve logs from this table.
Explain plan suggests it does a full table scan on mylog table which contain log entries since Jul-2012, having 500,000 entries.
There are no partitions or index available on the table.
It is not possible to add partitions now as all programs in my project will have to be modified so that the partition key is also sent by mypkg.write_log(v_msg,v_da
Index on msg filed does not seem to be a proper way since there is no key field in it just text.
How can i pull the logs faster, what are my alternatives.
The logging is based on msg_id, msg_ts, msg fields
It takes forever to retrieve logs from this table.
Explain plan suggests it does a full table scan on mylog table which contain log entries since Jul-2012, having 500,000 entries.
There are no partitions or index available on the table.
It is not possible to add partitions now as all programs in my project will have to be modified so that the partition key is also sent by mypkg.write_log(v_msg,v_da
Index on msg filed does not seem to be a proper way since there is no key field in it just text.
How can i pull the logs faster, what are my alternatives.
Who is Participating?
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
-
Course of the Month5 days, 19 hours left to enrollMonitoring and Operating a Private Cloud with System Center 2012 R2 273 lessons
Most likely a cheaper alternative would be to add an index and/or a partitioning scheme of some kind to this table. If it doesn't include a date column at all now, this could also include adding a date column with a name something like "date_created" and a trigger to populate the new date column.