Download Adventure Works 2014 Full Database Backup.zip

0 views

Skip to first unread message

Aureo Harvey

unread,

Aug 3, 2024, 3:51:08 PM8/3/24

to viacichisleu

I've just installed MS SQL Server Express 2014 and SQL Server Management Studio 2014 under Windows 10. I'm following the official Microsoft tutorial on database fundamentals, which uses the Adventureworks DW2008 database. I have tried to restore this dB using the Restore GUI, but it fails every time, as shown here:

I have verified the backup media, but it still fails. I have also restored a different dB, and that worked fine, so I know I am following the correct procedure. I have the file (AdventureworksDW2008Big.bak) in the following location:

I do not know if it will solve your problem or not,but I had same problem. I mean I am using SQL SERVER 2017 and I wanted to restore AdventureWorks2012.I received restore failed error, and I decided to restore AdventureWorks2017. my queries on AdventureWorks2012 in an older system in university led to the same results as my queries in AdventureWorks2017 in my system. if you are using a version of SQL SERVER and trying to restore an older or another version of AdventureWorks, you can try the same way.I mean restoring a version of AdventureWorks which is the same as the version of your SQL SERVER.

copy adventureworksxx.bak into the sql server DATA directory where bydefault all databases are usually located. ( Note: if it is in other directorythe restore may not find it OR may cause errors later)

Consider working, therefore, with 2008R2, if at all possible: learning the basics of MDX is challenging enough for most that are new to it, without the additional distractions imposed by working with older releases.

I found projects for later versions at -server-samples/releases/tag/adventureworks-analysis-services and I (not knowing anything about designing, deploying and processing a cube) actually managed to deploy and process a cube, but I had to edit the cube XML (basically I commented out some statements that referred to years greater than 2008).

A sample Analysis Services multidimensional model project. Requires Visual Studio 2015 with SQL Server Data Tools. To use this sample project, you must install an AdventureWorksDW database as a data source.

Using my msdn subscription I've built a VM with sql server 2012 using the image gallery supplied. Everything is up and running fine but I'm trying to create the adventure works dbs so I can have a play with the data.

Yeah, you're trying to create an Azure SQL Database copy of Adventureworks. You're in a VM. That's just like any other version of SQL Server. So you can go to the demos page[/url] and download a backup or an MDF file and restore or attach AdventureWorks. The other script is for creating the database within the Platform as a Service aspect of Azure.

Grant thanks for the reply. Yes that's exactly what I did last night just did a standard restore from the mdf ldf files. I was a bit thrown by the other blogs posts and I had issues with access to the c drive on my VM. All part of the learning curve while trying azure for the first time!!

Logical. Data is stored in an open format, for example, as an SQL script to recreate database objects and fill them with data. Such backups take longer, but you can view and modify them before restoring.

Physical. Data in the backup is in the same format that the database stores on the disk. Such backups are usually created and restored much faster because it is just copying data without transformations, but you will not be able to change something before restoring.

Partial. The backup does not contain all the data from the database, but only the specified schema or table. Useful if the database contains a lot of data that does not need to be backed up (temporary data, logs).

SQLBackupAndFTP is a popular backup utility. This utility creates databases backups and immediately sends them to the cloud storage on a selected schedule. The interface of the tool is very simple, and in order to configure the entire backup process, you do not need to know the SQL language, batch or PowerShell scripts.

The main advantage of incremental backups is that they can be done much more frequently. They take up little space and do not overload the server. The more often you make backups, the more restoration points you have.

Data-Tier Application is a stand-alone unit of database deployment that contains all database definitions such as a table, view, users, etc. As a result of an export, you get an archive with a set of XML files. This functionality is primarily intended for transferring data between different SQL servers. However, this feature can also be used to create a compressed logical backup.

Important note. Export Data-Tier Application is not executed within a single transaction. Therefore, the data may be exported in an inconsistent state, for example, a record in a table may reference a foreign key that is not available in another table. To avoid this, it is advisable to take a snapshot of the database before exporting.

A snapshot is not a physical copy of a database. Immediately after creation, the snapshot will take up almost no space. But it will grow every time the original database changes. After you have finished export, delete the snapshot.

If the resulting script is not large, you can restore it using SSMS by simply copying it into the SQL editor window. However, a text editor is not designed to run large scripts. Instead of an editor, you can run a backup using the sqlcmd utility.

You cannot just copy the file of the active database, it will be damaged. However, this problem can be solved. Windows has a Volume Shadow Copy service that helps the external backup service notify the software about the start of the backup, so the program can free the file it needs for the backup. For this trick to work, it is necessary that both the program that works with the file and the program that makes the backup be able to integrate with Volume Shadow Copy. SQL Server supports Volume Shadow Copy, and most file backup services do too.

As an example, consider backing up your database files with Windows Server Backup (WSB). The program is part of the Windows server. It is not connected by default. You can enable it via Add Roles and Feature.

A good practice for SQL Server backups is to create a hot physical backup based on BACKUP DATABASE. It can be created either by running an SQL command, or through SSMS, or SQLBackupAndFtp. To create backups, use differential or transaction log backups more often.

On the other hand, if you do not have access to SQL Server, but you have access to the machine on which it is installed, then you can use Windows Server Backup, as well as any other tool for backing up the volume or entire virtual machines.

The article describes not only how to make backups, but also how to restore the backups you created. People tend to leave out this information. Remember that a backup is created so that later it can be restored. Test your backups.

This article explains the process of installing the AdventureWorks2016 and AdventureWorksDW2016 sample database on a stand-alone instance of SQL Server and Azure SQL Server. The sample databases were published by Microsoft to demonstrate how to design a database using SQL Server. Microsoft has also published another lightweight database named AdventureworksLT, which can be used as a sample database on Azure SQL Server.

Once the backup is downloaded, open SQL Server Management Studio and from Object Explorer, expand database engine, right-click on Databases and select Restore Database. See the following image:

In the Locate backup devices window, select the backup media by clicking Add, and then in the newly opened window navigate to the directory where the database backup is downloaded and select the backup (.bak) file. Click OK:

If you want to change the physical location of the data file and log file, click on Files pane and change the target location for the data and log files. Note that it is best practice to keep data files and log files on separate drives:

Click OK. It will initiate the database restoring process. Once the database restores successfully, a popup appears stating that the database has been restored successfully. See the following image:

We can also prepare the database by executing the database installation script on SQL Server. To do that, first, you must download the installation scripts of AdventureWorks2016 and AdventureWorksDW2016 databases. You can download the installation scripts of the AdventureWorks OLTP database from AdventureWorks-OLTP-install-script.zip or use the files in the OLTP-install-script GitHub folder.

Similarly, to install AdventureWorksDW2016, you must download the installation scripts. You can download the installation script of the AdventureWorks OLAP database from AdventureWorksDW-data-warehouse-install-script.zip or use the files in data-warehouse-install-script Github folder. To install the AdventureWorksDW2016 database, follow the same process, which I explained above.

To install the sample database on Azure SQL Server, you must create a SQL Server resource group with the AdventureWorksLT database. To do that, log in to the Microsoft Azure portal, and on the home screen, click on Create a resource. See the following image:

On the next screen, fill the details of subscription, resource group, name of the database, and name of the server and type of compute + storage. Click Next. See the following image:

SQL Database Deployment process will start. It will take a couple of minutes. Once the deployment process completes, you will be able to connect to the database from the SQL Server Management Studio. See the following image:

In this article, I have explained how we can install the AdventureWorks2016 sample database on SQL Server stand-alone instance using full backup and installation scripts. Moreover, I have also installed the AdventureWorksLT database on Azure SQL Server.