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,052 reads
2005-06-01
1,820 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,101 reads
2005-03-07
1,388 reads
2004-12-22
1,716 reads
2004-12-08
1,734 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,070 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,921 reads
2004-08-27
2,233 reads
By Brian Kelley
Following the advice in Smart Brevity improves communication.
By John
Microsoft has released SQL Server 2025, bringing big improvements to its main database engine....
By Steve Jones
A customer was asking about what certain items in Redgate Monitor mean. They have...
Comments posted to this topic are about the item Using Python notebooks to save...
Comments posted to this topic are about the item Your AI Successes
I have table: t1 in schema1 with 19 billion records. I have another table...
What is returned from this code in SQL Server 2025?
SELECT BASE64_ENCODE(NULL)See possible answers