SQL Server Q&A

Symptoms
Consider the following scenario:On a Microsoft Windows-based computer, you apply Cumulative Update 3 for SQL Server 2008 Service Pack 1 by using a slipstream installation.For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
971491?(http://support.microsoft.com/kb/971491/) Cumulative update package 3 for SQL Server 2008 Service Pack 1You tryto uninstall this cumulative update after the slipstream installation.In this scenario, the Full-Text Search component is not completely rolled back to the SQL Server 2008 Service Pack 1 version.
To confirm whether you are encountering this issue, you can check the SQL Server Full-Text Key file (Sql_fulltext_keyfile.dll) in theSQL Server 2008 Installation folder. Typically, this file is located in the following folder:
%ProgramFiles%\Microsoft SQL Server\MSQL10.<Instance Name>\MSSQLIf this file has a file version that is greater than 10.00.2531.00, the Full-Text Search component is not completely rolled back to the SQL Server 2008 Service Pack 1 version.
Resolution
To work around this problem, follow these steps: In Control Panel, open Add or Remove Programs.
Note For Windows Vista or for Windows Server 2008, open Programs and Features.In the Currently installed programs list, click Microsoft SQL Server 2008, and then click Change/Remove.
Note For Windows Vista or Windows Server 2008, right-click Microsoft SQL Server 2008, and then click Change.In the SQL Server 2008 dialog box, click Remove.Select the appropriate instance or instances, and then click Next.In the Select Features window, select Full-Text Search from the Features list.Complete the Remove SQL Server 2008 wizard, as appropriate for your configuration.Click Start, point to All Programs, point to Microsoft SQL Server 2008, point to Configuration Tools, and then click SQL Server Installation Center.Click Installation, and then click New SQL Server stand-alone installation or add features to an existing installation.In the Browse For Folder dialog box, locate the SQL Server 2008 installationfolder that you want, and then click OK.In the SQL Server 2008 Setup window,click Next to move to the Installation Type phase.Click Add Features to an existing instance of SQL Server 2008, select the appropriate instance in the drop-down list, and then click Next to move to the Feature Selection phase.Select Full-Text Search from the Features list.Follow the steps in the Full-Text Search installation wizard.Note There is no workaround for cluster scenarios. To roll back the cumulative update, you must reinstall the clustered instance of SQL Server.

Symptoms
When running the Version Upgrade Wizard to upgrade SQL Server 6.x to SQL Server 7.0, if a database whose name is 30 characters long is excluded from the upgrade, the wizard generates an unhandled exception and stops running.
If Dr. Watson is set as the default debugger, an error message similar to the following will be displayed immediately after clicking the EXCLUDE button:

An application error has occurred
and an application error log is being generated.
upgrade.exe
Exception: privileged instruction (0xc0000065), Address: 0×007f1a80
Resolution
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in SQL Server 7.0 Service Pack 1. For more information, contact your primary support provider.

Symptoms
This article describes the following about this hotfix release:The issues that are fixed by this hotfix packageThe prerequisites for installing the hotfix packageInformation about whether you must restart the computer after you install the hotfix packageInformation about whether the hotfix package is replaced by any other hotfix packageInformation about whether you must make any registry changesThe files that are contained in the hotfix package
Resolution
When you execute a user-defined function in SQL Server 2005, you receive an error message. This problem occurs if you run the following statement before you execute the user-defined function:

SET FMTONLY ONYou receive a different error message, depending on the version of SQL Server 2005 that you have installed. If you use SQL Server 2005 Service Pack 1 (SP1), you may also experience other problems.
The original release version of SQL Server 2005When you execute the user-defined function in the original version of SQL Server 2005, you receive the followingerror message.

Msg 536, Level 16, State 5, Line 4
Invalid length parameter passed to the SUBSTRING function.
SQL Server 2005 SP1When you execute the user-defined function in SQL Server 2005 SP1, you experience the following problems:You receive the following error message:

Msg 109, Level 20, State 0, Line 0
A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 – The pipe has been ended.)The SQL Server service stops.The following access violation is logged in the SQL Server Errorlog file:

SqlDumpExceptionHandler: Process 53 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

