Tell Me What You Need - iPod
Ever worked on a software project where you didn't get all the requirements? One where the functions and features change in midstream? Steve Jones comments on some possibilities on why this happens.
Ever worked on a software project where you didn't get all the requirements? One where the functions and features change in midstream? Steve Jones comments on some possibilities on why this happens.
Ever worked on a software project where you didn't get all the requirements? One where the functions and features change in midstream? Steve Jones comments on some possibilities on why this happens.
SQL Server 2008, Katmai, apparently won't ship in Q2. Looks like a Q3 possibility now.
Dealing with NULL data is something that often confuses new SQL Server developers, but even experienced DBAs might not understand all the intricacies of NULL operations. In a follow up to his highly acclaimed Four Rules of Null article, Michael Coles brings us a few new
tricks with NULLs.
Updated: Jan 2008. One of the big changes in SQL Server 2005 is the integration of the CLR into the relational engine itself. This is probably the biggest reason for the delays in completing the product and it is a controversial decision. Steve Jones spends a few minutes looking at the pros and cons of having the CLR integrated and possible implications for DBAs.
This white paper describes how application developers can incorporate data quality into their Microsoft SQL Server 2005 Integration Services solutions.
Part one of this series illustrates how to enable Change Data Capture on a database, and on a table, and how to keep track of Data Definition Language changes on a table.
In order to support multiple environments, a number of choices, not readily apparent, need to be made. This article outlines one approach that is working.
By Steve Jones
I come to Heathrow often. Today is likely somewhere close to 60 trips to...
By Brian Kelley
If your organization is spending money, then meaningful results are a must. Pen testing...
By HeyMo0sh
In my experience, FinOps success has never been just about tools or dashboards. It...
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers