In part one Chris Kempster covered a variety of security recommendations primarily for production systems. In Part two of this series he continues to explore security at a variety of levels where you may not realize you are vulnerable.
2019-10-04 (first published: 2004-01-30)
35,423 reads
This article by Chris Kempster covers a wide variety of areas concerned with data migration. Primarily, it focuses on process, standards and some of the many issues to consider when undertaking this role.
2017-08-23 (first published: 2004-03-24)
56,872 reads
This article by Chris Kempster shows you how to quickly move a database by detaching or taking a database offline.
2008-02-08 (first published: 2004-05-18)
148,318 reads
In this series of articles, Chris Kempster will discuss some of the finer aspects of SQL Server security and also touch on OS, physical and application security to open up this science for general discussion.
2007-10-02 (first published: 2002-01-14)
50,633 reads
For the most part the DTC (Distributed Transaction Coordinator) just works. What happens when it doesn't? Chris had to resolve an issue with it recently and documented some of the steps he used.
2004-01-19
19,929 reads
SQL Mail comes with SQL, but you have to load Outlook to use it. The alternative is to send email directly via SMTP. Combine that idea with alerts and you've got a new article!
2004-01-13
14,445 reads
Full text indexing is interesting, but not always easy for the user to apply well. Chris has some ideas about to make that
2003-12-11
12,211 reads
Chris Kempster brings us a basic look at the database design topic of denormalization.
2003-12-01
17,808 reads
One of our favorite authors is back with a great how-to on log shipping. This isn't the baked in log shipping, this is a code your own solution that gives you a starting point for your situation. Even if you don't need it now, it's worth looking at to gain a better understanding of how shipping works.
2003-11-26
26,209 reads
Another product review! Chris put AdeptSQL (a schema comparison and sync product) to work and wrote up the results. This article also includes some feedback from the vendor that is worth reading.
2003-11-03
5,192 reads
By HeyMo0sh
One of the biggest challenges I’ve faced in cloud operations is maintaining clear visibility...
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...
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