If the computer running SQL Server 7.0 has more than four processors, queries that must allocate significant space for a heap (a table
without a clustered index), such as SELECT INTO, INSERT .. SELECT, may be slower in SQL Server 7.0 Service Pack 4 (SP4) than they did in SQL Server 7.0 SP2 or SQL Server 7.0 SP3. The query plans may be
the same across versions, and the I/O that is reported by SET STATISTICS
IO may also be the same, but the CPU utilization and elapsed time may be
higher in SQL Server 7.0 SP4.
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.
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, submit a request to 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.
The English version of this fix has the file attributes (or later) 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 tool in Control Panel.
Date Time Version Size File name
-----------------------------------------------------------------
04-Oct-2002 23:59 7.00.1081 28,944 Dbmssocn.dll
06-Sep-2002 23:55 7.00.1077 53,520 Distrib.exe
06-Sep-2002 23:55 7.00.1077 98,576 Logread.exe
05-May-2003 18:34 54,904 Opends60.dbg
05-May-2003 18:34 7.00.1093 155,920 Opends60.dll
06-Sep-2002 23:56 7.00.1077 250,128 Rdistcom.dll
06-Sep-2002 23:55 7.00.1077 82,192 Replmerg.exe
06-Sep-2002 23:56 7.00.1077 78,096 Replres.dll
17-Sep-2002 22:52 7,941 Securityhotfix.sql
06-Sep-2002 23:56 7.00.1077 160,016 Snapshot.exe
30-May-2003 04:21 59,214 Sp4_serv_uni.sql
15-Jan-2003 01:33 7.00.1085 344,064 Sqlagent.exe
06-Sep-2002 23:55 7.00.1077 45,056 Sqlcmdss.dll
16-May-2003 00:18 7.00.1094 2,629,632 Sqldmo.dll
16-May-2003 13:29 7.00.1094 81,920 Sqlmap70.dll
30-Jun-2003 22:29 7.00.1097 5,062,928 Sqlservr.exe
04-Oct-2002 23:59 7.00.1081 45,328 Ssmsso70.dll
16-May-2003 00:18 7.00.1094 24,848 Ssnmpn70.dll
26-Sep-2002 20:30 28,408 Ums.dbg
26-Sep-2002 20:27 7.00.1079 57,616 Ums.dll
16-May-2003 13:31 7.00.1094 151,552 Xpweb70.dll
Because of file dependencies, the most recent hotfix or feature that
contains these files may also contain additional
files.
To work around this problem, create a clustered index to overcome the impact on performance.
Note This workaround is not appropriate for some scenarios, including SELECT INTO.
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.