MORE INFORMATION
Service Pack 1 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
May 25, 1999
(c) Copyright Microsoft Corporation, 1999
Contents
1.0 Introduction 1.1 Service Pack Versions
2.0 Downloading and Extracting SP1 2.1 Extracting Database Components SP1
2.2 Extracting
OLAP Services SP1
3.0 Service Pack Installation 3.1 Back Up Databases
3.2 Ensure the System Databases
Have Enough Free Space
3.3 Prepare Cluster Configurations
3.4 Stop
Applications Before Running Service Pack 1 Setup
3.5 Install Database
Components SP1
3.6 Install OLAP Services SP1
3.7 Restart
Services
3.8 Recluster a Cluster Configuration
3.9 Restart
Applications
4.0 Redistributing Database Components SP1 Client Components5.0 Documentation Notes 5.1 Upgrading Client-Only Computers After Installing
SP1
5.2 Rebuilding master After Installing SP1
5.3 Applying SP1 to a
Later Version
5.4 Installing SP1 on Windows NT 4.0, Terminal Server
Edition
5.5 SP1 and Replication
5.5.1 Installing SP1 on a Server Providing a Remote Distribution Database for Merge Publications
5.5.2 Upgrading to SP1 a Merge Publisher That Will Still Receive New Subscriptions from the Original Release of SQL Server 7.0
5.5.4 Running SP1 Replication with Earlier Versions of SQL Server
5.5.5 Updating Access 2000 (Jet 4.0) Merge Replication Subscribers
5.6 Change in Cursor Behavior
5.7 Changes in OLAP
Services
5.7.1 Improved Security
5.7.2 The German Version of SQL Server OLAP Services on Alpha
5.7.3 Migrating the Repository of a Remotely Administered OLAP Server
5.7.4 OLAP Services SP1 with the Korean Version of Windows NT
5.8 Data Transformation Services
5.8.1 Exporting to Oracle Databases
5.8.2 Using the DTS Test Feature
5.8.3 Changes to the Execute Package Dialog Box
5.8.4 Data Transformation Services Error Messages
5.8.5 Use of the SET keyword in Microsoft Visual Basic Scripts
5.8.6 Tests Now Support Global Variables and Lookups
5.9 SQL Server 7.0 and Exchange 5.5
5.10 The French Version
of SQL Server Books Online
5.11 SQL Server Clustering White Paper
1.0 Introduction
SP1 for SQL Server 7.0 and MSDE 1.0 is provided in two parts:
- Database Components SP1
Provides updates for the
database components of a SQL Server 7.0 or MSDE 1.0 installation,
including:
- Data engine.
- Database client utilities such as SQL Server Enterprise
Manager and osql. (SQL Server 7.0 only.)
- Database client connectivity components, such as the
OLE DB Provider for SQL Server, the SQL Server ODBC driver, and the client
Net-Libraries.
- OLAP Services SP1
Provides updates for the OLAP
Services components of a SQL Server 7.0 installation, including:
- OLAP Services.
- OLAP client components, such as OLAP Manager and the
OLE DB Provider for OLAP Services.
- Database client connectivity components, such as the
OLE DB Provider for SQL Server, the SQL Server ODBC driver, and the client
Net-Libraries.
These two parts of the service pack can be applied
independently:
- SQL Server 7.0 sites can use the Database Components SP1 to
upgrade their database components without upgrading their OLAP Services
components.
- SQL Server 7.0 sites can also use OLAP Services SP1 to
upgrade their OLAP Services components without upgrading their database
components.
- SQL Server 7.0 sites wanting to upgrade both their database
components and OLAP Services components must apply both parts of the service
pack.
- MSDE 1.0 sites can use the Database Components SP1 to
upgrade their MSDE 1.0 components.
Service Pack 1 Setup automatically detects which edition of SQL
Server 7.0 or MSDE 1.0 is present on the computer and only upgrades the
components present in that edition. The service pack will not attempt to
upgrade components present in SQL Server 7.0 Enterprise Edition unless it
detects the presence of the Enterprise Edition. When the service pack is
applied to a computer running MSDE 1.0, it will not attempt to upgrade
components that ship only with SQL Server 7.0.
Once the service pack
has been applied to a computer, there is no procedure to remove the service
pack. This applies to both Database Components SP1 and OLAP Services SP1.
At this time there are no fixes required for the version of
Microsoft English Query shipping with SQL Server 7.0.
The list of
the fixes contained in this service pack is in Microsoft Knowledge Base article
225019. Each fix listed in Q225019 has a link to the
Knowledge Base article describing the problem addressed by the fix. These
Knowledge Base articles are published at
http://support.microsoft.com/search/.
Select the option to search by article number and enter the article number
Q225019.
For the latest year 2000 information specific to SQL Server
7.0, refer to the SQL Server 7.0 information in the Microsoft Year 2000
Resource Center.
1.1 Service Pack Versions
If you are not sure which service pack you have installed on an
instance of the SQL Server 7.0 database engine or MSDE 1.0, you can verify the
version by issuing SELECT @@VERSION from osql, SQL Server Query Analyzer, or
isql. This table illustrates the relationship between the version string
reported by @@VERSION and the SQL Server 7.0 and MSDE 1.0 service packs:
|
7.00.623 | Original SQL Server 7.0 or MSDE 1.0
release |
7.00.699 | Database Components SP1 |
If you are not sure which edition of SQL Server 7.0 you
are running, or if you have connected to MSDE 1.0, the last line of output
returned by @@VERSION reports the edition to which you have connected:
- MSDE on Windows NT 4.0 (Build 1381: Service Pack
4)
- Desktop Edition on Windows NT 4.0 (Build 1381: Service Pack
4)
- Standard Edition on Windows NT 4.0 (Build 1381: Service
Pack 4)
- Enterprise Edition on Windows NT 4.0 (Build 1381: Service
Pack 4)
If you are not sure which service pack you have installed on an
instance of SQL Server 7.0 OLAP Services, you can verify the version in the
following manner:
- Select OLAP Services in the SQL Server 7.0 program group,
and then select OLAP Manager.
- Select the OLAP Servers node in the OLAP Manager tree
view.
- Select About Microsoft SQL Server OLAP Services in the OLAP
Manager Help menu. This table illustrates the relationship between the OLAP
Manager version information and the OLAP Services service packs:
|
7.0.1073 | Original SQL Server 7.0 OLAP Services
release |
7.0.1295 | OLAP Services SP1 |
2.0 Downloading and Extracting SP1
This service pack is distributed in two formats:
- On an SP1 compact disk.
- In four self-extracting files that can be downloaded from
the Internet:
Sql70sp1i.exe: Database Components SP1 for Intel-based computers
Sql70sp1a.exe: Database Components SP1 for Alpha-based computers
Sql70olapsp1i.exe: OLAP Services SP1 for Intel-based computers
Sql70olapsp1a.exe: OLAP Services SP1 for Alpha-based computers
The self-extracting files are used to build a set of
directories and files on your computer that are the same as those present on
the SP1 compact disk. The Setup process is then the same for both the SP1
compact disk and the extracted SP1 files.
If you downloaded SP1, you
need to extract the files to build the service pack directories before you can
run Setup.
NOTE: Several of the files in service packs are system files. Make sure
you have the 'Show all files' option turned on in either Windows NT Explorer or
Windows Explorer when working with service packs. To enable this option, on the
View menu click Options and then select the option.
2.1 Extracting Database Components SP1
To extract the Database Components SP1, place the self-extracting
file for your processor architecture into a directory on the computer running
SQL Server or MSDE. From that directory, execute the file. The self-extraction
program will prompt you for the name of the directory in which you want the
service pack files placed. For example, if you are running SQL Server or MSDE
on an Intel-based computer and have created a directory named C:\70sp1, copy
the file Sql70sp1i.exe to your computer, execute it, and provide the name of
the C:\70sp1 directory when prompted.
This will extract the service
pack files and place the two Microsoft Systems Management Server files in the
C:\70sp1 directory. Additionally, a subdirectory will be created for the
hardware platform (X86 or Alpha) where the remainder of the service pack files
will be placed.
You can rename the database installation directory;
however, you need to make sure that the directory name does not contain space
characters.
2.2 Extracting OLAP Services SP1
To extract the OLAP Services SP1, create a directory on your
computer to hold the OLAP Services SP1. Copy the self-extracting OLAP Services
file for your processor architecture into a directory on the computer running
OLAP Services. From that directory, execute the file. The self-extraction
program will prompt you for the name of the directory in which you want the
service pack files placed. For example, if you are running SQL Server on an
Alpha-based computer and have created a directory named C:\70sp1olap, copy the
file Sql70olapsp1a.exe to your computer, execute it, and provide the name of
the C:\70sp1olap directory when prompted. This will extract the service pack
files.
3.0 Service Pack Installation
You may use different series of the installation steps to install
the different parts of this service pack:
- To apply the entire service pack (both Database Components
SP1 and OLAP Services SP1), complete Steps 3.1 through 3.9.
- To apply only Database Components SP1 to a server running
both the server and client components, complete Steps 3.1 through 3.5, and 3.7
through 3.9.
- To apply only Database Components SP1 to a computer that is
running only the database client components, complete Steps 3.4, 3.5, and 3.7
through 3.9.
- To apply only OLAP Services SP1, complete only Steps 3.4,
3.6, 3.7, and 3.9. Use the same steps for computers running only the client
OLAP Services components, or computers running both the client and server OLAP
Services components.
If OLAP Services SP1 is applied to a server, but not to a
client accessing the server, the client will not benefit from the OLAP Services
SP1 fixes and it will not be able to use the cell-level security introduced in
OLAP Services SP1.
If you install OLAP Services SP1 on a computer,
and subsequently reinstall the original version of SQL Server 7.0 OLAP
Services, you must install OLAP Services SP1 again.
You can also use
Systems Management Server to install SP1 automatically on multiple computers
running Windows NT(R) Server. The Smssq701.pdf file is a Package Definition
File (PDF) that automates the creation of a SQL Server package in Systems
Management Server. The SQL Server package can then be distributed and installed
on computers running Systems Management Server. The Smssq701.cmd file is a
batch file that detects the platform of the computer and runs the appropriate
version of the Setup program.
3.1 Back Up Databases
As a precaution, back up all of your databases, including the
master and
msdb databases. Installation of the service pack does not make
modifications to user databases, but it does make modifications to the
master and
msdb databases.
3.2 Ensure the System Databases Have Enough Free Space
If the autogrow option is on for both the
master and
msdb databases in the SQL Server or MSDE system on which you apply
SP1, you may skip this step. You can verify this in SQL Server 7.0 by
connecting to SQL Server from SQL Server Enterprise Manager, right clicking the
icon for the database, and selecting Properties. Verify that the
Automatically grow file check box is selected. You can verify this in MSDE by issuing
these SQL statements:
sp_helpdb master
sp_helpdb msdb
In the output of these statements, verify that the growth column is not
0.
If the autogrow option is not on for either
master or
msdb databases, the databases that cannot autogrow must have at least
500 KB of free space. To verify this, run the
sp_spaceused system stored procedure in the context of the
master or
msdb database. If the unallocated space figure in either database is
less than 500 KB, increase the size of the database. Follow the instructions in
the topic "Expanding the Database" in SQL Server Books Online.
3.3 Prepare Cluster Configurations
Before installing Database Components SP1 to SQL Server 7.0,
Enterprise Edition in a clustered environment, ensure that the group containing
Microsoft Distributed Transaction Coordinator (DTC) is owned by the node on
which DTC was first installed. If the group is not owned by this node, Service
Pack 1 Setup will display a DTC setup error prompting you to correct the
problem and then retry the setup. Correct the problem by moving the group to
the node on which DTC was first installed.
If SQL Server, Enterprise
Edition is running in a clustered configuration, it must be unclustered before
you can apply Database Components SP1. To uncluster SQL Server, select the
Failover Cluster Wizard in the SQL Server 7.0 program group. When prompted,
insert your original SQL Server, Enterprise Edition compact disc and follow the
instructions displayed by the wizard. Do this on all nodes of the Microsoft
Windows NT(R) cluster where SQL Server has been clustered.
All SQL
Server 7.0 instances operating in a cluster must be upgraded to SP1 before they
are reclustered.
Additional information about running SQL Server in
a clustered environment is available in a white paper. For more information
about the white paper, see section 5.11 of this Readme.txt file.
3.4 Stop Applications Before Running Service Pack 1 Setup
Before running Service Pack 1 Setup to apply Database Components
SP1, shut down the following services and applications:
- The Microsoft Search, MSDTC, MSSQLServer,
MSSQLServerOLAPService, and SQLServerAgent services.
- Microsoft Transaction Server, Microsoft Message Queue
Server, and Microsoft COMTI.
- All applications, including Windows NT Control
Panel.
Before running Service Pack 1 Setup to apply OLAP Services SP1,
shut down the services and applications listed above; however, you must not
stop the MSSQLServer service if you have migrated your OLAP Services repository
to SQL Server.
If installing in a Windows NT cluster, ensure these
applications and services are stopped on all nodes in the cluster.
Also stop SQL Server Service Manager if it is running. Right click on the
minimized SQL Server Service Manager icon on the right side of the task bar,
and then select
Exit.
3.5 Install Database Components SP1
Run the Setup.bat script from either:
- The directory containing the extracted service pack files
from either Sql70sp1i.exe or Sql70sp1a.exe.
- The service pack directory on the SQL Server 7.0 SP1
compact disc.
Setup.bat starts an Installshield dialog box that prompts you
for information such as whether to use SQL Server authentication or Windows NT
authentication. If you choose SQL Server authentication you must supply the
Setup program with the password for the sa login. If you choose Windows NT
authentication you must be running Setup while logged on to Microsoft
Windows(R) using a Microsoft Windows login account that is in the sysadmin
fixed server role of the instance of SQL Server or MSDE you are upgrading.
The setup process then replaces the existing SQL Server or MSDE
files with the service pack files. Setup also runs several .sql script files to
update system stored procedures.
The DTC installer installs a new
version of Microsoft Distributed Transaction Coordinator on your system. In a
clustered environment, it does this on all nodes of the Windows NT cluster.
Setup places a record of the actions it performed in the Sqlsp.log
file in the Temp directory of the computer on which it was run.
3.6 Install OLAP Services SP1
Review section 3.0, Service Pack Installation, to see which steps
are required to install the OLAP Services SP1 if that is all you want to
install.
To install OLAP Services SP1, run Setup.exe from either:
- The Msolap\Install subdirectory in the directory containing
the extracted OLAP Services service pack files from either Sql70olapsp1i.exe or
Sql70olapsp1a.exe.
- The Msolap\Install directory on the SP1 compact
disc.
Setup.exe starts an Installshield dialog box that prompts you
for information and then completes the installation.
3.7 Restart Services
When Setup has completed, it may prompt you to restart the
system. After the restart, or after Setup completes without requesting a
restart, use the Services application in Control Panel to make sure the
Microsoft Search, MSDTC, MSSQLServer, MSSQLServerOLAPService, and
SQLServerAgent services are running.
3.8 Recluster a Cluster Configuration
If you have applied this service pack in a Windows NT cluster
configuration, recluster SQL Server. You must apply this service pack to all
SQL Server 7.0 instances that will be included in the cluster before
reclustering.
To recluster SQL Server, select the Failover Cluster
Wizard in the SQL Server 7.0 program group. When prompted by the wizard, insert
your original SQL Server, Enterprise Edition compact disc and follow the
instructions displayed by the wizard. Do this on all nodes of the Windows NT
cluster containing instances of SQL Server that you want to include in the
cluster.
3.9 Restart Applications
Restart the applications you closed before running Service Pack 1
Setup.
4.0 Redistributing Database Components SP1 Client Components
This service pack includes a new file which contains updated
Microsoft Data Access Components (MDAC) for redistribution.
Developers of OLE DB or ODBC applications use the file Mdac_typ.exe to
distribute the client connectivity components required to connect the
application to various data sources:
- The MDAC core components, such as the core components for
ADO, OLE DB, and ODBC.
- Various OLE DB providers and ODBC drivers, including the
OLE DB Provider for SQL Server and the SQL Server ODBC driver.
The licensing requirements and instructions for using
Mdac_typ.exe are contained in a file named Mdacredist.txt.
Developers wanting to distribute the versions of the OLE DB Provider for SQL
Server and the SQL Server ODBC driver that shipped with the original version of
SQL Server 7.0 or MSDE 1.0 should use the versions of Mdac_typ.exe and
Mdacredist.txt that shipped with:
- SQL Server 7.0
- MDAC 2.1
- MDAC 2.1 SP1
- Access 2000 or Office 2000
Service Pack 1 for SQL Server 7.0 and MSDE 1.0 includes a new
self-extracting file, Sqlredis.exe, and a new version of Mdacredist.txt. These
files are in the Database Components SP1. By default, when Sqlredis.exe is
executed it:
- Executes the Mdac_type.exe from MDAC 2.1 SP1. This installs
the MDAC 2.1 SP1 core components and the versions of the SQL Server and MSDE
client connectivity components that shipped with the original versions of SQL
Server 7.0 and MSDE 1.0.
- Replaces the SQL Server and MSDE client connectivity
components with the new versions from the Database Components SP1.
If you only wish to install the updated Database Components SP1
client connectivity components, use the following syntax at the command prompt:
sqlredis.exe /C:"setupre.exe MDAC=0 -s -SMS"
You may redistribute the Sqlredis.exe file under the same terms and
conditions noted in the Mdacredist.txt file which accompanies this service
pack.
5.0 Documentation Notes
This section discusses issues that affect sites running SP1, but
are not the result of fixes contained in the service pack.
Changes
in behavior introduced by fixes are documented in the "FIX" Knowledge Base
article published for each fix. Knowledge Base article Q225019 is a list of
fixes contained in the service pack. Each fix is linked to its corresponding
Knowledge Base article. You can access the articles from
http://support.microsoft.com/search/.
Select the option to specify an article number, and specify Q225019. Follow the
links to the "FIX" Knowledge Base articles to see the details of each fix.
5.1 Upgrading Client-Only Computers After Installing SP1
Users sometimes first install only the SQL Server client
components on a computer, then later add a Standard, Enterprise, or Desktop
Edition of the database server to the computer. This is done by running the
Setup program from the SQL Server compact disk. If the client components on the
computer have already been upgraded to SP1, the SQL Server Setup program will
fail with the error:
You cannot install a version that
is older (7.00.623) than the version on your machine (7.00.699). Uninstall the
older version.
Use the following procedure to add a Standard,
Enterprise, or Desktop Edition of the database server to a client computer
running the SP1 client components:
- Copy the Bcp.exe file from your SQL Server 7.0 Setup
compact disk to the client computer, overlaying the SP1 version of Bcp.exe in
the C:\Mssql7\Binn directory.
- Run the Setup program from your SQL Server 7.0 Setup
compact disk to install the server components.
- Run Database Components SP1 Service Pack 1 Setup by
following the instructions in this Readme.txt file to upgrade all SQL Server
database components on the computer to SP1.
NOTE: Upgrading a client to a Standard or Enterprise Edition of the
server requires the purchase of an appropriate server license. Client computers
covered by either a Standard or Enterprise SQL Server Client Access License
(CAL) can install a Desktop Edition server.
5.2 Rebuilding master After Installing SP1
Rebuilding the master database after applying SP1 removes the SP1
updates to the system tables. Users who rebuild their master database after
applying SP1 should reapply Database Components SP1 after the rebuild.
5.3 Applying SP1 to a Later Version
If you attempt to upgrade a SQL Server installation whose
database engine executable files are the same date or newer than the ones
provided with Database Components SP1, Service Pack 1 Setup will terminate with
the following message:
Setup has detected newer SQL
Server components than those available in the Service Pack. Setup will not
continue.
Usually this indicates that SP1 (or higher) has already
been applied to the SQL Server instance on the server and an upgrade is not
required.
Possible exceptions to this are customers who have
received from their SQL Server support vendor a special SQL Server build that
is newer than the SP1 build, and have applied that build to a system that was
not first upgraded to SP1. These customers should contact their SQL Server
support vendor to request information about the upgrade process.
5.4 Installing SP1 on Windows NT 4.0, Terminal Server Edition
Service Pack 1 introduces support for running SQL Server on
Windows NT Server 4.0, Terminal Server Edition. The original release of SQL
Server 7.0 is not supported on Windows NT 4.0, Terminal Server Edition.
Service Pack 1 requires that Windows NT Server 4.0, Terminal Server
Edition, Service Pack 4 be applied to a computer running Terminal Server
Edition before SQL Server is installed. This service pack is specific to
Terminal Server Edition and is separate from the Windows NT Server 4.0 Service
Pack 4. For more information on the Terminal Server Edition service pack, see
the Microsoft service pack download Web page at
http://support.microsoft.com/support/downloads/.
Use these steps to install SQL Server 7.0 and SP1 on Windows NT
Server 4.0, Terminal Server Edition:
- Ensure that Windows NT 4.0, Terminal Server Edition,
Service Pack 4 has been applied.
- Use the Services application in Control Panel to stop the
Terminal Server Licensing Service.
- Copy the SQL Server ODBC files to the System32 directory on
the computer running Terminal Server Edition. Place the SQL Server 7.0 compact
disk in the computer. Copy the files from the ODBC directory on the compact
disk to the C:\Winnt\System32 directory of the server:
- For Alpha-based servers, copy the files in the
Alpha\ODBC directory. Do not copy the Symbols subdirectory.
- For Intel-based servers, copy the files in the X86\ODBC
directory. Do not copy the Symbols subdirectory.
- Use the Services application in Control Panel to restart
the Terminal Server Licensing Service.
- Install SQL Server 7.0 using the SQL Server 7.0 compact
disk. SQL Server cannot be installed by a thin client, it must be installed
using the console on the computer running Terminal Server Edition. You cannot
install SQL Server on a computer running Terminal Server Edition using the
autorun setup window that is displayed when you insert the SQL Server compact
disk. Close the window, and then open the Add/Remove Programs application in
Control Panel. Select the Install button and follow the instructions. Run the
Setup program directly from the SQL Server 7.0 compact disk:
- For Intel-based servers, run
X86\Setup\Setupsql.exe.
- For Alpha-based servers, run
Alpha\Setup\Setupsql.exe.
Follow the instructions displayed by SQL Server Setup. If
you want to install a database directly on the computer running Terminal Server
Edition, you can run a full SQL Server setup to install both the client
communications components and the database engine. If you only need to give
applications running on the same computer with Terminal Server Edition the
ability to connect to SQL Server databases on other servers, you can install
only the client connectivity components. For more information on doing full
server or client connectivity-only setups, see Running SQL Server Setup in SQL
Server 7.0 Books Online. - Apply SP1 by following the instructions in this file. SP1
must be installed from the console of the computer running Terminal Server
Edition. Also, you must run the Service Pack 1 Setup (Setup.bat) from the
Add/Remove Programs application in Control Panel.
5.5 SP1 and Replication
We recommend you apply this service pack to all 7.0 participants
in your replication topology: Publisher, Distributor, and Subscribers. We
recommend that you deploy SP1 across the replication topology in this sequence:
- Distributor (if separate from the Publisher)
- Publisher
- Subscriber
NOTE: In most cases, especially in merge replication, the Distributor
and Publisher are on the same server, and are upgraded at the same time.
In merge replication, the distribution database is simply used to
store agent history. Typically, the distribution database in a merge
replication topology resides on the same computer as the published database.
However, it is possible to also have a remote distribution database for merge
replication at sites that want to centralize agent history logging.
You may not be able to immediately upgrade all the servers in a replication
topology, so replication operations generally work unaffected between servers
running the original version of SQL Server 7.0 and SP1 participants. These are
the exceptions and considerations:
5.5.1 Installing SP1 on a Server Providing a Remote
Distribution Database for Merge Publications
If you upgrade to SP1 a server with a remote distribution
database for merge publications, you must also upgrade to SP1 each of the merge
replication Publishers that use that distribution database. This requirement
ensures optimal delivery of data changes from the associated merge replication
Publishers by any Merge (Push) Agents running on the Distributor.
5.5.2 Upgrading to SP1 a Merge Publisher That Will Still
Receive New Subscriptions from the Original Release of
SQL Server 7.0
To allow new merge replication Subscribers from servers that do
not have SP1 installed, you must add the optional parameter "-70Subscribers" to
each Snapshot Agent job. This ensures complete initial synchronization of any
new SQL Server 7.0 merge Subscribers that do not have SP1 installed.
If a Subscriber running the original version of SQL Server has already received
the initial synchronization, that Subscriber will continue to be able to merge
data even without this parameter. However, if the subscription is dropped and
re-created, or the subscription has to be completely reinitialized, the
parameter would be necessary. The preferred solution would be to upgrade the
Subscriber to SP1 rather than use the parameter. If you want to be sure, you
can add the parameter until you are confident all Subscribers have moved to
SP1.
5.5.3 Installing SP1 on a Merge Replication Subscriber
If you upgrade a SQL Server merge replication pull Subscriber to
SP1, you must also upgrade each of its associated merge replication Publishers
to SP1. This ensures optimal delivery of data changes from the associated merge
replication Publishers by any Merge (Pull) Agents running on the Subscriber.
This is best accomplished using the Distributor-Publisher-Subscriber deployment
sequence stated above.
5.5.4 Running SP1 Replication with Earlier Versions of SQL Server
There are no known differences in how SP1 works with SQL Server
6.0 or 6.5 Publishers and Subscribers compared to how the original SQL Server
7.0 works with the earlier versions.
5.5.5 Updating Access 2000 (Jet 4.0) Merge Replication Subscribers
In order for Jet-based Access 2000 Merge Subscribers to take
advantage of improvements in SP1, you will need to copy the following Database
Components SP1 files to your workstations running Access 2000:
- x86\binn\replres.dll
- x86\binn\replrec.dll
- x86\binn\replprov.dll
- x86\jet\msrpjt40.dll
Copy each file to the \Program Files\Common Files\Microsoft
Shared\Database Replication folder on the system drive in the workstation.
NOTE: These steps are not necessary if MSDE 1.0 is serving as the
Access 2000 Merge Subscriber. In this case, simply apply Database Components
SP1 following the instructions in this Readme.
5.6 Change in Cursor Behavior
In the original releases of SQL Server 7.0 and MSDE 1.0, a
rollback closes all open cursors except for cursors that meet all of the
following conditions:
- CURSOR_CLOSE_ON_COMMIT is OFF.
- The cursor is static.
- The cursor has finished populating its work
table.
To increase compatibility with earlier versions of SQL Server,
Database Components SP1 changes this so that cursors are only closed on
rollback if one of the following is true:
- CURSOR_CLOSE_ON_COMMIT is ON.
- An asynchronously populated cursor is currently
populating.
5.7 Changes in OLAP Services
These changes in OLAP Services are introduced in OLAP Services
SP1:
5.7.1 Improved Security
Security for OLAP Services has been enhanced in OLAP Services
SP1. Cell-level security is now supported. For information about using
cell-level security, see the white paper "Cell-Level Security," available at
http://www.microsoft.com/sql/productinfo/olap.htm.
5.7.2 The German Version of SQL Server OLAP Services on Alpha
The German version of OLAP Services Setup now works only on Intel
platforms. The German version of SQL Server 7.0 OLAP Services is not supported
on Alpha platforms. If you attempt to run the German version of the OLAP
Services SP1 Setup program on an Alpha computer, Setup terminates with an
error. Use the US English version of OLAP Services SP1 on Alpha computers
running German-version software.
If you installed the German version
of SQL Server 7.0 OLAP Services on an Alpha computer running the German version
of Windows NT, you must install the US English version of OLAP Services SP1.
5.7.3 Migrating the Repository of a Remotely Administered OLAP Server
After you install OLAP Services SP1 on a server, you can migrate
the repository using the instance of OLAP Manager on the server. You cannot use
OLAP Manager from another computer remotely administering the server to perform
this task.
5.7.4 OLAP Services SP1 with the Korean Version of Windows NT
If you use SQL Server 7.0 OLAP Services on a server running the
Korean version of Windows NT, you will not be able to connect to your OLAP
server if you install Database Components SP1, OLAP Services SP1, or separately
install the MDAC 2.1 SP1.
After you install any of these service
packs on the server running OLAP Services, you must run Olaprepair.exe on the
server to be able to connect to your OLAP server. Olaprepair.exe is located in
the English version of OLAP Services SP1. Running this utility may require you
to restart your server twice.
5.8 Data Transformation Services
These changes in Data Transformation Services (DTS) are
introduced in Database Components SP1:
5.8.1 Exporting to Oracle Databases
When exporting to Oracle using the DTS Export Wizard, if you
create the destination tables using DTS, DTS will create the case-sensitive
tables using quotation marks around the owner and table names. This is required
to support owner or table names that are keywords or contain spaces. If your
names are not keywords and do not contain spaces, and you want to remove the
quotation marks, delete them in the DTS Copy Tables dialog box.
5.8.2 Using the DTS Test Feature
The DTS Test feature has improved functionality and now supports
global variables and lookups. However, the DTS Test feature does not support
data lineage columns in Microsoft ActiveX(R) scripts in Test mode.
5.8.3 Changes to the Execute Package Dialog Box
When you execute a DTS package in the DTS Import Wizard, DTS
Export Wizard, or DTS Designer, extra columns have been added to the Execute
Package dialog box to display start time, end time, and duration. These new
columns are not available if the package is run with a user password.
In addition, transfer notification information is provided during
package execution.
5.8.4 Data Transformation Services Error Messages
DTS Error messages have been improved and now supply OLE DB
provider-specific information, and information on the operation that failed.
5.8.5 Use of the SET keyword in Microsoft Visual Basic Scripts
ActiveX assignment of object references to DTS global variables
in Visual Basic, Scripting Edition scripts now follows standard Visual Basic
SET syntax in all cases.
Use SET when you want to assign an object
reference; otherwise, the default value of the object will be assigned.
If a global variable contains an object reference, use both SET and
.Value to reassign the object reference. For example, in the statements below:
- The first statement assigns a reference to the connection
object to the global variable x.
- The second statement sets the variable o to a reference to
the connection object.
- The third statement sets the variable o to a reference to a
global variable that contains a reference to the connection object.
SET DTSGlobalVariables("x") =
CreateObject("ADO.Connection")
SET o = DTSGlobalVariables("x").Value
SET o = DTSGlobalVariables("x")
5.8.6 Tests Now Support Global Variables and Lookups
The DTS user interface has a test option in two dialog boxes:
- In the Data Transformation Properties dialog box, click the
Transformations tab and right-click on one of the lines mapping the column
transformations. The menu presented has a test menu item.
- Double-click on an ActiveX Script Trask Properties dialog
box and select the test button.
These tests now support global variables and lookups. The tests
are not supported on lineage columns.
5.9 SQL Server 7.0 and Exchange 5.5
You must explicitly configure memory usage in SQL Server if you
run both a SQL Server 7.0 and a Microsoft Exchange version 5.5 server on the
same computer. SQL Server will not operate properly if you leave the SQL Server
minimum dynamic memory option set at the default value of 0.
To
address a known memory issue that occurs when the two products are run
together, you must set the SQL Server 7.0 minimum dynamic memory (or
sp_configure min server memory option) to the amount of memory required to
support the peak processing load of SQL Server. In this environment, SQL Server
will not acquire enough memory to reach the maximum dynamic memory setting (or
sp_configure max server memory option). Instead, SQL Server will usually run
with the amount of memory specified in the minimum dynamic memory option. The
minimum dynamic memory setting must therefore be sufficient to run SQL Server
when it is operating at high capacity.
To determine the memory
needed by SQL Server, monitor the memory used by SQL Server under the following
conditions:
- If your database is running in production, monitor the SQL
Server memory usage when the system is running at high capacity.
- If your SQL Server applications were developed in-house,
run stress tests while monitoring the memory used by SQL Server.
- If your SQL Server applications were developed by a third
party, you may need to consult the application documentation or vendor to
determine its impact on SQL Server memory.
For more information on monitoring SQL Server memory, see
"Monitoring Memory Usage" in SQL Server Books Online.
For more
information on setting the SQL Server memory options, see "Server Memory
Options" in SQL Server Books Online.
5.10 The French Version of SQL Server Books Online
The original French version of SQL Server Books Online had an
incorrect table of contents. The French version of the Database Components SP1
includes a self-extracting file that contains a new French SQL Server Books
Online file with a corrected table of contents.
To install the
corrected French version of SQL Server Books Online:
- Copy the file Sqlbolfr.exe from the service pack directory
to an empty folder on your computer.
- Execute Sqlbolfr.exe to extract the file
Sqlbol.chm.
- Copy this new Sqlbol.chm to the C:\Mssql7\Books directory.
This will overwrite the incorrect version of the file.
5.11 SQL Server Clustering White Paper
There is a white paper named "How to Install SQL Server 7.0,
Enterprise Edition, on Microsoft Cluster Server: Step by Step Instructions."
This white paper supplements the clustering information in SQL Server Books
Online. For more information about the white paper, see
http://www.microsoft.com/sql/prodinfo/previousversions/whitepapers.mspx.