Skip to main content

Live From @LearningTree London Backup and Restore - Day 3

This week I’m teaching Learning Tree’s course 2108 SQL Server Database Administration in the LEC in London. Following on from last weeks success live blogging from the back of the room whilst producing the 294 influence skills course, this week I’m in the process of trying this from the front of the class.

You can read all about the previous days here

Day 3 three focuses on the most important area of SQL Server Database Administration in my opinion. Backup and Restore. We cover everything from restoring restoring user databases to recovering broken servers.

If you need any help with your disaster recovery planning and implmentation. Check out our SQL Server Consulting Page

You can follow how today goes here on the blog

16:30 With the backup job for Human Resources created. That's going to be it for the day. We'll start again in the morning looking database maintenance tasks.

16:05 Creating a backup job for the Human Resources database.

15:45 Started looking at agents jobs and configuring the agent to work with database mail.

15:30 Chapter 6 is working with the Agent. We're about setup database mail so we can configure some alerts and notifications.

15:00 We are going to look at automating a lot of these tasks in the next chapter.

14:50 Everyone has recovered the databases and the SQL Servers are backup and running. Phew! I think everyone deserves a coffee

14:45 Log block version 2 is not supported. Interesting error.

14:10 after some dicssion around rebuilding and restoring the master database, the group are now attempting to run through the recovery process. Rebuilding master and restoring then restoring the orders database to a point in time. Fun stuff.

13:30 - We're getting to the creating chaos section of the lab. I'm starting to get nervous for the attendees :-)

13:10 - We are back after lunch, with a hands-on exercise backing up user and system databases, then we'll create some chaos

12:10 Lunch on day 3 - We have a fun afternoon to look forward too.

12:05 Looking at why you should backup the system databases and the frequency with which they should be backed up

12:00 Discussion around transaction log backups, why they are important and the role they play in being able to recover a database to a point in time.

11:40 - Looking at creating a full database backup and a differential database backup

11:05 Setting our databases up with the correct recovery model

10:40 We'll start again by looking at restore scenarios

10:25 Coffee Break Time

10:00 Discussion the different types of Recovery mode

  • Simple
  • Bulk Logged 
  • Full

And their implications and what we need to do to manage the log.

09:30 Started talking about the transaction log  and its importance in the SQL Server recovery process

0900 Review of yesterday and did some practice questions on what we have covered so far. 

08:30 Classroom is setup and people are beginning to arrive


Popular posts from this blog

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

New in SQL Server 2017: Graph Databases

David has recorded and published a video of his presentation on SQL Server Graph Database. In his video which you can watch below, David provides an excellent introduction into SQL Server 2017 Graph Databases. In his presentation he looks at Tennis results at tournaments for  his favourite player "The Fed"  Rodger Federer.

David  shows how to set up graph database and work with them in SQL Server 2017.

Graph Database is not new. Other vendors have had graph database capabilities for some time so Microsoft are quite late to the market. In David presentation it appears that Microsoft have done a reasonable job of implementing some of the graph database features but he does point some of the limitations of the Microsoft product too and suggests that it is not ready for production yet but Microsoft seem serious about this feature.

Please watch the video and feel free to leave a comment or feedback - David is delivering a version of this talk on Graph databases in SQL Saturday Ka…