Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How does writing SQL queries for reports, which often are just run once a week, once a month or some infrequent amount, differ from writing queries for web applications (or applications) which are run many times a day? If a query runs only once a month, speed and performance isn’t a big issue, correct? How about in terms of using aspects of SQL more frequently (temp tables, CTEs, etc)?
They are not different and the same considerations taken with any other query apply.
Whether speed and performance are an issue is not your decision, but that of the report users.
What happens if your monthly report query takes 3 hours, blocking several tables in the process and bringing your other applications to a halt because they don’t have access to them?