You’re a C# or Java developer building an application that stores data in Microsoft SQL Server, and you want to avoid common pitfalls that will cause you scalability problems down the road.
In this session from my live stream, you’ll learn why you probably want to avoid triggers, SELECT *, user-defined functions, dynamic SQL, big datatypes, heaps, storing binaries in the database, old indexes, TempDB, and SQL Server’s v1 features:
This slide deck is a decade old: I wrote it back in 2010, but I’m revisiting it now to see what’s changed. I’m kinda surprised at how much I still agree with a decade later! My feelings have changed about a lot of SQL Server tactics, but 9 out of 10 of these are still a problem.
Wanna see more of this? Every Saturday & Sunday morning from 9AM-11AM Eastern (iCal), you can catch me on my Twitch, YouTube, or Facebook channels.
3 Comments. Leave new
Well you’ve eliminated a good majority of items that are used through out sql programming.
While functions aren’t always bad that can provide a way to retrieve data in a much more efficient way as long as they’re not repetitive.
While I’m no superstar with sql I have been developing since 1997.
Lisa – uh oh, I’ve got some terrible news. https://www.brentozar.com/archive/2019/05/user-defined-scalar-functions-suck-even-when-they-dont-access-data/
Great presentation – I get a 10/10 for the things I have been preaching for more than a decade to more junior developers. Amazing how in line we are. I would add #11 the gotcha for Entity Framework – there is no bulk update support. So juniors might use EF and not realize they are sending many more update statements than they realize.