Tracking Illicit Users
Longtime SQL Server guru David Poole brings us a look at one of the thorny problems a DBA faces: tracking down illicit users.
Longtime SQL Server guru David Poole brings us a look at one of the thorny problems a DBA faces: tracking down illicit users.
Application locks aren't a well known area of locking in SQL Server, but they can be very useful for special scenarios. They work in an analogous way to the lock() construct in .Net and are basicaly user defined mutexes in SQL Server.
The amount of data in the world grows every day and there's no end in sight. How big a problem is storage management? Steve Jones shares a few thoughts on how you might manage your storage.
The amount of data in the world grows every day and there's no end in sight. How big a problem is storage management? Steve Jones shares a few thoughts on how you might manage your storage.
The amount of data in the world grows every day and there's no end in sight. How big a problem is storage management? Steve Jones shares a few thoughts on how you might manage your storage.
An offer from Red Gate for free downloadable posters. You can print them out and decorate your cube, showing some great disaster recovery tips from MVP Brad McGehee.
It would be wonderful to be able to simple purchase a tool or technology and have your data challenges disappear. It is time to step back and take a much needed different look at data.
SQL Server 2000 replication is usually simple and easy to setup and work with. However there are many restrictions to ensure this, one of which is the alteration of a column which is engaged in replication. Author Paul Ibison brings us two options for altering columns.
Digital technologies have made the transfer of information easier than ever, but what about it's long term storage? That doesn't seem to be as easy as we might think.
When automating administrative actions for SQL Server, there are a number of ways to handle the workflow. Longtime SQL Server DBA Roy Carlson brings us a technique for using a text file as input to the standard SQL Server tools.
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
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