This article shows how to install Northwind and Pubs databases on Microsoft SQL Server 2008 Express.

Step-by-step

1. Browse to SQL Server 2000 Sample Databases and click on SQL2000.Sample.Databases.(Northwind,pubs).zip to download the Northwind and Pubs databases. Once you clicked the file, there will be a pop-up displays license of this file. Click I Agree to download the file.
   Note: This file contains sample databases that can be used on SQL Server 2000/2005/2008.
   
2. Extract the zipped file, you will see files as the figure below. There are two methods to install these sample databases on SQL Server. The first method, run query on the SQL Server using instnwnd.sql and instpubs.sql for Northwind and Pubs databases respectively. The second method, attach database on SQL Server using NORTHWND.LDF and NORTHWND.MDF for Northwind database and PUBS.MDF and PUBS_LOG.MDF for Pubs database. On this article, I will show how to install Northwind and Pubs databases using the second method.
   
3. Open Microsoft SQL Server Management Studio and connect to your SQL Server.
   
4. Once the connection has been established, right-click on Databases and select Attach.
   
5. On Attach Databases, click Add in Databases to attach section.
   
6. On Locate Database File, browse to the folder where you extracted the downloaded file in step 2. Select a database file that you want to attach. I select NORTHWND.MDF which refers to Northwind database and click OK.
   
7. You will see detail of Northwind database. The NORTHWND.LDF is automatically added in the details on section below (“Northwind” database details).
   
8. Repeat step 5 and 6 for Pubs database by attach PUBS.MDF file if you want to attach more than one database at the time. After you finish selecting databases that you want to attach, click OK.
   
9. If there is no error, you will see the sample databases (Northwind and Pubs) list on the SQL Server as the figure below. Now you can use these sample databases as you want.
   

Related posts:

1. Enable Remote Connection on SQL Server 2008 Express Introduction Last time, I wrote an article show how to...
2. Restore Database From SQL Server 2008 to SQL Server 2005, Part 2: Generate SQL Server Scripts Wizard Generate SQL Server Scripts Wizard On Part 1: Introduction, I...

When you are installing Microsoft SQL Server Management Studio Express on Windows Vista or Windows 7, you may receive this error message:

The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 29506.

This error message relates with permission issue (UAC) on Windows Vista and Windows 7. To solve this problem, you have to re-run the installer again using elevated command prompt by run the command prompt as administrator and execute the installer in there. If you are using 64-bit Windows, you should use the command prompt at C:\Windows\SysWOW64\cmd.exe instead. Otherwise, you can use the command prompt at C:\Windows\System32\cmd.exe. You will see the step-by-step guide to use elevated command prompt to execute the installer file on the section below.

The other solution, you can disable UAC on Windows but I don’t recommend it since it will lower your security system.

Step-by-step

1. Run elevated command prompt by right-click on Command Prompt in Start -> All Programs -> Accessories -> Command Prompt and select Run as administrator.
   Note: This step is for 32-bit Windows. If you are using 64-bit Windows, see the next step.
   
2. If you are using 64-bit Windows, you have to run the command prompt in C:\Windows\SysWOW64. Right-click on cmd.exe and select Run as administrator.
   
3. On User Account Control, click Yes.
   
4. On Command Prompt (both 32-bit and 64-bit Windows), change path to directory where the installer file is and execute the file. By default, the file name for 32-bit version is SQLServer2005_SSMSEE.msi and 64-bit version is SQLServer2005_SSMSEE_x64.msi.
   
5. On Setup Wizard, follow the instruction as usual. There won’t be the error message this time.
   

No related posts.

If you execute a vb script which use SQL-DMO on SQL Server 2008, you will notice that the script doesn’t work at all.

You will see the error message as similar to this one when you execute the vb script:

Error: ActiveX component can’t create object: ‘SQLDMO.SQLServer’
Code: 800A01AD
Source: Microsoft VBScript runtime error

Cause

This is because SQLDMO is deprecated since SQL Server 2005. But SQLDMO is installed on SQL Server 2005 by default so you can run a vb script which uses SQLDMO without any error on SQL Server 2005. On SQL Server 2008, SQLDMO is not installed by default . If you want to use SQLDMO, you have to install it manually.

Solution

