Here's the link to download the sample scripts and meme-tastic slidedeck from my presentation "SQL Server Indexes in Your Ill-Begotten Databases".
Thanks for everyone who attended, presented, judged and laughed!
Wednesday, November 20, 2013
Tuesday, November 05, 2013
Potential Backup Software Issues with Read-Only Databases in FULL Recovery
If you decide to park a database in read-only mode for a long period of time, go ahead and alter it into SIMPLE recovery mode too.
The message returned by SQL when you try to take a transaction log backup is:
"BACKUP LOG cannot modify the database because the database is read-only. The backup will continue, although subsequent backups will duplicate the work of this backup."
which is fairly self-explanatory to a human.
But to an automated system, such as a third-party enterprise backup platform, this message is not always interpreted correctly.
eVault, for example, does not detect the read-only condition or the message from SQL and instead returns this generic error message:
"A gap was detected in log files for database foo. You will need to re-run a Full backup."
Which is misleading and incorrect and pointed troubleshooting efforts of backup administrators in the wrong direction.
The message returned by SQL when you try to take a transaction log backup is:
"BACKUP LOG cannot modify the database because the database is read-only. The backup will continue, although subsequent backups will duplicate the work of this backup."
which is fairly self-explanatory to a human.
But to an automated system, such as a third-party enterprise backup platform, this message is not always interpreted correctly.
eVault, for example, does not detect the read-only condition or the message from SQL and instead returns this generic error message:
"A gap was detected in log files for database foo. You will need to re-run a Full backup."
Which is misleading and incorrect and pointed troubleshooting efforts of backup administrators in the wrong direction.
Saturday, November 02, 2013
SQL Saturday #255 Dallas 2013 - SQL Server Permissions and Security Principals
500+ IT pros at UT-Arlington this weekend for SQL Saturday #255 Dallas!
Notes from today:
Notes from today:
- A big shout-out to SQLSat Dallas organizer and 2013 PASSion Award Honorable Mention winner Ryan Adams, the South Central PASS Regional Manager, which includes the Baton Rouge User Group. Ryan has spoken at SQLSatBR in the past and it's my pleasure to return the favor.
- I presented an introductory-level SQL security principals session at 1:30 in Track 1 Room 100. Thanks for attending! Click this link for the slidedeck and demo scripts from this presentation. Great crowds and amazing feedback today, great job everyone! Big thanks to the 40+ in attendance!
- Also, my favorite human resources professional presented on "Mastering your Resume & Interview: Tips to Get Hired" at 9:45AM in Track 6 Room 110 and "Interview Tips for Managers" at 1:30PM in the same room. Huge crowds in both, and great questions!
- It is totally Data Manipulation Language. I'm not above admitting I'm wrong or fulfilling my promise to admit it on my blog. :)
On a more serious note:
Someone at #SQLSat255 asked one of my female developer coworkers today if she was a "booth babe". Someone else assumed she was in "sales", not technical. Damnit, guys. Totally not cool. We can do much better.
Subscribe to:
Posts (Atom)