Random page. Wiki Guidelines. Community portal. KB Archive. Tools What links here. Related changes. Special pages. Printable version. Permanent link. Page information. View source.
Twee's return on TikTok. Windows Windows. Most Popular. New Releases. Desktop Enhancements. Networking Software. Trending from CNET. Developer's Description By Microsoft. Full Specifications. What's new in version 1. Release December 5, For more information about the RepositoryUser role, see Section 5.
If the Analysis Services Data folder is located on a computer other than the one on which the Analysis server is running, you must modify the permissions on the folder after running SP3a Setup. You must contact the application provider for a patch file that can be used to upgrade these instances of MSDE For instructions on how to determine if an instance of MSDE falls into this category, see section 2. Note Microsoft does not support configurations where there are more than 16 instances of the database engine on one computer.
This includes instances of SQL Server 6. You must run Setup from the command prompt and specify parameters to install or upgrade any instance of MSDE. For more information on the required parameters, see sections 3. If problems are encountered, restart Setup from the local computer. In SP3 and later versions of Setup, Setup manages the. Run InstMsi When prompted, reboot the computer.
The behavior of MSDE setup has been changed in SP3a so that the default settings result in a more secure configuration. If no application running on another computer will connect to your instance of MSDE , the instance has no need for network support and it is prudent to turn off a resource that is not being used. If you disable the network support when installing an instance of MSDE SP3a, you can later reconfigure the instance to enable the support. For more information about disabling and restoring network access, see Microsoft Knowledge Base article You should assign a strong password to the sa login, even when upgrading an existing instance, unless the application using your instance of MSDE depends in some way on a null sa password.
Even if the instance of MSDE is running in Windows Authentication mode, the sa login becomes immediately active if the instance is ever switched to Mixed Mode. A null, blank, simple, or well-known sa password could be used for unauthorized access. You have defined Windows Authentication logins for all users who need to connect to the instance. MSDE is designed to be distributed with applications and installed by the setup program of the application. MSDE does not have an interactive setup program.
The setup mechanisms for MSDE are designed to be called by an application setup utility, where any required interaction with the end-user is handled by the application setup. The setup utility is usually called by an application setup utility, but can also be run from a command prompt window. The MSDE setup utility does not have a graphical user interface through which a user can control the behavior of the utility. Instead, this utility accepts a set of parameters that define what actions the utility should take.
A set of Windows Installer merge modules. Developers can control the configuration of the installed instance by specifying installation package properties that correspond to the MSDE setup utility parameters. The setup parameters can be specified in one of two ways: On the command line. In an. You must enclose the values for MSDE Setup parameters in double quotation marks if the value specified has special characters, such as blanks.
Otherwise the quotation marks are optional. When you specify the name of an MSDE For example, if you specify SqlRun MSIPath is the path to the folder holding the.
In SP3a, the Net-Libraries are disabled. For more information, see section 5. If you are a developer incorporating the MSDE merge modules.
If you do not specify a path as part of the name, the log file is created in the current folder. The examples in this section assume that the sa login has a strong password. For more information about the sa login password, see section 3. Important If you use an. Note When upgrading Desktop Engine on a computer running Windows 98 or Windows Millennium Edition, the instance of Desktop Engine that you are upgrading must be stopped before starting Setup.
The examples in this section will install a new instance of MSDE SP3a that has been configured with its network connectivity disabled. These examples install instances using the defaults for all configuration items such as collation and file locations. For more information about the configuration parameters that you can specify with setup, see "Customizing Desktop Engine Setup. To install a new instance of Desktop Engine Open a command prompt window. Important If you are using an. Important Always specify a strong password for the sa login, even when the instance is configured to use Windows Authentication Mode.
The examples in this section will upgrade an existing instance of MSDE 1. MSDE 1. To upgrade from Desktop Engine version 1. Caution The use of blank passwords is strongly discouraged.
Only patch files produced by the application vendor will contain the proper product codes. Application vendors who elect to instruct their customers to apply SP3a directly should develop a set of instructions customized to the needs of their customers.
When Setup completes, it may prompt you to restart the system. After the system restarts or after Setup completes without requesting a restart , use the Services application in Control Panel to make sure that any services you stopped before applying the service pack are now running.
The following information applies only to SQL Server components that are part of a failover cluster. To install the service pack on a failover cluster If any resources have been added with dependencies on SQL Server resources, those dependencies must either be removed or taken offline before you install SP3a.
If you do not do this, the installation of SP3a may cause those dependent resources to fail over. Run the service pack from the node that owns the group containing the virtual server that you are going to upgrade.
This installs the service pack files on all nodes in the failover cluster. In the Setup dialog box, type the name of the virtual server that you are upgrading. Keep all nodes of the cluster online during setup. This ensures that the upgrade is applied to each node of the cluster. If you removed dependencies or took resources offline in Step 1 above, add back the dependencies or bring the resources back online.
Note Setup might require rebooting of the failover cluster nodes. This replaces the files that were in use during setup with the updated files. If you are upgrading a default non-clustered instance of SQL Server to a virtual server, first, you must upgrade the default non-clustered instance to a virtual instance, and then apply SP3a.
For additional information on installing SP3a on a failover cluster, see Knowledge Base article If you need to rebuild a node in the failover cluster, perform the following steps Rebuild the node in the failover cluster.
Run SP3a Setup on the newly added node. This will update to SP3a only the binaries on the new node. Note If you run Setup from the node where the virtual server is running, you must reapply SP3a to all the nodes. You must also rerun the database upgrade scripts. Fail over to the newly upgraded node. Repeat steps 1 and 2 until all instances in the cluster are upgraded.
For replication topologies based on merge replication or transactional replication with updating Subscribers, you must upgrade the Subscriber after the Publisher and Distributor. Note In many cases, especially in merge replication, the Distributor and Publisher are on the same server and are upgraded at the same time. For replication topologies based on merge replication or transactional replication with updating Subscribers that include one or more servers that act as both a Subscriber and a Publisher or Distributor , you might need to quiesce the system in other words, stop all updates and upgrade all servers simultaneously.
The following table includes servers that both publish and subscribe to publications that allow updates at the Subscriber. As noted earlier, you must follow the upgrade order Distributor, Publisher, Subscriber for topologies that allow updates at the Subscriber. This order requires you to upgrade Server A first for the merge publication and Server B first for the transactional publication with updating Subscribers.
In this case, you must quiesce the system and upgrade the servers simultaneously. Important Before you upgrade to SP3a, ensure that the Windows account under which the SQL Server service runs is a member of the sysadmin fixed server role. You must do this because replication distribution databases are upgraded under the context of the SQL Server service account.
After upgrading to SP3a, you should remove the Windows account from the sysadmin role. If you are using merge replication and the Distributor is located on another computer or database instance a remote Distributor , after applying SP3a you must generate a new snapshot.
SP3a introduces a change in the requirements for attaching or restoring replication databases. SP3a Setup upgrades user databases that are members of a replication topology. If any of the databases that are members of a replication topology are non-writable, to apply SP3a to those databases you must make them writable, and then reapply SP3a Setup. For information about reapplying SP3a, see Section 3. An existing backup scheme that accounts for replication allows you to restore a database to a known point after the SP3a upgrade in case of a failure.
After applying SP3a, a log or full database backup is recommended for any user database that is included in a replication topology. This way, if a replication database fails, you do not have to reapply SP3a after the database is restored.
The following information applies only to SQL Server components that are part of a replication topology. In general, you can ignore this warning and setup will continue. However, if any of the non-writable databases listed in the Setup log are members of a replication topology, you must make those databases writable and reapply SP3a Setup to that instance of SQL Server Note During installation, Setup makes no distinction between non-writable databases and databases that are offline or in a suspect state.
If a database or filegroup is in any of these conditions during setup, you must reapply the service pack. Apply or reapply the service pack. Note MDAC updates are not uninstalled. To revert to the pre-SP3a versions of SQL Server components, you must have back ups of the master , msdb , and model databases taken prior to installing SP3a.
Note If any of the databases are involved in replication, you must disable publishing. Click the Publication Databases tab. Clear the check box for each database that is involved in replication. This allows the databases to be detached. Uninstall SQL Server.
Restore the databases master , msdb , and model from the last backup that was created before applying SP3a. This automatically attaches any user databases that were attached at the time the backup was created, assuming that the location of the data files has not changed. Attach any user databases that were created after the last backup of the master database. Configure replication if necessary.
Note If you did not backup this registry key, you must follow the process documented in Microsoft Knowledge Base article If databases or filegroups that are part of a replication topology and were read-only during the initial application of SP3a are made writable. To reapply SP3a, follow the steps in Section 3. This section documents additional service pack installation considerations that apply only in special cases. The corresponding batch file to use is Sql2kdef.
You must change the instance name in this. This file can be used for installation without any modifications. The following considerations relate to unattended installations: Run unattended installations using Windows Authentication whenever possible.
If you must run an unattended setup using SQL Server Authentication; for example if you are running an unattended setup of SP3a on a computer running Windows 98 or Windows Millennium Edition, you should not include a password for the sa login in the. When running an unattended installation of SP3a, you must manually set the following setup switches that correspond to the Backward Compatibility Checklist dialog box or the unattended installation will fail.
Unattended setup switch Description UpgradeMSSearch This switch is required to address the required rebuild of full-text catalogs. If Full Text Search is enabled, you must set this switch to 1.
If you are applying SP3a to a master or target server, you must set this switch to 1. To enable cross-database ownership chaining, set this switch to 1. During an unattended installation, if Setup detects any non-writable databases or filegroups, that information is written to the Setup log and the unattended installation continues.
When Sqlredis. This installs the MDAC 2. For more information, see 5. You can redistribute the Sqlredis. This section covers issues that can occur in addition to new features that are available when you run SP3a.
This section is not meant to be a description of all of the fixes provided in SP3a. For a complete list of these fixes, see Microsoft Knowledge Base article These system files are necessary for sorting Chinese, Japanese, or Korean characters. For more information about running Sqlredis. Note You do not have to reapply Sqlredis. Hash teams have been removed. In addition, removing hash teams makes SQL Server more stable. In rare cases, the removal of hash teams can cause a query to be processed more slowly.
Analyze such queries to see whether creating more suitable indexes will return query performance to its previous level. This switch must be used in conjunction with the affinity mask option. With this service pack, you can configure systems that are enabled for Virtual Interface Architecture VIA to bind the SQL Server connections from certain network cards to a processor or a set of processors. If you have encountered SQL Server bug as documented in Microsoft Knowledge Base Article , this service pack will only prevent future occurrences of unexpected results because of data modifications.
This allows developers to build enterprise-class reliability and advanced database features into their desktop applications. An attractive alternative to using the Microsoft Jet database, MSDE is designed primarily to provide a low-cost option for developers who need a database server that can be easily distributed and installed with a value-added business solution.
Downloadable file name: SQL2kdesksp3.
0コメント