Hi,
We intend to write a query that will act like wireshark i.e. note down which process or program was executing at particular point of time OR which query had to wait for resources OR blocked another query OR what was the query plan etc. This query would run for 16 hours during the day and will read more than 50 million messages and would be stored in a table on day to day basis.
This is required to track if any issues was encountered or analysis for performance tuning like. for e.g. a query timeout was encountered in live environment however we could not trace the real reason.
Kindly guide for the same. Please note the query should be light weight and should not block the main transactions as time is critical factor here.
Regards,
Saumik
Let me ask... what would one of these 50 million messages actually have in it by column to actually make is useful in posthumously determining what a fault at any given time of the day was? Considering the possible number of messages, 50 million messages in a 16 hour period is way too low but, for the sake of argument, 50 million messages in 16 hours equates to 868 or so messages PER SECOND. What makes you think that you'll know which of those 868 messages was actually causing a problem?