Good presentations include stories. The best presenters illustrate their points with the use of stories, most often personal ones. The easiest way to explain complicated ideas is through examples or by sharing a story that underscores the point. Stories are easy to remember for your audience. If you want your audience to remember your content, then find a way to make it relevant and memorable to them. You should try to come up with good, short, interesting stories or examples to support your major addition, it is useful to think of your entire 30 minute presentation as an opportunity to “tell a story.” Good stories have interesting, clear beginnings, provocative, engaging content in the middle, and a clear, logical conclusion. I have seen pretty good (though not great) presentations that had very average delivery and average graphics, but were relatively effective because the speaker told relevant stories in a clear, concise manner to support his points. Rambling streams of consciousness will not get it done; audiences need to hear (and see) your points illustrated.
KiUserExceptionDispatcher is the routine responsible for calling the user mode portion of the SEH dispatcher. When an exception occurs, and it is an exception that would generate an SEH event, the kernel checks to see whether the exception occurred while running user mode code. If so, then the kernel alters the trap frame on the stack, such that when the kernel returns from the interrupt or exception, execution resumes at KiUserExceptionDispatcher instead of the instruction that raised the fault. The kernel also arranges for several parameters (a PCONTEXT and a PEXCEPTION_RECORD) that describe the state of the machine when the exception occurred to be passed to KiUserExceptionDispatcher upon the return to user mode. (This model of changing the return address for a return from kernel mode to user mode is a common idiom in the Windows kernel for several user mode event notification mechanisms.)
SHOW VIEWS lists all the views in the current database (or the one explicitly named using the IN or FROM clause) with names matching the optional regular expression. Wildcards in the regular expression can only be '*' for any character(s) or '|' for a choice. Examples are 'page_view', 'page_v*', '*view|page*', all which will match the 'page_view' view. Matching views are listed in alphabetical order. It is not an error if no matching views are found in metastore. If no regular expression is given then all views in the selected database are listed.