To use SQL-DMO on SQL Server 2008, you need to download and install Microsoft SQL Server 2005 Backward Compatibility Components to solve the problem. You can go to Microsoft Download Center and search for “Microsoft SQL Server 2008 Feature Pack” and sort by Release Date to find the latest version. Or you can download at Linglom’s Download Page.

Step-by-step

1. Download Microsoft SQL Server 2005 Backward Compatibility Components. Next, execute the setup file.
2. On Welcome to the Install Wizard for Microsoft SQL Server 2005 Backward compatibility Setup, click Next.
   
3. On License Agreement, select ‘I accept the terms in the license agreement‘. Then, click Next.
   
4. On Registration Information, enter your personal information. Then, click Next.
   
5. On Feature Selection, ensure that SQL Distributed Management Objects is selected. Then, click Next.
   Note: SQL-DMO is the feature that is require to run a vb script that uses DMO.
   
6. On Ready to Install the Program, click Install.
   
7. Installing Microsoft SQL Server 2005 Backward compatibility.
   
8. On Completing the Microsoft SQL Server 2005 Backward compatibility Setup, click Finish. Now try to run vb script again, the problem should be gone!
   

Reference

Where the Heck is DMO?

Related posts:

1. Restore Database From SQL Server 2008 to SQL Server 2005, Part 2: Generate SQL Server Scripts Wizard Generate SQL Server Scripts Wizard On Part 1: Introduction, I...
2. Restore Database From SQL Server 2008 to SQL Server 2005, Part 1: Introduction Problem When you restore or attach a database which is...
3. [Solved] Failed to Create SQL Login for Group On Database Server Problem You’re configuring BizTalk Server 2006 which BizTalk databases are...

On Part 1: Introduction, I mentioned about error messages when you try to restore a database from SQL Server 2008 to SQL Server 2005. You can see the first solution at Part 2: Generate SQL Server Scripts Wizard. Now let’s see the second solution to solve the problems.

On this post, you see how to export tables on ‘Northwind’ database from SQL Server 2008 to SQL Server 2005 using export data wizard.

Step-by-step

1. On Microsoft SQL Server Management Studio, connects to SQL Server 2008. Right-click on the database that you want to export data -> select Tasks -> Export Data.
   
2. On Welcome to SQL Server Import and Export Wizard, click Next.
   
3. On Choose a Data Source, select the source from which to copy data. Set Data source to SQL Server Native Client 10.0. Verify that Server name is the source of SQL Server 2008 that you want and select Database as ‘Northwind’. Click Next.
   
4. On Choose a Destination, specify where to copy data to. Set Destination to SQL Server Native Client 10.0. Type the Server name to the destination of SQL Server 2005 that you want. You can also click Refresh to verify if you can connect to the specify server name. Currently, I don’t have ‘Northwind’ database on SQL Server 2005 so I will create a new one, click New.
   
5. On Create Database, type name as ‘Northwind’ and click OK.
   
6. Back to Choose a Destination, I have created ‘Northwind’ database so select it as Database. Click Next.
   
7. On Specify Table Copy or Query, select Copy data from one or more tables or views and click Next.
   
8. On Select Sources Tables and Views, select tables that you want to export. On this example, I select all tables on ‘Northwind’ database.
   
9. On Save and Run Package, click Next.
   
10. On Complete the Wizard, you can verify the choices made in the wizard. Then, click Finish.
    
11. Wait until the wizard finishes execution.
    
12. Now I have exported tables of ‘Northwind’ database from SQL Server 2008 to SQL Server 2005 successfully.
    

Related posts:

1. Restore Database From SQL Server 2008 to SQL Server 2005, Part 2: Generate SQL Server Scripts Wizard Generate SQL Server Scripts Wizard On Part 1: Introduction, I...
2. Restore Database From SQL Server 2008 to SQL Server 2005, Part 1: Introduction Problem When you restore or attach a database which is...
3. How to backup and restore database on Microsoft SQL Server 2005 Introduction This post will give you a brief introduction of...

On Part 1: Introduction, I mentioned about error messages when you try to restore a database from SQL Server 2008 to SQL Server 2005. Now let’s see a first solution to solve the problems.

On this post, you see how to backup ‘Northwind’ database by generate a SQL Server script on SQL Server 2008. Then, restore the ‘Northwind’ database by execute the SQL Server script on SQL Server 2005.

Step-by-step

