Skip to main content

Setup a Database Snapshot

I have been tinkering lately with database snapshots and I thought the subject warranted a short post on the subject. This post will details a few things of note about snapshots and how to create a snapshot on your database.

Database snapshot provide a read-only point in time view of the source database. Database snapshot utilise sparse files and “copy on write” technology to take a snapshot of your database at a point in time. Database snapshots work at the page level, Before a page is changed  in the source database, the page as it exists before any change is made  is copied to the snapshot thus preserving the values on that page in the snapshot.

Because of the dependency on the source database, the snapshot must reside on the same SQL Server instance as the source database.

In terms of size, the largest a snapshot can get is the exact same size of the source database when the snapshot was taken. Thus if all the data in your database changes frequently you will need enough space to hold two copies of the source database.

Pages will only be copied to the snapshot once.

You cannot currently backup a snapshot, I think Steve Jones of SQL Server Central has posted a connect requested asking for snapshot backups and he has received a response, he has a post on the subject here http://www.sqlservercentral.com/blogs/steve_jones/archive/2010/02/19/feedback-from-connect-_3A00_-allow-snapshot-backups.aspx

Snapshots are only available in Enterprise edition of SQL Server.

The write on copy (write before copy) procedure can be a performance overhead because of the additional IO needed to maintain the snapshot

Snapshots can be useful for reporting against the source database and also provide a way to recover the source database in certain scenarios.

OK so how do you create a database snapshot?

You need to use TSQL, you can’t create a snapshot through management studio. I have a bankingDB database on my instance of SQL Server (developer edition) I will create a snapshot of that database for the purposes of this example.

You create a snapshot using the CREATE DATABASE statement specifying AS SNAPSHOT OF clause. You also need to specify all the logical file names of the data files in the source database.

To get all the logical filenames of the data files in the source database you run this TSQL:

USE BankingDB
GO
select * from sysfiles




When you have logical name of the database files you can form your TSQL script. This is script i used to create a snapshot of my BankingDB database:



CREATE DATABASE Banking_dbss ON
( NAME = BankingDB, FILENAME =
'C:\DATA\SQLServer2008\Banking_dbss.ss' )
AS SNAPSHOT OF BankingDB;
GO



When you have created you snapshot you should have an entry under the database snapshots folder in SSMS



SnapshotSSMS



You can reference this snapshot as you would a normal database with the USE statement and you can run select statements against it too.

Comments

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…

How to Setup Kerberos Correctly

David was in Copenhagen this weekend delivering his Kerberos talk Taming the Beast: Kerberos for the SQL DBA to SQL Saturday Denmark. I have had a quick chat with him via email since he got back and he said he had a great time. The event was very well attended with 280+ attendees and his talk was well attended.

I think David is planning submitting a few sessions to SQL Saturday events in Europe in the next few months so look out for him there and we'll keep you posted as to his whereabouts when schedules get finalised later in the year.

David has pre-recorded his Kerberos talk. You can watch on you tube and I have also embedded it in this post if you want to see what his kerberos talk  covers...



If we can help you with a SQL Sever problem visit our SQL Server Consulting page or contact us