When the Tables Tab is refreshed after the script is run, the AWBuildVersion table is dropped from the AdventureWorks Source database as it appears in image number 2 below. For example, the AWBuildVersion table that appears in Frame 1 under the DBO schema from the AdventureWorks database is being dropped.

For example, errors such as deleting a table completely, or truncating the table known Administrator errors. I said Snapshot database are also effective for Administrator and user errors. As in the image below, the same tables as Source database can also be queried from the Snaphot database. in the Source are all in the Snapshot database. When we examine the Snapshot database, all items such as Table, Views, Stored Procedures etc. Sparse File as shown in the image below, only the Source database will be changed pages. Size 2 is the size of the AdventureWorksSnaphot’s Sparsefile file. The size 1 of the above image (1) is actually the size of the AdventureWorks Source database. The following image shows the location of the AdventureWorksSnaphot database on the Physical disk. Although a Sparse file is created up to the size of the AdventureWorks database in the disk, it is initially created as a very small size. This database is just an image or snapshot of the AdventureWorks database.

AdventureWorksSnaphot was created at the bottom of the Snaphot tab, as it appears on the left side when the script is run.

Adventureworks database sql server 2012