1. On Microsoft SQL Server Management Studio, connects to the SQL Server 2008. Right-click on the database that you want to backup and select Tasks -> Generate Scripts.
   
2. On Welcome to the Generate SQL Server Scripts Wizard, click Next.
   
3. On Select Database, select Northwind and check Script all objects in the selected database. Then, click Next.
   
4. On Choose Script Options, set Script Database Create to False and Script for Server Version to SQL Server 2005.
   Note: You can set Script Database Create to True if your source and destination for store database files are the same location.
   
5. Continue on Choose Script Options, scroll down and set Script Data to True. Click Next
   Note: Set this option to true to include data on each table to a script.
   
6. On Output Option, select a destination for the output script. Select Script to file and browse to the location that you want. Click Next.
   
7. On Script Wizard Summary, you can review your selections. Then, click Finish.
   
8. On Generate Script Progress, the wizard is creating a SQL Server script.
   
9. When the script has been completed, you see the output file as similar the figure below.
   
10. Connect to SQL Server 2005, create a new database. Right-click Database -> New Database.
    Note: If you have set Script Database Create to True on step 4, you don’t have to create a database manually.
    
11. Type ‘Northwind’ as database name. Click OK.
    
12. Execute the SQL Server script file that you have created.
    
13. Now the database ‘Northwind’ is restored on SQL Server 2005.
    

Related posts:

1. Restore Database From SQL Server 2008 to SQL Server 2005, Part 3: Export Data Wizard Export Data Wizard On Part 1: Introduction, I mentioned about...
2. Restore Database From SQL Server 2008 to SQL Server 2005, Part 1: Introduction Problem When you restore or attach a database which is...
3. How to backup and restore database on Microsoft SQL Server 2005 Introduction This post will give you a brief introduction of...

When you restore or attach a database which is created from SQL Server 2008 to SQL Server 2005 or SQL Server 2000, you will see some error messages as the examples below.

Backup and Restore

You have backup a database from SQL Server 2008. If you try to restore the backup database file to SQL Server 2005, you will receive the error message:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Additional information:
-> The media family on device ‘the backup file‘ is incorrectly formed. SQL Server cannot process this media family.
RESTORE HEADERONLY is terminating abnormally. (Microsoft SQL Server, Error: 3241)

Detach and Attach

You have detach a database from SQL Server 2008. If you try to attach the detached database file to SQL Server 2005, you will receive the error message:

Attach database failed for Server ‘SQL Server name’. (Microsoft.SqlServer.Smo)
Additional information:
-> An exception occurred while executing a Transact-SQL statement batch. (Microsoft.SqlServer.ConnectionInfo)
–> The database ‘database name’ cannot be opened because it is version 655. This server supports version 611 and earlier. A downgrade path is not supported.
Could not open new database ‘database name’. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 948)

Solution

These problems occur because a backup or detach database file is not backward compatible. You cannot restore or attach a database which is created from a higher version of SQL Server to a lower version of SQL Server.

But there are some alternatives which can help you to restore a database to a lower version of SQL Server. I divide into separate parts.

1. Part 2: Generate SQL Server Scripts Wizard. The solution creates a SQL Server script file using a wizard. Then, you simply execute the script file on SQL Server 2005 or SQL Server 2000. So you will get everything as same as the source database on the destination. But there are some disadvantages:
   • If the source database contains lots of data, you will have a large script file.
   • The generated file is a plain text. Anyone who has access to the file can read it. So you should delete the script file after the restoration.
2. Part 3: Import and Export Wizard. This solution exports data to the targeted SQL Server using a wizard. It is more secure and effective than the first solution. But you can only export tables and views only.

Related posts:

1. Restore Database From SQL Server 2008 to SQL Server 2005, Part 2: Generate SQL Server Scripts Wizard Generate SQL Server Scripts Wizard On Part 1: Introduction, I...
2. Restore Database From SQL Server 2008 to SQL Server 2005, Part 3: Export Data Wizard Export Data Wizard On Part 1: Introduction, I mentioned about...
3. How to backup and restore database on Microsoft SQL Server 2005 Introduction This post will give you a brief introduction of...

You have backup a database on SQL Server 2005. Then, you try to restore the backup file on an existing database and receive the error message below:

