Installing the AdventureWorks Database with SQL Server 2012

My newest gig requires more day-to-day work with Microsoft SQL Server. In fact, I was told there'd be more SQL than C# involved in this job. I do pretty well with SQL but I figure it wouldn't hurt to reinforce the basics and learn some new tricks. Plus, I want to play in-depth with SQL Server Integration Services (SSIS), SQL Server Reporting Services (SSRS), and SQL Server Data Services (SSDS).

Nearly every tutorial out there uses the Northwinds database or the AdventureWorks database. AdventureWorks is pretty easy to install, so it's a good warm up exercise before we get into dealing with Northwinds.

Follow the steps below to obtain and install the AdventureWorks database.
  1. Open a web browser and go to http://msftdbprodsamples.codeplex.com/
  2. Click on the link "AdventureWorks Databases – 2008, 2008R2 and 2012" (http://msftdbprodsamples.codeplex.com/releases/view/93587). You'll be taken to the following page:
  3. Decide which version of the AdventureWorks database you wish to download. I chose the first option, AdventureWorks2012_Database.zip, which was the recommended option. Click on the file to download it.
  4. Unzip the file:
  5. If you didn't unzip the files to the SQL Server data directory, then copy the files from where you did unzip them to the SQL Server data directory. In my case, the data directory can be found at
    C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA
  6. Launch SQL Server Management Studio.
  7. Right-click on the Databases folder under the server you to which you wish to attach the database. Select "Attach..." from the popup menu.
  8. The system will display the "Attach Databases"dialog box:
  9. Click the "Add..." button and select the AdventureWorks database. Click the "OK" button.
  10. You'll be returned to the "Attach Database" dialog box. You'll see the AdventureWorks database listed:
  11. Click the "OK" button.
  12. The database is now listed:
Voila! You now have your own copy of the AdventureWorks database.

Note: The link above is for the AdventureWorks 2014 Sample Database (which, as far as I tell, works alright with SQL Server 2012). If you want the AdventureWorks 2012 Sample Database -- which is specifically for 2012, 2008 R2, and 2008 -- then you should go to http://msftdbprodsamples.codeplex.com/releases/view/93587.

Comments

Post a Comment

Popular posts from this blog

Using Reference Aliases

Image
I recently ran across a situation where two different libraries shared identical namespaces and class names. Visual Studio complained anytime I used one of these classes that it was an ambiguous reference. I needed both libraries -- each contained some unique elements -- so I couldn't ditch one or the other. But, as I said, anytime I tried to use a class that was common (again, via the class name and namespace), I received the ambiguous reference error. This was a real problem, so say the least. However, C# provides a way to specify exactly which library (reference) you mean when you use an object that's common to two or more libraries. Simply put, you use an extern alias  statement. The concept is fairly simple: Give the reference an alias (I used the Properties windows for the reference). Add an extern alias statement, putting it before your using statements. Add a using statement, which effectively links a specific object through the extern alias statement to th
Read more

List of Visual Studio Keyboard Shortcuts

Here's a link to a great list of keyboard shortcuts for Visual Studio: 149 Shortcuts for Visual Studio 2015 (Windows) While there's no need to memorize the list (that's why someone has created a cheat sheet, after all), it certainly doesn't hurt to look over the list from time to time and try to add one more command to your repertoire.
Read more

Quick Example of System.IO.Abstractions Use

I just got on a new project and am trying from the get-go to structure all my code so that it's easily testable. Academically, that is a no-brainer. In practice, though, some chunks of code are more difficult to structure so that they're easily testable. Towards that end, I've been pushing System.IO.Abstractions again. And, to get that going I decided it was time to refresh my examples. In the code below, we see how injecting the file system into the repository ultimately allows us to write testable code. If structured correctly, then our repository requires no subsequent refactoring to run in a unit test environment versus a "real" environment even when dealing with something like the file system. Let's take a look at our code. The Console Application The console application is straightforward. We have a private method (at the bottom) that assembles and returns a mock file system. Next, we perform the following steps: We feed that mock file system
Read more