2013-10-07
2,814 reads
T-SQL
2013-10-02
2,889 reads
2013-09-30
3,133 reads
2013-09-24
3,016 reads
2013-09-17
2,507 reads
2013-09-16
2,803 reads
2013-09-12
2,078 reads
2013-09-11
2,475 reads
2013-09-09
2,665 reads
A Hazard of Using the SQL Update Statement
If you've never encountered this quirk of the SQL UPDATE statement, you should take a look and find a simple way around it.
2015-04-06 (first published: 2013-09-09)
27,761 reads
Blogs
Monday Monitor Tips: A New Analysis Page
By Steve Jones
We have multiple teams (8) working on Redgate Monitor. Some work on the Standard...
Case Studies: Real-World Success Stories of FinOps Implementation
By HeyMo0sh
Learning any kind of theory is easy, but adapting FinOps and watching it rescue...
SQL Server Security: Always Encryption
By Vinay Thakur
As discussed introduction of Always Encryption blog and initial Encryption at rest as TDE...
Forums
The day-to-day pressures of a DBA team, and how we can work smarter with automation and AI
Comments posted to this topic are about the item The day-to-day pressures of a...
The Problem Isn't Always Your Query or Schema... Sometimes It's Hidden Assumptions
Comments posted to this topic are about the item The Problem Isn't Always Your...
Identity Defaults
Comments posted to this topic are about the item Identity Defaults
Question of the Day
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