Installing the Northwinds Database with SQL Server 2012

As mentioned earlier, my new gig requires a lot more day-to-day work with SQL Server, including SSIS, SSRS, and SSDS. Since most tutorials use either the AdventureWorks database or the Northwinds database, you ought to have both in place if you want to get hands-on with the tutorials and sample out there.

In the last post, we downloaded and attached the AdventureWorks database to our SQL Server 2012 installation. In this post, we'll grab the Northwinds database and attach it to the same server.

Follow the steps below to obtain and install the Northwinds database.
  1. Open a web browser and go to http://www.microsoft.com/en-us/download/details.aspx?id=23654:
  2. Click the "Download" button and save the file SQL2000SampleDb.zip.
  3. Click on the file to run it. You'll be asked if you really want to run the installation:

    Click the "Run" button.
  4. Step through the prompts:








  5. You'll find that the installation has created a new folder, SQL Server 2000 Sample Databases, on your primary drive (usually C:).
  6. Open the folder. You'll find among other things to SQL scripts, instnwnd.sql and instpubs.sql:
  7. Edit each file, commenting out the lines referring to the stored procedure  sp_dboption, which was deprecated in SQL Server 2012.
  8. Save the edited files and run them. I started with the Northwind script, instnwnd.sql, and then followed up with the pubs script, instpubs.sql.
  9. If you run into any problems, then check the message(s) kicked back by the system. They'll tell you which lines were an issue and why. Correct the issues and rerun the scripts.
Once you're done, then you'll have two new databases, northwind and pubs.

Note: I can't take credit for figuring out the issue with the store procedure sp_dboption. I found the solution here. If you get time, then you ought to check out the rest of that blog; it's got lots of good stuff.

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