Cursors are considered by many to be the bane of good T-SQL. What are the best ways to avoid iterative T-SQL and to write queries that look and perform beautifully? This first part in an ongoing series of cursor-killing handles inter-row analysis.
2015-12-18 (first published: 2014-05-27)
22,681 reads
You make an example database, like NorthWind or WidgetDev in order to test out your deployment system and the next thing you know you're worrying about constraints, backup and security. Then you add an index to the production system and feel a pang of guilt. What would the Devs say? Somehow databases take on lives of their own, populated by the lost souls of users, Developers and DBAs. Has the Redgate DLM Team's practice Forex database somehow come alive?
2015-12-18
3,479 reads
Execute these stored procedures to backup all your database daily and your transaction logs several time daily. Save space by using the overwrite feature.
2015-12-17
5,158 reads
Aaron Bertrand takes a look at the changes in store for In-Memory OLTP (the feature formerly known as "Hekaton").
2015-12-17
5,473 reads
A new article that shows how you can automate a basic function that many environments need: the backup of a production database and the restore on a development system.
2015-12-16 (first published: 2010-10-05)
16,215 reads
2015-12-16
411 reads
Understanding backup and restore processes is essential for developers and DBAs to be more confident when dealing with uncommon situations and having the ability to suggest flexible solutions related to these processes. In this article, Sergey Gigoyan answers some key questions relating to backup and restore.
2015-12-16
3,341 reads
In SQL, you can express the logic of what you want to accomplish without spelling out the details of how the database should do it. Nowhere is this more powerful than in constraints. In this introduction to Declarative SQL, Joe Celko demonstrates how you can write portable code that performs well and executes some complex logic, merely by creating unique constraints.
2015-12-15
6,149 reads
With the introduction of SQL Server 2016 you now have a new way to encrypt columns called Always Encrypted. With Always Encrypted, data is encrypted at the application layer via ADO.NET. This means you can encrypt your confidential data with your .NET application prior to the data being sent across the network to SQL Server. In this article, Greg Larson explains his experience with exploring setting up a table that stores always encrypted data.
2015-12-14
3,661 reads
Convert the rows of a SELECT statement into a predetermined number of columns.
2015-12-11 (first published: 2014-07-17)
27,194 reads
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...
By Vinay Thakur
As discussed introduction of Always Encryption blog and initial Encryption at rest as TDE...
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