Timeline for Validate many SQL statements for correctness
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 26, 2015 at 0:02 | vote | accept | trailmax | ||
| Feb 25, 2015 at 0:12 | answer | added | Michael Green | timeline score: 1 | |
| Feb 24, 2015 at 21:42 | comment | added | LowlyDBA - John M |
That may not apply to all the reports, but that's where I'd start. SELECT 1 FROM ... might prove useful as well.
|
|
| Feb 24, 2015 at 21:41 | comment | added | trailmax |
There are many issues here, never mind the change management and other good practices. But I am where I am and I need to make this work. So you are saying add top 1 after every Select keyword?
|
|
| Feb 24, 2015 at 21:36 | comment | added | LowlyDBA - John M | The real issue here sounds like a lack of a change management system, wherein these reports should be tested in a dev environment where running them wouldn't be an issue. Alternatively you could make modified versions of the reports that only select a few rows to ensure they run. | |
| Feb 24, 2015 at 21:22 | history | asked | trailmax | CC BY-SA 3.0 |