2018-02-19 (first published: 2018-02-07)
931 reads
2018-02-19 (first published: 2018-02-07)
931 reads
There are several obvious problems with poor SQL Coding habits. It can make code difficult to maintain, or can confuse your team colleagues. It can make refactoring a chore or make testing difficult. The most serious problem is poor performance. You can write SQL that looks beautiful but performs sluggishly, or interferes with other threads. A busy database developer adopts good habits so as to avoid staring at execution plans. Rob Sheldon gives some examples.
2017-10-05
6,056 reads
Technical debt is a real problem in database development, where corners have been cut in the rush to keep to dates. The result may work but the problems are in the details: such things as inconsistent naming of objects, or of defining columns; sloppy use of data types, archaic syntax or obsolete system functions. With databases, technical debt is even harder to pay back. Robert Sheldon explains how and why you can get it right first time instead.
2017-07-25
5,860 reads
TSQL Code must work properly and efficiently. That's not enough though. Unless you are working alone, have perfect memory and plan to never change job, then you need to comment and document your code, it must be inherently readable, well laid out, use informative and obvious names, and it must be robust and resilient; written defensively. It must not rely on deprecated features of SQL Server, or assume particular database settings. Robert Sheldon starts a series of articles that explains the basics.
2017-07-05
7,732 reads
Prefer tabs but your teammates use spaces? That's not a problem with the brand new formatting options in SQL Prompt. It's now possible to customize, save, and share multiple styles that you can then quickly switch between when working. Here's how it works, and how to get set up.
2017-06-06
4,008 reads
Louis Davidson shows how to save a defined SQL formatting style as a shareable template that you can quickly share with your coworkers.
2017-05-02
5,605 reads
The way that you format T-SQL code can affect the productivity of the people who have to subsequently maintain your work. It is never a good experience to see SQL Code, cry out “Who the devil wrote this code?”, and then realise that it was you. Grant gives some examples of bad formatting and explains why you should never check-in badly-formatted SQL code.
2016-11-29
6,105 reads
When you're formatting SQL Code, your objective is to make the code as easy to read with understanding as is possible, in a way that errors stand out. The extra time it takes to write code in an accessible way is far less than the time saved by the poor soul in the future, possibly yourself, when maintaining or enhancing the code. There isn't a single 'best practice, but the general principles, such as being consistent, are well-established. Joe Celko gives his take on a controversial topic.
2016-08-30
8,612 reads
A quick tip for using a combination of block and line comments to test CTEs
2014-11-10
7,354 reads
We use a tally table to find the appropriate denominator for a given decimal part of a number.
2014-04-29 (first published: 2014-04-07)
1,001 reads
By Steve Jones
I can’t remember how I heard about Small Data SF 2024, but it caught...
By Steve Jones
moledro – n. a feeling of resonant connection with an author or artist you’ll...
By Arun Sirpal
Let’s go back to data platforms today and I want to talk about a...
Comments posted to this topic are about the item 7 sept, scheduled book
Comments posted to this topic are about the item 7 sept, schedlued article
Comments posted to this topic are about the item 6 sept, published book
Azure Data Lake Storage Gen 2 is built on ...?
See possible answers