Steve Jones - SSC Editor (1/20/2011)
This is a presentation that I have been working on and evolving at a few user groups. Is this abstract ok?
Abstract: This presentation looks at a number of common mistakes that people make in SQL Server. There are edge cases where these might not apply, but for the most part, these are mistakes that you do not want to repeat as you are building applications on the SQL Server platform.
The basic agenda:
* SELECT *
* Shrinking databases
* GUID as a Clustered Key
* Functions in the WHERE Clause
* IS NULL
* Multi-row triggers
* Indexing all Columns
* SA Account Usage
Short and sweet... that's nice. Knowing the speaker, I'd go. Not knowing the speaker, I'd select it as something that should be included in a conference (if it were my vote) and then I'd have to do like I do with everyone else... find out what else is in the time slot and make a decision from there.
If it were me, I'd write the abstract as follows (BOLD shows the changes)...
This presentation looks at a number of common mistakes that people make in SQL Server and how to correct those mistakes
. There are edge cases where these might not apply, but for the most part, these are mistakes that you
do not don't
as you are building applications on the SQL Server platform.
As a side bar, I still don't understand why people refuse to use contractions in their descriptions, articles, and elsewhere.
Of course, all of that is an "opinion" and we know how those are. :-D
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs