I've been backing up SQL Servers for almost a decade now, and it's time to share the lessons I've learned. All of this is my own opinion - your mileage may vary - but I'll try to explain the reasoning behind the choices I make. I won't address log shipping or snapshots this time around.…
Database administrators need to know each SQL Server's weakest link so we know where to focus their hardware budgets and time. On any given server, we need to know what the slowest component is, and where it'll pay off to invest hours and dollars. This is performance tuning, and the first place to start is by using Performance Monitor.
YES! YES! YES!
Or as they say in the World Cup, GOOOOOOOOOOOOOOOAL!
I had to do some developer training last week and I wrote up a paper on the basics of primary keys and indexes. Sure, there's tons of similar stuff around the net, but this is MINE, baby.
Our Table: Phone Numbers
For our evil training purposes, let's say we work for the phone company, and we need a database table with phone numbers. We need to track:
I had a really crummy day yesterday. Things just weren't going my way, and I had all kinds of stupid small programming problems at work. Just one unrelated thing after another. Sometime in the afternoon, I stumbled downstairs for yet another pot of coffee and some ibuprofen, but I wasn't really paying attention. I was…
