|
I have seen this before. Users creates a query and does the join wrong and suddenly you have millions of joins instead of one. For myself, that is why I never let users run queries directly against tables. My preferred way is to create a stored procedure to get the data for them or at the minimum creates views that have the joins they need pre-created so they don't do this kind of stuff. Crystal Enterprises has this built in. Anyway, my two cents. Anything that is for production should go through a stored procedure. Looks like folks might have some ideas on how to prevent run away jobs.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
