Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
stonebreaker
Yak Posting Veteran
92 Posts |
Posted - 2009-11-05 : 09:06:14
|
My boss has implemented a bi-weekly presentation meeting with the development team. Each of us will give a short lecture on a topic of our choice. I was wondering if anyone had a suggestion for a 5-10 minute topic I could lecture on for developers familiar with SQL code. |
|
Ifor
Aged Yak Warrior
700 Posts |
Posted - 2009-11-05 : 09:25:34
|
Maybe the pitfalls of T-SQL UPDATE FROM Statement:http://sqlblog.com/blogs/hugo_kornelis/archive/2008/03/10/lets-deprecate-update-from.aspx |
 |
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2009-11-05 : 10:35:54
|
or the pitfalls of "no where clause" in a delete statement!table-scans v index-seeks.cursors-be-damned |
 |
|
stonebreaker
Yak Posting Veteran
92 Posts |
Posted - 2009-11-05 : 14:35:40
|
I never knew the UPDATE FROM clause was proprietary to microsoft. |
 |
|
robvolk
Most Valuable Yak
15732 Posts |
|
Ifor
Aged Yak Warrior
700 Posts |
Posted - 2009-11-06 : 06:00:16
|
quote: Originally posted by stonebreaker I never knew the UPDATE FROM clause was proprietary to microsoft.
The main thing to stress to developers is when a JOIN is used that produces a one to many relationship the row that gets updated is non-deterministic. This can cause all sorts of 'random' bugs in production systems. (ie They have to make sure that JOINs in UPDATE FROM are one to one or one to zero.) If you are using SQL2008 then using MERGE ensures this happens. |
 |
|
|
|
|