2005-06-30
1,624 reads
2005-06-30
1,624 reads
Ever do something to your SQL Server 2000 server and then realize you've just broken something major? Ever have a moment when you want to go "whoops", but really feel like crying ot running away? Steve Jones just had one of those and gives you a few things to think about when you deal with a situation like that.
2005-06-16
12,079 reads
2005-06-01
1,825 reads
Backing up SQL Server data is like many of the things we do because we figure we need to. It is good for you, like eating a good diet and getting exercise. Unfortunately, folks are often about as successful with SQL Server backups as they are with diet and exercise.
This is the first in a series of articles covering SQL Server database backup. The series starts from the very basics of why database backup is important. The question of why to backup a database can inform many other decisions.
2005-05-09
2,411 reads
2005-04-08
2,111 reads
2005-03-07
1,398 reads
2004-12-22
1,724 reads
2004-12-08
1,743 reads
Another in our series of things you should avoid at all costs. Seems silly at first, not having a detailed recovery plan for your SQL Server. Perhaps it is, but having dealt with any number of problems over the last few years, Steve Jones has some ideas why a detailed plan may not be the best thing to spend your time on.
2004-11-09
8,105 reads
Part 2 of Steve Jones' Incident Response series that looks at how you should be prepared as well as what to do when disaster strikes. Part 1 established a basic framework and part 2 dives deeper into what you might need for the next virus, hardware failure, or hurricane :(.
2004-10-11
4,938 reads
By James Serra
(This post starts a three-part series on how AI is changing the way we...
I built a free library of runnable SQL Server demos. Each reproduces a real...
By Steve Jones
I was looking over the CHOOSE() function while editing an article at SQL Server...
We're currently in Azure, however as we had a very tight migration timeline when...
I have a section of code similar to the following abstract: DECLARE @loop [int]...
Hello everyone, I am planning to implement a data purging solution that is expected...
In SQL Server 2022+, what does the ##MS_DatabaseConnector## role allow?
See possible answers