Symptoms
In Microsoft SQL Server 2008, you restore a backup file that was created in SQL Server 2005. The database recovery process may take much longer in SQL Server 2008 than when you restore the same backup file in SQL Server 2005. This issue may occur when you restore any kind of backup file that was created in SQL Server 2005. This issue is most likely to occur when you try to restore a transaction log backup file that was created in SQL Server 2005.
Resolution
Cumulative update information for the release version of SQL Server 2008The fix for this issue was first released in Cumulative Update 4 for the release version of SQL Server 2008. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
963036?(http://support.microsoft.com/kb/963036/) Cumulative update package 4 for SQL Server 2008Note 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. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
956909?(http://support.microsoft.com/kb/956909/) The SQL Server 2008 builds that were released after SQL Server 2008 was released
Cumulative update information for SQL Server 2008 Service Pack 1The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 Service Pack 1. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
969099?(http://support.microsoft.com/kb/969099/) Cumulative update package 1 for SQL Server 2008 Service Pack 1Note 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. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365?(http://support.microsoft.com/kb/970365/) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Hotfix information 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 the problem described in this article. 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” section at the top of this Knowledge Base article. 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:
http://support.microsoft.com/contactus/?ws=support(http://support.microsoft.com/contactus/?ws=support)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.PrerequisitesNo prerequisites are required.Restart informationYou do not have to restart the computer after you apply this hotfix.Registry informationYou do not have to change the registry.Hotfix file informationThis hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of 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.SQL Server 2008, 32-bit version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSqlncli10.dll2007.100.1790.02,457,43230-Jan-200910:15×86Sqlncli_keyfile.dll2007.100.1790.013,65630-Jan-200908:21×86SQL Server 2008, x64-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSqlncli10.dll2007.100.1790.02,457,43230-Jan-200910:15×86Sqlncli10.dll2007.100.1790.03,155,81630-Jan-200913:02×64Sqlncli_keyfile.dll2007.100.1790.014,18430-Jan-200911:42×64SQL Server 2008, Itanium architecture version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSqlncli10.dll2007.100.1790.02,457,43230-Jan-200910:15×86Sqlncli10.dll2007.100.1790.06,346,60030-Jan-200918:05IA-64Sqlncli_keyfile.dll2007.100.1790.019,30430-Jan-200916:44IA-64

Symptoms
Consider the following scenario: In Microsoft SQL Server 2008, you use the DTExec.exe or DTExecUi.exe utility to run a SQL Server Integration Services (SSIS) package. You specify a configuration file by using the /ConfigFile option when you run the DTExec.exe or DTExecUi.exe utilities. The configuration file contains many configurations for objects in the package. However, the paths of the objects that are referenced in the configuration file do not exist in the current package. For example, you use a shared configuration file for many packages. However, some variables, connection managers, tasks, or other objects that are referenced in the shared configuration file are not contained in all packages. In this scenario, when you run the command, you receive the following error message:

Code: 0×80012017
Source: Package
Description: The package path referenced an object that cannot be found: “Path”. This occurs when an attempt is made to resolve a package path to an object that cannot be found.
DTExec: Could not import the configuration file Configuration File.
Additionally, if you specify the shared configuration file in Business Intelligence Design Studio (BIDS) when you design the SSIS package, instead of specifying the shared configuration file by using the /ConfigFile option, the package can run successfully. The SupressConfigurationWarnings package setting does not affect this issue.
Note This issue does not occur in SQL Server 2005 Integration Services. In SQL Server 2005 Integration Services, the command provides warning messages as expected for the invalid values. However, the command can run successfully.
Resolution
The fix for this issue was first released in Cumulative Update4 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
973602?(http://support.microsoft.com/kb/973602/LN/) Cumulative update package 4 for SQL Server 2008 Service Pack 1Note 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. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365?(http://support.microsoft.com/kb/970365/LN/) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was releasedMicrosoft SQL Server 2008hotfixes 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.

Symptoms
Consider the following scenario.You are running one of the following versions of SQL Server Management Studio:SQL Server 2005 Service Pack 2 (SP2) Management Studio, version 9.00.3325 to 9.00.3329
Note For example, you install SQL Server 2005 SP2 Cumulative Update 13, and the version of Management Studio is 9.00.3325.SQL Server 2005 Service Pack 3 (SP3) Management Studio, version 9.00.4220 to 9.00.4228
Note For example, you install SQL Server 2005 SP3 Cumulative Update 3, and the version of Management Studio is 9.00.4220.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.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.You use one of these versions of SQL Server Management Studio to connect to a SQL Server 2000 instance.You perform a backup operation on a database in the SQL Server 2000 instance.InSQL Server Management Studio, you right-click the database to perform a restore operation in this SQL Server 2000 instance.In this scenario, you receive the following error message:

Cannot show requested dialog.
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
Program Location:
at Microsoft.SqlServer.Management.Smo.Enumerator.Process(Object connectionInfo, Request request)
at Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseGeneral.GetBackupSetsFromHistory(String DatabaseName)
at Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseGeneral.comboDatabaseSource_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
at System.Windows.Forms.ComboBox.set_SelectedItem(Object value)
at Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseGeneral.InitializeProperties()
at Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseGeneral.OnHosted()
at Microsoft.SqlServer.Management.SqlMgmt.SqlManagementUserControl.SetSite(IServiceProvider sp)
at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.ProcessAllViews()
at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.InitializeUI(ViewSwitcherTreeView treeView, ISqlControlCollection viewsHolder, Panel rightPane)
at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm.InitializeForm(XmlDocument doc, IServiceProvider provider, ISqlControlCollection control)
at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm..ctor(XmlDocument doc, IServiceProvider provider)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ToolsMenuItem.OnCreateAndShowForm(IServiceProvider sp, XmlDocument doc)
at Microsoft.SqlServer.Management.SqlMgmt.RunningFormsTable.RunningFormsTableImpl.ThreadStarter.StartThread()
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Program Location:
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteReader(String sqlCommand)
at Microsoft.SqlServer.Management.Smo.ExecuteSql.GetDataReader(String query)
at Microsoft.SqlServer.Management.Smo.DataProvider.SetConnectionAndQuery(ExecuteSql execSql, String query)
at Microsoft.SqlServer.Management.Smo.ExecuteSql.GetDataProvider(StringCollection query, Object con, StatementBuilder sb, RetriveMode rm)
at Microsoft.SqlServer.Management.Smo.ExecuteSql.ExecuteWithResults(StringCollection query, Object con, StatementBuilder sb)
at Microsoft.SqlServer.Management.Smo.SqlObjectBase.FillData(ResultType resultType, StringCollection sql, Object connectionInfo, StatementBuilder sb)
at Microsoft.SqlServer.Management.Smo.SqlObjectBase.FillDataWithUseFailure(SqlEnumResult sqlresult, ResultType resultType)
at Microsoft.SqlServer.Management.Smo.SqlObjectBase.BuildResult(EnumResult result)
at Microsoft.SqlServer.Management.Smo.RestorePlan.GetData(EnumResult erParent)
at Microsoft.SqlServer.Management.Smo.Environment.GetData()
at Microsoft.SqlServer.Management.Smo.Environment.GetData(Request req, Object ci)
at Microsoft.SqlServer.Management.Smo.Enumerator.GetData(Object connectionInfo, Request request)
at Microsoft.SqlServer.Management.Smo.Enumerator.Process(Object connectionInfo, Request request)
Line 235: Incorrect syntax near ‘(‘.
Line 296: Incorrect syntax near ‘(‘.
Line 362: Incorrect syntax near ‘(‘.
Line 413: Incorrect syntax near ‘(‘.
Line 474: Incorrect syntax near ‘(‘.
Line 548: Incorrect syntax near ‘(‘.
Line 610: Incorrect syntax near ‘(‘.
Line 651: Incorrect syntax near ‘(‘.
Line 690: Incorrect syntax near ‘(‘. (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2282&EvtSrc=MSSQLServer&EvtID=170&LinkId=20476
Server Name: <Server Name>
Error Number: 170
Severity: 15
State: 1
Line Number: 235
——————————
Program Location:
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader()
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteReader(String sqlCommand)
Resolution
To resolve this problem, use the following table to find the appropriate method for your version of SQL Server.

Collapse this tableExpand this table
SQL Server releaseCumulative update (version of SQL Server)ResolutionSQL Server 2005 SP29.00.3325 to 9.00.3329Apply SQL Server 2005 SP2 Cumulative update package 15. SQL Server 2005 SP39.00.4220 to 9.00.4228Apply SQL Server 2005 SP3 Cumulative update package 5. The release version of SQL Server 200810.00.1806 to 10.00.1813Apply the individual hotfix for the 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 SP110.00.2714 to 10.00.2725Apply the individual hotfix for theSQL 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 informationSQL Server 2005 Service Pack 2 (SP2)Important You must install this hotfix if you are running SQL Server 2005 Service Pack 2 (SP2). The fix for this issue was first released in Cumulative Update15 for SQL Server 2005 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
972510?(http://support.microsoft.com/kb/972510/LN/) Cumulative update package 15 for SQL Server 2005 Service Pack 2Note 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 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
937137?(http://support.microsoft.com/kb/937137/LN/) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was releasedMicrosoft SQL Server 2005hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack. SQL Server 2005 Service Pack 3 (SP3)Important You must install this hotfix if you are running SQL Server 2005 Service Pack 3 (SP3). The fix for this issue was also released in Cumulative Update5 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
972511?(http://support.microsoft.com/kb/972511/LN/) Cumulative update package 5 for SQL Server 2005 Service Pack 3Note 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 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
960598?(http://support.microsoft.com/kb/960598/LN/) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was releasedMicrosoft SQL Server 2005hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack. SQL Server 2008Important You must use this fix if you are running the release version of SQL Server 2008.
The fix for this issue was first released in Cumulative Update 7. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
973601?(http://support.microsoft.com/kb/973601/) Cumulative update package 7 for SQL Server 2008Note 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. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
956909?(http://support.microsoft.com/kb/956909/) The SQL Server 2008 builds that were released after SQL Server 2008 was releasedSQL Server 2008 Service Pack 1Important You must use this fix if you are running SQL Server 2008 Service Pack 1.
The fix for this issue was first released in Cumulative Update4 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
973602?(http://support.microsoft.com/kb/973602/LN/) Cumulative update package 4 for SQL Server 2008 Service Pack 1Note 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. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365?(http://support.microsoft.com/kb/970365/LN/) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was releasedMicrosoft SQL Server 2008hotfixes 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 2005 Service Pack 3 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 the problem described in this article. 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” section at the top of this Knowledge Base article. 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:
http://support.microsoft.com/contactus/?ws=support(http://support.microsoft.com/contactus/?ws=support)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.PrerequisitesTo apply this hotfix, your computer must be running SQL Server 2005 Service Pack 3.Registry informationTo use the hotfix in this package, you do not have to make any changes to the registry.Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.File informationThe English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). The dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time (DST) bias. Additionally, the dates and times maychange when you perform certain operations on the files.SQL Server 2005, x86-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformAtxcore90.dll2005.90.4229.023,38429-Jul-200919:08×86Chsbrkr.dll12.0.9730.01,682,27223-Apr-200903:10×86Chtbrkr.dll12.0.9730.06,110,04823-Apr-200903:10×86Databasemailengine.dll9.0.4229.075,60829-Jul-200919:08×86Databasemailprotocols.dll9.0.4229.042,84029-Jul-200919:08×86Distrib.exe2005.90.4229.067,43229-Jul-200919:09×86Dtspipeline.dll2005.90.4229.0601,94429-Jul-200919:09×86Dtspipelineperf.dll2005.90.4229.030,04029-Jul-200919:09×86Fteref.dll12.0.9730.0446,46423-Apr-200903:11×86Infosoft.dll12.0.9730.0465,76023-Apr-200903:10×86Korwbrkr.dll12.0.9730.068,46423-Apr-200903:10×86Langwrbk.dll12.0.9730.0133,98423-Apr-200903:10×86Logread.exe2005.90.4229.0399,19229-Jul-200919:13×86Microsoft.sqlserver.maintenanceplantasks.dll9.0.4229.0292,69629-Jul-200919:13×86Microsoft.sqlserver.replication.dll2005.90.4229.01,625,43229-Jul-200919:13×86Microsoft.sqlserver.smo.dll9.0.4229.01,603,41629-Jul-200919:13×86Microsoft.sqlserver.smoenum.dll9.0.4229.0218,96829-Jul-200919:13×86Microsoft.sqlserver.sqlenum.dll9.0.4229.0919,38429-Jul-200919:13×86Microsoft.sqlserver.webservicetask.dll9.0.4229.096,08829-Jul-200919:13×86Msfte.dll12.0.9730.02,431,84023-Apr-200903:10×86Msftefd.exe12.0.9730.064,35223-Apr-200903:10×86Msftepxy.dll12.0.9730.093,02423-Apr-200903:10×86Msftesql.exe12.0.9730.093,02423-Apr-200903:10×86Msgprox.dll2005.90.4229.0196,95229-Jul-200919:13×86Msir5jp.dll5.0.2130.03,157,34423-Apr-200903:11×86Msmdlocal.dll9.0.4229.015,983,44829-Jul-200919:13×86Nlhtml.dll12.0.9730.0121,69623-Apr-200903:11×86Nls400.dll5.0.7112.012,287,32823-Apr-200903:11×86Query.dll12.0.9730.045,92023-Apr-200903:11×86Rdistcom.dll2005.90.4229.0644,44029-Jul-200919:14×86Repldp.dll2005.90.4229.0185,17629-Jul-200919:14×86Replmerg.exe2005.90.4229.0317,80029-Jul-200919:14×86Replprov.dll2005.90.4229.0551,25629-Jul-200919:14×86Replrec.dll2005.90.4229.0782,68029-Jul-200919:14×86Replsub.dll2005.90.4229.0405,33629-Jul-200919:14×86Snapshot.exe9.0.4229.011,09629-Jul-200919:15×86Sqlaccess.dll2005.90.4229.0346,96829-Jul-200919:15×86Sqlagent90.exe2005.90.4229.0345,94429-Jul-200919:15×86Sqlmergx.dll2005.90.4229.0191,32029-Jul-200919:15×86Sqlservr.exe2005.90.4229.029,279,06429-Jul-200919:16×86Sqltaskconnections.dll2005.90.4229.0104,28029-Jul-200919:16×86Sqlwep.dll2005.90.4229.087,38429-Jul-200919:16×86Thawbrkr.dll12.0.9730.0203,61623-Apr-200903:10×86Xmlfilt.dll12.0.9730.0195,42423-Apr-200903:11×86Xmlsub.dll2005.90.4229.0192,34429-Jul-200919:16×86SQL Server 2005, x64-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformAtxcore90.dll2005.90.4229.029,03229-Jul-200920:18×64Chsbrkr.dll12.0.9730.01,691,48823-Apr-200905:24×64Chtbrkr.dll12.0.9730.06,107,48823-Apr-200905:24×64Databasemailengine.dll9.0.4229.075,62429-Jul-200920:18×86Databasemailprotocols.dll9.0.4229.042,85629-Jul-200920:18×86Distrib.exe2005.90.4229.083,30429-Jul-200920:19×64Dtspipeline.dll2005.90.4229.01,065,83229-Jul-200920:19×64Dtspipelineperf.dll2005.90.4229.040,80829-Jul-200920:19×64Fteref.dll12.0.9730.0433,15223-Apr-200905:24×64Infosoft.dll12.0.9730.0618,84823-Apr-200905:24×64Korwbrkr.dll12.0.9730.099,16823-Apr-200905:24×64Langwrbk.dll12.0.9730.0234,33623-Apr-200905:24×64Logread.exe2005.90.4229.0525,16029-Jul-200920:21×64Microsoft.sqlserver.maintenanceplantasks.dll9.0.4229.0292,69629-Jul-200919:13×86Microsoft.sqlserver.replication.dll2005.90.4229.01,816,40829-Jul-200920:21×64Microsoft.sqlserver.smo.dll9.0.4229.01,603,43229-Jul-200920:21×86Microsoft.sqlserver.smoenum.dll9.0.4229.0218,98429-Jul-200920:21×86Microsoft.sqlserver.sqlenum.dll9.0.4229.0919,40029-Jul-200920:21×86Microsoft.sqlserver.webservicetask.dll9.0.4229.096,10429-Jul-200920:21×86Msfte.dll12.0.9730.03,813,72823-Apr-200905:24×64Msftefd.exe12.0.9730.096,60823-Apr-200905:24×64Msftepxy.dll12.0.9730.0124,76823-Apr-200905:24×64Msftesql.exe12.0.9730.0156,00023-Apr-200905:24×64Msgprox.dll2005.90.4229.0258,92029-Jul-200920:22×64Msir5jp.dll5.0.2130.03,418,97623-Apr-200905:24×64Msmdlocal.dll9.0.4229.015,983,44829-Jul-200919:13×86Nlhtml.dll12.0.9730.0189,28023-Apr-200905:24×64Nls400.dll5.0.7112.014,101,85623-Apr-200905:24×64Query.dll12.0.9730.065,90423-Apr-200905:24×64Rdistcom.dll2005.90.4229.0821,09629-Jul-200920:22×64Repldp.dll2005.90.4229.0185,17629-Jul-200919:14×86Repldp.dll2005.90.4229.0236,90429-Jul-200920:22×64Replmerg.exe2005.90.4229.0414,55229-Jul-200920:22×64Replprov.dll2005.90.4229.0750,95229-Jul-200920:22×64Replrec.dll2005.90.4229.01,010,53629-Jul-200920:22×64Replsub.dll2005.90.4229.0508,77629-Jul-200920:22×64Snapshot.exe9.0.4229.011,09629-Jul-200919:15×86Snapshot.exe9.0.4229.011,11229-Jul-200920:23×86Sqlaccess.dll2005.90.4229.0354,15229-Jul-200920:23×86Sqlagent90.exe2005.90.4229.0425,32029-Jul-200920:23×64Sqlmergx.dll2005.90.4229.0233,83229-Jul-200920:23×64Sqlservr.exe2005.90.4229.039,762,79229-Jul-200920:23×64Sqltaskconnections.dll2005.90.4229.0150,37629-Jul-200920:23×64Sqlwep.dll2005.90.4229.087,38429-Jul-200919:16×86Sqlwep.dll2005.90.4229.0120,16829-Jul-200920:23×64Thawbrkr.dll12.0.9730.0207,20023-Apr-200905:24×64Xmlfilt.dll12.0.9730.0266,59223-Apr-200905:24×64Xmlsub.dll2005.90.4229.0335,20829-Jul-200920:24×64SQL Server 2005, IA-64-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformAtxcore90.dll2005.90.4229.056,15230-Jul-200901:04ia64Chsbrkr.dll12.0.9730.01,880,92823-Apr-200904:13ia64Chtbrkr.dll12.0.9730.06,152,56023-Apr-200904:13ia64Databasemailengine.dll9.0.4229.075,62430-Jul-200901:04×86Databasemailprotocols.dll9.0.4229.042,85630-Jul-200901:04×86Distrib.exe2005.90.4229.0197,48030-Jul-200901:04ia64Dtspipeline.dll2005.90.4229.01,930,08830-Jul-200901:04ia64Dtspipelineperf.dll2005.90.4229.081,75230-Jul-200901:05ia64Fteref.dll12.0.9730.0433,15223-Apr-200904:13ia64Infosoft.dll12.0.9730.01,912,67223-Apr-200904:13ia64Korwbrkr.dll12.0.9730.0180,06423-Apr-200904:13ia64Langwrbk.dll12.0.9730.0330,59223-Apr-200904:13ia64Logread.exe2005.90.4229.01,100,13630-Jul-200901:07ia64Microsoft.sqlserver.maintenanceplantasks.dll9.0.4229.0292,69629-Jul-200919:13×86Microsoft.sqlserver.replication.dll2005.90.4229.02,530,64830-Jul-200901:07ia64Microsoft.sqlserver.smo.dll9.0.4229.01,603,41630-Jul-200901:07×86Microsoft.sqlserver.smoenum.dll9.0.4229.0218,96830-Jul-200901:07×86Microsoft.sqlserver.sqlenum.dll9.0.4229.0919,38430-Jul-200901:07×86Microsoft.sqlserver.webservicetask.dll9.0.4229.096,10430-Jul-200901:07×86Msfte.dll12.0.9730.07,081,84023-Apr-200904:13ia64Msftefd.exe12.0.9730.0170,86423-Apr-200904:13ia64Msftepxy.dll12.0.9730.0132,96023-Apr-200904:13ia64Msftesql.exe12.0.9730.0292,19223-Apr-200904:13ia64Msgprox.dll2005.90.4229.0542,04030-Jul-200901:08ia64Msir5jp.dll5.0.2130.03,821,92023-Apr-200904:13ia64Msmdlocal.dll9.0.4229.050,026,34430-Jul-200901:08ia64Nlhtml.dll12.0.9730.0293,21623-Apr-200904:13ia64Nls400.dll5.0.7112.014,747,50423-Apr-200904:13ia64Query.dll12.0.9730.0120,68823-Apr-200904:13ia64Rdistcom.dll2005.90.4229.01,888,08830-Jul-200901:09ia64Repldp.dll2005.90.4229.0185,17629-Jul-200919:14×86Repldp.dll2005.90.4229.0512,34430-Jul-200901:09ia64Replmerg.exe2005.90.4229.0954,71230-Jul-200901:09ia64Replprov.dll2005.90.4229.01,627,49630-Jul-200901:09ia64Replrec.dll2005.90.4229.02,147,17630-Jul-200901:09ia64Replsub.dll2005.90.4229.01,156,96830-Jul-200901:09ia64Snapshot.exe9.0.4229.011,09629-Jul-200919:15×86Snapshot.exe9.0.4229.011,11230-Jul-200901:09×86Sqlaccess.dll2005.90.4229.0348,50430-Jul-200901:09×86Sqlagent90.exe2005.90.4229.01,251,16030-Jul-200901:09ia64Sqlmergx.dll2005.90.4229.0443,75230-Jul-200901:09ia64Sqlservr.exe2005.90.4229.072,814,44030-Jul-200901:10ia64Sqltaskconnections.dll2005.90.4229.0314,21630-Jul-200901:10ia64Sqlwep.dll2005.90.4229.087,38429-Jul-200919:16×86Sqlwep.dll2005.90.4229.0217,43230-Jul-200901:10ia64Thawbrkr.dll12.0.9730.0250,72023-Apr-200904:13ia64Xmlfilt.dll12.0.9730.0439,64823-Apr-200904:13ia64Xmlsub.dll2005.90.4229.0578,90430-Jul-200901:10ia64
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” section at the top of this Knowledge Base article. 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 tocreate a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support(http://support.microsoft.com/contactus/?ws=support)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.PrerequisitesYou must have SQL Server 2008 Service Pack 1 installed before you apply this hotfix.Restart informationYou do not have to restart the computer after you apply this hotfix.Registry informationYou do not have to change the registry.Hotfix file informationThis 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.32-bit versionSQL Server 2008 Database Services Core Shared
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformCommanddest.dll2007.100.2727.0164,71213-Aug-200903:01×86Datacollectorenumerators.dll2007.100.2727.069,46413-Aug-200903:03×86Distrib.exe2007.100.2727.075,09613-Aug-200903:19×86Dtspipeline.dll2007.100.2727.0694,10413-Aug-200903:19×86Dtswizard.exe2007.100.2727.0804,71213-Aug-200903:19×86Exceldest.dll2007.100.2727.0173,40013-Aug-200903:35×86Excelsrc.dll2007.100.2727.0183,12813-Aug-200903:35×86Flatfiledest.dll2007.100.2727.0276,31213-Aug-200903:36×86Flatfilesrc.dll2007.100.2727.0283,99213-Aug-200903:36×86Iftsph.dll2007.100.2727.038,24813-Aug-200903:52×86Logread.exe2007.100.2727.0423,25613-Aug-200904:33×86Microsoft.sqlserver.dmf.dll10.0.2727.0296,79213-Aug-200904:39×86Microsoft.sqlserver.pipelinehost.dll10.0.2727.071,51213-Aug-200904:42×86Microsoft.sqlserver.sqlenum.dll10.0.2727.01,083,22413-Aug-200904:42×86Oledbdest.dll2007.100.2727.0173,91213-Aug-200904:52×86Oledbsrc.dll2007.100.2727.0186,72813-Aug-200904:52×86Rdistcom.dll2007.100.2727.0651,11213-Aug-200905:09×86Repldp.dll2007.100.2727.0191,33613-Aug-200905:10×86Replmerg.exe2007.100.2727.0341,35213-Aug-200905:10×86Snapshot.exe10.0.2727.013,14413-Aug-200906:18×86Sql_engine_core_shared_keyfile.dll2007.100.2727.013,65613-Aug-200904:19×86Sqllogship.exe10.0.2727.096,10413-Aug-200906:19×86Sqlmergx.dll2007.100.2727.0192,85613-Aug-200906:19×86Sqltaskconnections.dll2007.100.2727.0113,49613-Aug-200906:20×86Txdataconvert.dll2007.100.2727.0206,69613-Aug-200906:24×86SQL Server 2008 Database Services Core Instance
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformDatabasemailengine.dll10.0.2727.075,62413-Aug-200903:03×86Databasemailprotocols.dll10.0.2727.042,84013-Aug-200903:03×86Sql_engine_core_inst_keyfile.dll2007.100.2727.013,65613-Aug-200904:19×86Sqlaccess.dll2007.100.2727.0405,35213-Aug-200906:18×86Sqlagent.exe2007.100.2727.0367,96013-Aug-200906:18×86Sqlctr100.dll2007.100.2727.072,53613-Aug-200906:18×86Sqlscriptdowngrade.dll2007.100.2727.014,69613-Aug-200906:20×86Sqlscriptupgrade.dll2007.100.2727.03,378,00813-Aug-200906:20×86Sqlservr.exe2007.100.2727.042,723,16013-Aug-200906:20×86SQL Server 2008 Database Services Common Core
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformMicrosoft.analysisservices.adomdclient.dll10.0.2727.0546,66413-Aug-200904:33×86Microsoft.analysisservices.dll10.0.2727.01,316,69613-Aug-200904:34×86Microsoft.analysisservices.xmla.dll10.0.2727.0227,16013-Aug-200904:34×86Microsoft.sqlserver.sqlenum.dll10.0.2727.01,083,22413-Aug-200904:42×86Msgprox.dll2007.100.2727.0202,07213-Aug-200904:44×86Replprov.dll2007.100.2727.0575,32013-Aug-200905:10×86Replrec.dll2007.100.2727.0789,84813-Aug-200905:10×86Replsub.dll2007.100.2727.0410,96813-Aug-200905:10×86Sql_common_core_keyfile.dll2007.100.2727.013,65613-Aug-200904:19×86Xmlsub.dll2007.100.2727.0192,36013-Aug-200906:25×86x64-based versionSQL Server 2008 Database Services Core Shared
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformCommanddest.dll2007.100.2727.0247,14413-Aug-200906:17×64Datacollectorenumerators.dll2007.100.2727.093,54413-Aug-200906:20×64Distrib.exe2007.100.2727.086,88813-Aug-200906:26×64Dtspipeline.dll2007.100.2727.01,086,82413-Aug-200906:26×64Dtswizard.exe2007.100.2727.0800,61613-Aug-200906:26×64Exceldest.dll2007.100.2727.0260,45613-Aug-200906:34×64Excelsrc.dll2007.100.2727.0279,89613-Aug-200906:34×64Flatfiledest.dll2007.100.2727.0414,55213-Aug-200906:35×64Flatfilesrc.dll2007.100.2727.0424,79213-Aug-200906:35×64Iftsph.dll2007.100.2727.054,61613-Aug-200906:44×64Logread.exe2007.100.2727.0510,82413-Aug-200907:03×64Microsoft.sqlserver.dmf.dll10.0.2727.0296,80813-Aug-200907:07×86Microsoft.sqlserver.dmf.dll10.0.2727.0296,79213-Aug-200904:39×86Microsoft.sqlserver.pipelinehost.dll10.0.2727.071,51213-Aug-200907:08×86Microsoft.sqlserver.sqlenum.dll10.0.2727.01,083,22413-Aug-200904:42×86Oledbdest.dll2007.100.2727.0259,94413-Aug-200907:17×64Oledbsrc.dll2007.100.2727.0286,05613-Aug-200907:17×64Rdistcom.dll2007.100.2727.0789,86413-Aug-200907:26×64Repldp.dll2007.100.2727.0191,33613-Aug-200905:10×86Repldp.dll2007.100.2727.0229,73613-Aug-200907:26×64Replmerg.exe2007.100.2727.0408,40813-Aug-200907:26×64Snapshot.exe10.0.2727.013,14413-Aug-200906:18×86Snapshot.exe10.0.2727.013,14413-Aug-200908:11×86Sql_engine_core_shared_keyfile.dll2007.100.2727.014,18413-Aug-200906:57×64Sqllogship.exe10.0.2727.096,08813-Aug-200908:12×86Sqlmergx.dll2007.100.2727.0229,20813-Aug-200908:12×64Sqltaskconnections.dll2007.100.2727.0161,12813-Aug-200908:13×64Txdataconvert.dll2007.100.2727.0306,02413-Aug-200908:17×64SQL Server 2008 Database Services Core Instance
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformDatabasemailengine.dll10.0.2727.075,62413-Aug-200906:20×86Databasemailprotocols.dll10.0.2727.042,85613-Aug-200906:20×86Sql_engine_core_inst_keyfile.dll2007.100.2727.014,18413-Aug-200906:57×64Sqlaccess.dll2007.100.2727.0411,99213-Aug-200908:11×86Sqlagent.exe2007.100.2727.0428,88813-Aug-200908:11×64Sqlctr100.dll2007.100.2727.072,53613-Aug-200906:18×86Sqlctr100.dll2007.100.2727.0108,39213-Aug-200908:12×64Sqlscriptdowngrade.dll2007.100.2727.015,72013-Aug-200908:13×64Sqlscriptupgrade.dll2007.100.2727.03,377,51213-Aug-200908:13×64Sqlservr.exe2007.100.2727.057,629,03213-Aug-200908:13×64SQL Server 2008 Database Services Common Core
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformMicrosoft.analysisservices.adomdclient.dll10.0.2727.0546,66413-Aug-200907:03×86Microsoft.analysisservices.adomdclient.dll10.0.2727.0546,66413-Aug-200904:33×86Microsoft.analysisservices.dll10.0.2727.01,316,69613-Aug-200904:34×86Microsoft.analysisservices.xmla.dll10.0.2727.0227,17613-Aug-200907:04×86Microsoft.analysisservices.xmla.dll10.0.2727.0227,16013-Aug-200904:34×86Microsoft.sqlserver.sqlenum.dll10.0.2727.01,083,22413-Aug-200907:09×86Microsoft.sqlserver.sqlenum.dll10.0.2727.01,083,22413-Aug-200904:42×86Msgprox.dll2007.100.2727.0246,12013-Aug-200907:10×64Msgprox.dll2007.100.2727.0202,07213-Aug-200904:44×86Replprov.dll2007.100.2727.0575,32013-Aug-200905:10×86Replprov.dll2007.100.2727.0727,40013-Aug-200907:26×64Replrec.dll2007.100.2727.0789,84813-Aug-200905:10×86Replrec.dll2007.100.2727.0976,74413-Aug-200907:26×64Replsub.dll2007.100.2727.0410,96813-Aug-200905:10×86Replsub.dll2007.100.2727.0492,39213-Aug-200907:26×64Sql_common_core_keyfile.dll2007.100.2727.014,18413-Aug-200906:57×64Xmlsub.dll2007.100.2727.0192,36013-Aug-200906:25×86Xmlsub.dll2007.100.2727.0308,07213-Aug-200908:17×64Itanium-architecture versionSQL Server 2008 Database Services Core Shared
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformCommanddest.dll2007.100.2727.0557,92813-Aug-200910:15ia64Datacollectorenumerators.dll2007.100.2727.0190,29613-Aug-200910:17ia64Distrib.exe2007.100.2727.0205,67213-Aug-200910:24ia64Dtspipeline.dll2007.100.2727.02,020,69613-Aug-200910:24ia64Dtswizard.exe2007.100.2727.0800,60013-Aug-200910:24ia64Exceldest.dll2007.100.2727.0584,04013-Aug-200910:31ia64Excelsrc.dll2007.100.2727.0641,89613-Aug-200910:31ia64Flatfiledest.dll2007.100.2727.0951,12813-Aug-200910:33ia64Flatfilesrc.dll2007.100.2727.0975,19213-Aug-200910:33ia64Iftsph.dll2007.100.2727.088,42413-Aug-200910:41ia64Logread.exe2007.100.2727.01,124,71213-Aug-200911:01ia64Microsoft.sqlserver.dmf.dll10.0.2727.0296,79213-Aug-200911:04×86Microsoft.sqlserver.dmf.dll10.0.2727.0296,79213-Aug-200904:39×86Microsoft.sqlserver.pipelinehost.dll10.0.2727.071,52813-Aug-200911:06×86Microsoft.sqlserver.sqlenum.dll10.0.2727.01,083,22413-Aug-200904:42×86Oledbdest.dll2007.100.2727.0586,07213-Aug-200911:15ia64Oledbsrc.dll2007.100.2727.0653,67213-Aug-200911:15ia64Rdistcom.dll2007.100.2727.01,835,35213-Aug-200911:24ia64Repldp.dll2007.100.2727.0191,33613-Aug-200905:10×86Repldp.dll2007.100.2727.0522,60013-Aug-200911:24ia64Replmerg.exe2007.100.2727.0969,56013-Aug-200911:25ia64Snapshot.exe10.0.2727.013,14413-Aug-200906:18×86Snapshot.exe10.0.2727.013,14413-Aug-200912:09×86Sql_engine_core_shared_keyfile.dll2007.100.2727.019,30413-Aug-200910:54ia64Sqllogship.exe10.0.2727.096,08813-Aug-200912:10×86Sqlmergx.dll2007.100.2727.0428,37613-Aug-200912:10ia64Sqltaskconnections.dll2007.100.2727.0335,70413-Aug-200912:12ia64Txdataconvert.dll2007.100.2727.0674,64813-Aug-200912:15ia64SQL Server 2008 Database Services Core Instance
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformDatabasemailengine.dll10.0.2727.075,60813-Aug-200910:17×86Databasemailprotocols.dll10.0.2727.042,85613-Aug-200910:17×86Sql_engine_core_inst_keyfile.dll2007.100.2727.019,30413-Aug-200910:54ia64Sqlaccess.dll2007.100.2727.0398,68013-Aug-200912:09×86Sqlagent.exe2007.100.2727.01,205,59213-Aug-200912:09ia64Sqlctr100.dll2007.100.2727.072,53613-Aug-200906:18×86Sqlctr100.dll2007.100.2727.0135,01613-Aug-200912:10ia64Sqlscriptdowngrade.dll2007.100.2727.020,84013-Aug-200912:11ia64Sqlscriptupgrade.dll2007.100.2727.03,383,64013-Aug-200912:11ia64Sqlservr.exe2007.100.2727.0111,039,33613-Aug-200912:11ia64SQL Server 2008 Database Services Common Core
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformMicrosoft.analysisservices.adomdclient.dll10.0.2727.0546,64813-Aug-200911:01×86Microsoft.analysisservices.adomdclient.dll10.0.2727.0546,66413-Aug-200904:33×86Microsoft.analysisservices.dll10.0.2727.01,316,69613-Aug-200904:34×86Microsoft.analysisservices.xmla.dll10.0.2727.0227,17613-Aug-200911:01×86Microsoft.analysisservices.xmla.dll10.0.2727.0227,16013-Aug-200904:34×86Microsoft.sqlserver.sqlenum.dll10.0.2727.01,083,24013-Aug-200911:07×86Microsoft.sqlserver.sqlenum.dll10.0.2727.01,083,22413-Aug-200904:42×86Msgprox.dll2007.100.2727.0534,37613-Aug-200911:07ia64Msgprox.dll2007.100.2727.0202,07213-Aug-200904:44×86Replprov.dll2007.100.2727.0575,32013-Aug-200905:10×86Replprov.dll2007.100.2727.01,640,80813-Aug-200911:25ia64Replrec.dll2007.100.2727.0789,84813-Aug-200905:10×86Replrec.dll2007.100.2727.02,125,14413-Aug-200911:25ia64Replsub.dll2007.100.2727.0410,96813-Aug-200905:10×86Replsub.dll2007.100.2727.01,111,89613-Aug-200911:25ia64Sql_common_core_keyfile.dll2007.100.2727.019,30413-Aug-200910:54ia64Xmlsub.dll2007.100.2727.0192,36013-Aug-200906:25×86Xmlsub.dll2007.100.2727.0558,93613-Aug-200912:16ia64