![]() ![]() #BackToBasics : Common Table Expressions (CTEs) Performance Surprises and Assumptions : DATEADD() #BackToBasics : An Updated "Kitchen Sink" Example Pattern Matching : More Fun When I Was a Kid #BackToBasics : Why I use lower case for data type names (now) Top 5 Reasons for Wrong Results in SQL ServerĬan comments hamper stored procedure performance? Performance Surprises and Assumptions : GROUP BY vs. One way to get an index seek for a leading %wildcard Harmful, Pervasive SQL Server Performance Myths Safeguard to Avoid Costly Mistakes for UPDATE or DELETE Statements in SSMS Performance Myths : Oversizing string columns T-SQL Tuesday #104: Code I Would Hate to Live Withoutĭo tabs vs. Use Caution with SQL Server's MERGE Statementīe Careful with Key Order in Missing Index Recommendations Making a more reliable and flexible sp_MSforeachdb Improve Performance in SQL Server 2019 with Scalar UDF InliningĮxecute a Command in the Context of Each Database Part 2Įxecute a Command in the Context of Each Database using sp_ineachdb Using T-SQL to find events that overlap (or don't) in SQL Server Make SQL Server DMV Queries Backward Compatibleįour ways to improve scalar function performance NOLOCK Anomalies, Issues and Inconsistenciesįive Things I Wish I Knew When I Started My SQL Server Career How to Alter User Defined Table Type in SQL Serverįour SQL Server Syntax Rules I Always Follow Use caution with sys.dm_db_database_page_allocationsīad Habits to Kick : avoiding the schema prefix Video : Using BETWEEN for date range queriesĬreating a date dimension or calendar table in SQL Server Video : Datetime shorthand (and other tricks) How SQL Server handles the date format YYYY-MM-DDĭeprecated features, part 1 : sysprocessesīad Habits to Kick : relying on undocumented behavior Yes, data type names can still be case sensitiveįinding problematic NOLOCK patterns – Part 4įinding problematic NOLOCK patterns – Part 3įinding problematic NOLOCK patterns – Part 2įinding problematic NOLOCK patterns – Part 1ĭeprecated features, part 3 : text / ntext / imageĭeprecated features, part 2 : SQL Server Profiler Why I always start CTEs with a statement terminatorįORMAT is a convenient but expensive function, part 2įORMAT is a convenient but expensive function, part 1 T-SQL Tuesday #151 : Controversial Coding Conventions Why shouldn't I create 15,000 partitions in advance? T-SQL Tuesday #152 : Soapboxing (on leading commas) T-SQL Tuesday #154 : SQL Server 2022 (anti-pattern XE) One use case for NOT using schema prefixesįind 40 Problems in this Stored Procedure Not all are explicitly framed as a "bad habit," but they do all present things I wish I observed less often. Here is an ongoing list of articles that I consider to be along these lines – eradicating bad habits or at least promoting best practices. Download my latest materials from NESQL, (~ 1 MB).Download my latest materials from DBAVUG, (~ 1 MB).Often users just don't realize these things are bad or that there is a better way. ![]() Going back more than a decade, I've been writing and presenting about what I call "bad habits" – typically lazy shortcuts or sub-optimal ways to do things in SQL Server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |