Re: identify bad sqls running over db link

Just because the statistics on the remote database have been updated does not mean that some of your queries that reference objects on the remote database are going to start experiencing new performance problems. You could just wait to see if any problems are reported. Even if a problem is reported unless you have documentation on past plans and/or performance you do not know if the problem is really related to a possible plan change or the query was always slow and you are just now being informed.

If you want to take a pro-active approach you can find all the remote sql being issued from your database and try to time it on a query by query type basis, but without past knowledge of run times it can be difficult to determine if a 30 second run time is normal or a new problem.

Here is an article on finding distributed SQL: How do I find distributed queries / transactions (either issued from or connecting to this instance)?
http://www.jlcomp.demon.co.uk/faq/find_dist.html

HTH -- Mark D Powell -- Received on Mon Apr 03 2006 - 09:26:22 CDT