2007-01-22
1,775 reads
2007-01-22
1,775 reads
As a SQL Server DBA you should know that your code is stored in syscomments by default. While most DBAs use version control systems, there are times you might want to look through the code on the server for comparison purposes. Robert Cary brings us an article on how you can do this in 2000 and 2005.
2008-01-07 (first published: 2007-01-22)
8,419 reads
2007-01-19
1,256 reads
2007-01-16
1,458 reads
In this presentation Brian shows you some of the new features in SQL Server 2005 SP2. Then, he demos briefly how to install SP2 and some of the small quirks around the installation.
2007-01-11
2,926 reads
If business today is data, then the entire enterprise is in the capable hands of you, the SQL Server DBA. Before you panic, check out Grant's detailed dissection of SQL 2005 backup and recovery regimes.
2007-01-10
3,302 reads
2007-01-09
1,304 reads
Service Pack 2 for SQL Server 2005 is not quite here, but Wayne Fillis brings us a look at what you can expect if you install the CTP version that is available now.
2008-01-08 (first published: 2007-01-09)
11,448 reads
2007-01-08
1,249 reads
2007-01-03
1,356 reads
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