Automatically Gathering Server Information Part 2
The second part of Steve Jones's series on having SQL Server automatically report information to a DBA.
The second part of Steve Jones's series on having SQL Server automatically report information to a DBA.
The first part of Steve Jones's series on having SQL Server automatically report information to a DBA.
Get started with using WMI (Windows Mgmt Instrumentation) by seeing two good scripts to start with, one to reboot the server, another to list all the services.
Dinesh looks at the date functions, how to work with time zones (or not), and does a brief comparison to see how you do similar tasks in Oracle.
As Chris points out, in most applications these days you end up having to go with optimistic locking, which presents a few challenges. Chris works through the list of options. If you're building web/disconnected apps and need anything besides last update wins, this one is for you.
Sysdepends is a neat idea, but in practice it's not always accurate. This article talks about why it's not always reliable and presents some code (recursive even!) that will let you find all the dependencies by querying the system tables.
This article presents two best practices. One is about how to construct good table aliases, the other is about using ANSI join syntax. Good stuff!
This short article looks at some mistakes developers should avoid when they also have the task of designing the database, database objects, or TSQL used to access it.
Why would you ever create duplicate indexes? Does that even make sense? Steve Jones isn't sure, and that's for another day, but it sure caused him some problems. Follow along and find a solution for tracking these down.
Full text indexing is interesting, but not always easy for the user to apply well. Chris has some ideas about to make that
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