I experienced this problem earlier when I worked in Windows XP and Sql Server 2008. Now I am using Suse Linux Ent Server 11 and Oradcle 10G. I put here the detailed information and solutions what I did this time. Plz read it very minutely and apply as per ur desire. Before do anything, it is good practice to take full back up of ur database.
* You are running the following versions of SQL Server Management Studio:
1.The release version of SQL Server 2008 Management Studio, version 10.00.1806 to 10.00.1813
Note For example, you install SQL Server 2008 Cumulative Update 5, and the version of Management Studio is 10.00.1806.
2. SQL Server 2008 Service Pack 1 (SP1) Management Studio, version 10.00.2714 to 10.00.2725
Note For example, you install SQL Server 2008 SP1 Cumulative Update 2, and the version of Management Studio is 10.00.2714.
3. You use one of these versions of SQL Server Management Studio to connect to a SQL Server 2000 instance.
4. You perform a backup operation on a database in the SQL Server 2000 instance.
5. In SQL Server Management Studio, you right-click the database to perform a restore operation in this SQL Server 2008 instance.
To resolve this problem, use the following table to find the appropriate method for your version of SQL Server.
SQL Server release Cumulative update Resolution
(version of SQL Server)
The release version 10.00.1806 to 10.00.1813 Apply the individual hotfix for the
of SQL Server 2008 release version of SQL Server 2008.
To obtain this hotfix, refer to the
“Hotfix information” section in this
article. Or, apply SQL Server 2008
Cumulative update package 7
SQL Server 2008 SP1 10.00.2714 to 10.00.2725 Apply the individual hotfix for the SQL
Server 2008 Service Pack 1. To obtain
this hotfix, refer to the “Hotfix
information” section in this article. Or,
Apply SQL Server 2008 Service Pack 1
Cumulative update package 4.
Cumulative update information:
1. SQL Server 2008, Important You must use this fix if you are running the release version of
SQL Server 2008.
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. I recommend that you consider applying the most recent fix release that contains this hotfix.
2. The SQL Server 2008 builds that were released after SQL Server 2008 was released
SQL Server 2008 Service Pack 1
Important You must use this fix if you are running SQL Server 2008 Service Pack 1.
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix.
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Hotfix information for SQL Server 2008 Service Pack 1
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a “Hotfix download available” If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
You must have SQL Server 2008 Service Pack 1 installed before you apply this hotfix.
Restart information, You do not have to restart the computer after you apply this hotfix.
Registry information, You do not have to change the registry. Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
For 32-bit version:-
SQL Server 2008 Database Services Core Shared Collapse this tableExpand this table
File name File File size Date Time Platform
Commanddest.dll 2007.100.2727.0 164,712 13-Aug-2009 03:01 X86
Datacollectorenumerators.dll 2007.100.2727.0 69,464 13-Aug-2009 03:03 x86
Distrib.exe 2007.100.2727.0 75,096 13-Aug-2009 03:19 x86
Dtspipeline.dll 2007.100.2727.0 694,104 13-Aug-2009 03:19 x86
Dtswizard.exe 2007.100.2727.0 804,712 13-Aug-2009 03:19 x86
Exceldest.dll 2007.100.2727.0 173,400 13-Aug-2009 03:35 x86
Excelsrc.dll 2007.100.2727.0 183,128 13-Aug-2009 03:35 x86
Flatfiledest.dll 2007.100.2727.0 276,312 13-Aug-2009 03:36 x86
Flatfilesrc.dll 2007.100.2727.0 283,992 13-Aug-2009 03:36 x86
Iftsph.dll 2007.100.2727.0 38,248 13-Aug-2009 03:52 x86
Logread.exe 2007.100.2727.0 423,256 13-Aug-2009 04:33 x86
Microsoft.sqlserver.dmf.dll 10.0.2727.0 296,792 13-Aug-2009 04:39 x86
Microsoft.sqlserver.pipelinehost.dll 10.0.2727.0 71,512 13-Aug-2009 04:42 x86
Microsoft.sqlserver.sqlenum.dll 10.0.2727.0 1,083,224 13-Aug-2009 04:42 x86
Oledbdest.dll 2007.100.2727.0 173,912 13-Aug-2009 04:52 x86
Oledbsrc.dll 2007.100.2727.0 186,728 13-Aug-2009 04:52 x86
Rdistcom.dll 2007.100.2727.0 651,112 13-Aug-2009 05:09 x86
Repldp.dll 2007.100.2727.0 191,336 13-Aug-2009 05:10 x86
Replmerg.exe 2007.100.2727.0 341,352 13-Aug-2009 05:10 x86
Snapshot.exe 10.0.2727.0 13,144 13-Aug-2009 06:18 x86
Sql_engine_core_shared_keyfile.dll 2007.100.2727.0 13,656 13-Aug-2009 04:19 x86
Sqllogship.exe 10.0.2727.0 96,104 13-Aug-2009 06:19 x86
Sqlmergx.dll 2007.100.2727.0 192,856 13-Aug-2009 06:19 x86
Sqltaskconnections.dll 2007.100.2727.0 113,496 13-Aug-2009 06:20 x86
Txdataconvert.dll 2007.100.2727.0 206,696 13-Aug-2009 06:24 x86
To work around this problem, use one of the following methods:-
Use Transact-SQL statements to restore the database. For example, you can use the following command to restore a database:
restore database Database Name from disk = ‘Backup file’
To restore the database by using SQL Server Management Studio, following these steps:
1. Do not right-click the database. Instead, right-click the Database node, and then click Restore Database.
2. Do not select the From database option under Source for restore. Instead, select the From device option.
3. Follow the instructions to complete the restore operation.
To know whether the version of SQL Server Management Studio that is installed on your computer is affected by this problem,
check whether the version of the Microsoft.SqlServer.SqlEnum.dll file matches one of the affected versions in the “Symptoms”section. Generally,the Microsoft.SqlServer.SqlEnum.dll file is in one of the following folders, depending on whether SQL Server is installed by using Windows on Windows (WOW) mode.
SQL Server 2008
drive:\Program Files\Microsoft SQL Server\100\SDK\Assemblies
drive:\Program Files (x86)\Microsoft SQL Server\100\SDK\Assemblies