Restore failed for Server ‘SQL Server name‘. (Microsoft.SqlServer.Smo)
Additional information:
System.Data.SqlClient.SqlError: The backup set holds a backup of a database other than the existing ‘dbName‘ database. (Microsoft.SqlServer.Smo)

This error message indicates that you are going to restore a database on another database which are not the same database. For example, you have backup Northwind database and try to restore the backup to AdventureWorks database, the error will occur.

Solution

To solve the problem, you can use the overwrite the existing database option while you’re restoring.

1. On Restore Database, select Options tab on the left menu. Then, check Overwrite the existing database on Restore options.
   Note: This option will overwrite any existing data on the targeted database.
   
2. Try to restore the database, the problem should be gone now.
   

Note: you can also delete the targeted database before perform restore a database. This way also gives the result as same as the solution above.

Related posts:

1. [Solved] System.Data.SqlClient.SqlError: The tail of the log for the database “dbName” has not been backed up Problem You have backup a database on SQL Server 2005....

You have backup a database on SQL Server 2005. Then, you try to restore the backup file on the existing database and receive the error message below:

Restore failed for Server ‘SQL Server name‘. (Microsoft.SqlServer.Smo)
Additional information:
System.Data.SqlClient.SqlError: The tail of the log for the database “dbName” has not been backed up. Use BACKUP LOG WITH NORECOVERY to backup the log if it contains work you do not want to lose. Use the WITH REPLACE or WITH STOPAT clause of the RESTORE statement to just overwrite the contents of the log. (Microsoft.SqlServer.Smo)

This error message is likely to be a warning message rather than an error message. It indicates that you are going to restore a database to replace the existing database and some data may be lose. For example, you perform backup on this following schedule:

• database at 10:00 AM
• transaction log at 11:00 AM
• transaction log at 01:00 PM

Now if you are going to restore the backup at 04:00 PM. You will lose any work after 01:00 till 04:00 which is same as the error message above try to warn you.

Solution

To solve the problem, you can either:

• Replace the existing database with a backup file. This option is fast and easy but you will lose any work after the last backup has been performed.
• Do backup transaction log again with NORECOVERY option before restoring a database. With NORECOVERY option, the database will be in restoring state and waiting for restoration.

In this post, I will show only the first solution only. For the second solution, see How to: Back Up the Tail of the Transaction Log (SQL Server Management Studio)

Restore by overwrite an existing database

1. On Restore Database, select Options tab on the left menu. Then, check Overwrite the existing database on Restore options.
   Note: This option will overwrite any existing data on the targeted database.
   
2. Try to restore the database, the problem should be gone now.
   

Related posts:

1. [Solved] System.Data.SqlClient.SqlError: The backup set holds a backup of a database other than the existing ‘dbName’ database Problem You have backup a database on SQL Server 2005....

Last time, I wrote an article show how to enable remote connection on SQL Server 2005 Express. Now SQL Server 2008 Express is released for a while, it doesn’t allow remote connection on default installation as on SQL Server 2005 Express. So you have to enable it manually.

If you’re trying to connect to SQL Server 2008 Express remotely without enable remote connection first, you may see these error messages:

• “Cannot connect to SQL-Server-Instance-Name
  An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 28 – Server doesn’t support requested protocol) (Microsoft SQL Server)”
  
• “Cannot connect to SQL-Server-Instance-Name
  An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified) (Microsoft SQL Server)”
  
• “Cannot connect to SQL-Server-Instance-Name
  Login failed for user ‘username‘. (Microsoft SQL Server, Error: 18456)”
  

To enable remote connection on SQL Server 2008 Express, see the step below:

1. Start SQL Server Browser service if it’s not started yet. SQL Server Browser listens for incoming requests for Microsoft SQL Server resources and provides information about SQL Server instances installed on the computer.
2. Enable TCP/IP protocol for SQL Server 2008 Express to accept remote connection.
3. (Optional) Change Server Authentication to SQL Server and Windows Authentication. By default, SQL Server 2008 Express allows only Windows Authentication mode so you can connect to the SQL Server with current user log-on credential. If you want to specify user for connect to the SQL Server, you have to change Server Authentication to SQL Server and Windows Authentication.

Note: In SQL Server 2008 Express, there isn’t SQL Server Surface Area Configuration so you have to configure from SQL Server Configuration Manager instead.

Step-by-step

