Sometimes the problems aren't your code. Here a few places where re-examining your assumptions can help improve software development.
I’ve been a fan of sequences ever since they were added in SQL Server 2012. Prior to that, developers had a choice of IDENTITY columns or a roll-your-own table mechanism.
There’s a saying in security circles: the weakest link isn’t the lock on the front door but the spare key under the mat. This past week gave us two vivid, simultaneous demonstrations of that principle, and if you’re building anything in the AI space right now, both deserve your full attention. The Mythos Leak and […]
A company has both a server without a password and live data in test environments. Not a good situation.
Learn about migrating SSRS reports to Power BI Report Server in SQL 2025
This guide explains how IDENTITY columns and SEQUENCE objects differ in SQL Server, and how you might decide which one is appropriate for a given design.
In this third level of the Stairway, we examine how to store your encryption certificate in the Azure Key Vault.
Learn how to remove TDE from a database and return it to a normal state.
In the second level of the stairway to TDE, we examine how you can restore your databases on another instance after moving the encryption certificate.
By alevyinroc
Ten years (and a couple jobs) ago, I wrote about naming default constraints to...
By Steve Jones
We have multiple teams (8) working on Redgate Monitor. Some work on the Standard...
By HeyMo0sh
Learning any kind of theory is easy, but adapting FinOps and watching it rescue...
Comments posted to this topic are about the item The day-to-day pressures of a...
Comments posted to this topic are about the item The Problem Isn't Always Your...
Comments posted to this topic are about the item Identity Defaults
What happens when I run this code?
CREATE TABLE dbo.IdentityTest
(
id int IDENTITY(10) PRIMARY KEY,
somevalue VARCHAR(20)
)
GO
See possible answers