I agree that you should be running your SQL through VE during development.

However, it's likely you should also be running it through VE on production
prior to actual deployment.

I've yet to work at a shop where the development system was the same size
as production; most times it doesn't even have all the data that production
has. Even if DVP was the same size and had the same data, the workloads
would be quite different.

Given the way the SQE works, something that performs well in DVP can go on
and perform poorly in PDN.


On Fri, Oct 31, 2014 at 8:41 AM, <MichaelQuigley@xxxxxxxxxx> wrote:

As for Visual Explain, I rarely let something go to production without
running it through visual explain. Authority would only be an issue in a
production environment.

<soapbox warning!>

Going to SQL doesn't change the requirements for a separate development
environment where programmers have authority to do anything needed to
fully test and optimize a system. It seems that some folks think SQL is a
substitute for it. I think such logic is foolish and lacking full thought.

</soapbox warning!>

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.