1. Open SQL Server Configuration Manager. Click Start -> Programs -> Microsoft SQL Server 2008 -> Configuration Tools -> SQL Server Configuration Manager.
   
2. On SQL Server Configuration Manager, select SQL Server Services on the left window. If the state on SQL Server Browser is not running, you have to configure and start the service. Otherwise, you can skip to step 6.
   
3. Double-click on SQL Server Browser, the Properties window will show up. Set the account for start SQL Server Browser Service. In this example, I set to Local Service account.
   
4. On SQL Server Browser Properties, move to Service tab and change Start Mode to Automatic. Therefore, the service will be start automatically when the computer starts. Click OK to apply changes.
   
5. Back to SQL Server Configuration Manager, right-click on SQL Server Bowser on the right window and select Start to start the service.
   
6. On the left window, expand SQL Server Network Configuration -> Protocols for SQLEXPRESS. You see that TCP/IP protocol status is disabled.
   
7. Right-click on TCP/IP and select Enable to enable the protocol.
   
8. There is a pop-up shown up that you have to restart the SQL Service to apply changes.
   
9. On the left window, select SQL Server Services. Select SQL Server (SQLEXPRESS) on the right window -> click Restart. The SQL Server service will be restarted.
   
10. Open Microsoft SQL Server Management Studio and connect to the SQL Server 2008 Express.
    
11. Right-click on the SQL Server Instance and select Properties.
    
12. On Server Properties, select Security on the left window. Then, select SQL Server and Windows Authentication mode.
    
13. Again, there is a pop-up shown up that you have to restart the SQL Service to apply changes.
    
14. Right-click on the SQL Server Instance and select Restart.
    
15. That’s it. Now you should be able to connect to the SQL Server 2008 Express remotely.

Related posts:

1. Enable remote connection to SQL Server 2005 Express Introduction By default, SQL Server 2005 doesn’t allow remote connection...
2. How to Install Sample Databases (Northwind and Pubs) in SQL Server 2008 Express The databases, such Northwind and Pubs, are sample databases which...
3. How to Enable Remote Desktop Web Connection on Windows Introduction Remote Desktop Connection is one useful tool of Windows...

When you create a store procedure on Microsoft SQL Server with some input parameters, sometimes you don’t want to assign all of parameters (optional parameters) so you need to specify default value for the parameters. Otherwise, it shows error when execute the store procedure.

Let’s see some example, I have created a new store procedure to query product name from Northwind database which require 2 input parameters. The script to create a sample store procedure is below:

CREATE PROCEDURE sp_getproduct
		(@UnitPrice money,
		 @UnitsInStock SMALLINT = '10')
AS
BEGIN
	SET NOCOUNT ON;
 
	SELECT [ProductName] FROM Products
		WHERE ([UnitPrice] < @UnitPrice) AND
			  ([UnitsInStock] > @UnitsInStock)
END
GO

So as long as I specify both input parameters, the query is OK.

But if I miss an input parameter, the error will be shown as the figure below:

Solution

1. You can define the default value for parameters to avoid this error message. The default value generally is NULL. But you also can define other value as you want.
2. In this example, I’ve altered the store procedure by assign default value for these parameters to be NULL and also in WHERE clause.

   ALTER PROCEDURE sp_getproduct
   		(@UnitPrice money = NULL,
   		 @UnitsInStock SMALLINT = NULL)
   AS
   BEGIN
   	SET NOCOUNT ON;
    
   	SELECT [ProductName] FROM Products
   		WHERE ((@UnitPrice IS NULL) OR ([UnitPrice] < @UnitPrice)) AND
   			  ((@UnitsInStock IS NULL) OR ([UnitsInStock] > @UnitsInStock))
   END
   GO

   Code Explanation:

   • I’ve altered the parameters declaration to assign the NULL value as the default value.

     		(@UnitPrice money = NULL,
     		 @UnitsInStock SMALLINT = NULL)

   • Next, I’ve altered in WHERE clause to be TRUE if the parameters are NULL. So if the both parameters are NULL, the SELECT statement will return all ProductName from Products table.

     		WHERE ((@UnitPrice IS NULL) OR ([UnitPrice] < @UnitPrice)) AND
     			  ((@UnitsInStock IS NULL) OR ([UnitsInStock] > @UnitsInStock))

   

3. Re-execute the query again, you’ll see the error message is gone.
   

No related posts.