SQL Saturday #141 - South Florida
A free day of training in Davie, FL this weekend. Come by if you can
A free day of training in Davie, FL this weekend. Come by if you can
Is it worth writing your own software? Steve Jones says you ought to really think about it and perhaps spend time looking to buy something before you build a new application.
If you are trouble-shooting an AlwaysOn Availability Group topology, a study of the wait statistics will give a pointer to many of the causes of problems. Although several wait types are documented, there is nothing like practical experiment to familiarize yourself with new wait stats, and Joe Sack demonstrates a way of testing the sort of waits generated by an availability group under various circumstances.
Our 19th webinar will feature Brad McGehee talking about storage challenges, costs, and potential solutions for better managing your data. Tuesday, June 12, at 4:00pm GMT.
This editorial that was originally published on Aug 15, 2007. It is being rerun as Steve is traveling. This editorial looks at the issues that happen in production and how you should perhaps plan for disasters.
The Database Recovery Advisor in SQL Server 2012 will aid the ability of DBAs to recover their databases to a point in time in a crisis. Read about this new feature and how it can speed the process of recovery.
Database people are used to changing the hardware of the server on which a problem database resides, or making changes to indexes and database settings, but humans and their organisations are far more difficult to tune and optimise than databases.
Among the many new features released in SQL Server 2012 is FileTable, which facilitates database storage of file and directory storage.
This articles brings a comparison of temporary tables with table variables from SQL Server author, Wayne Sheffield. In includes an in-depth look at the differences between them.
Today we have an editorial from Aug 8, 2007 that is being republished as Steve is on holiday. This piece looks at interns and how it's a good idea for finding new employees.
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