Finding Special Characters within Character Strings

Special Characters can lead to many problems. Identifying and reporting on them can save a lot of headache down the road.

The Comeback of Migrations-Based Deployments

With database deployments, not all script-based processes are equal. Some use change scripts in a free-and-easy way, and some, which are normally called ‘migrations-based approaches’, have more discipline around them. In this article, Redgate Product Manager Elizabeth Ayer covers ‘migrations’, and shows some of the benefits that have come with new tooling which is specifically designed to assist the change script processes.

Naming Is Hard

Naming objects and variables in software can create contention in a team. While there are good conventions and standards, ultimately a team just needs to agree on something.

Exploring SQL Server 2016 Dynamic Data Masking – Part Two - Masking and Exporting Data in Existing Tables

Dynamic Data Masking allows you to obscure your confidential data column values at the database engine level for both new and existing SQL Server data. Being able to alter the definition of an existing column to add a masking rule makes it very simple to obscure your existing column values without even changing your application code.

Byte Me: Spy Where?

Performance Surprises and Assumptions: STRING_SPLIT

SQL Server 2016 RC0 introduces a new native string splitting function, STRING_SPLIT. In this article, Aaron Bertrand compares its performance to existing methods.

A SQL Server Patching Shortcut

This post on SQL Server patching illustrates a quick and simple way of safely extracting SQL Server installation files in advance of patching a SQL Server instance.

No Overtime

A new bill adds additional overtime exemptions for database professionals.

The 2015/2016 Simple-Talk Awards

Once more Simple-Talk invites its readers to vote on the top nominations for the Simple-Talk Awards. Find out who or what has been nominated for each of this year's nine categories, and cast your vote to decide the winners - voting closes tomorrow!

Code smells versus transgressions

The oddest SQL practices can be done deliberately for good reason, but are there any that are always wrong, that are so bad that that their use should be prohibited as a matter of policy?