4 ms·
I tried analyzing execution plans for a fairly large stored procedure. I only needed to do it a few times. Everytime resulting in the DBA informing me that they
by 6DM 10y ago
I tried analyzing execution plans for a fairly large stored procedure. I only needed to do it a few times. Everytime resulting in the DBA informing me that they've already analyzed that before and it was understandable why I couldn't make any real headway.
Side note I found a free pdf for analyzing execution plans in this stackoverflow answer (toward the bottom): http://stackoverflow.com/a/7359705/834579 http://stackoverflow.com/a/7359705/834579
Would you consider logging user actions, for reporting in website, as something that should be stored else where? In one case I can think of the table had about 7 million records, but nobody seemed concerned about it.
- partycoder 10y agoIf it's just a log then you can "merge on write" (nosql) instead of "merge on read" (join),