© Copyright Microsoft Corporation, 2003. All rights reserved.
The SQL Server documentation team cannot answer technical support questions, but welcomes your suggestions and comments about this readme documentation. You can quickly and directly send e-mail feedback using the link below. Please send your feedback in English.
To submit written feedback about this document, click here: Submit feedback.
1.0 Introduction
1.2 Identify the Current Version of SQL Server 2000 Analysis Services
1.3 Determine How to Remove Analysis Services SP4
1.4 Verify the Version of Microsoft Data Access Components
1.5 Additional Important Information About SP4
1.6 Updates to SQL Server Books Online Are Available
2.0 Where to Find and Download SQL Server 2000 SP4
2.1 Choosing the Correct Language
2.2 Downloading Analysis Services SP4
2.3 Extracting the Analysis Services SP4 Files
2.4 Download and Extraction Phase Guidelines
3.1 Prepare for Analysis Services SP4 Installation
3.2 Install Analysis Services SP4
3.4 Install on a Failover Cluster
3.5 Uninstall Analysis Services SP4
3.6 Reapply Analysis Services SP4
4.0 Additional Installation Information
4.2 Redistributing SP4 Data Access Components
5.1 Analysis Services Enhancements
5.2 Error Reporting
5.3 Meta Data Services Enhancements
5.4 Serviceability Enhancements
This Readme file describes how to use the Analysis Services part of Microsoft® SQL Server™ 2000 Service Pack 4 (SP4) to upgrade an existing installation of Analysis Services.
The general process for installing SP4 is as follows:
SQL Server 2000 SP4 has four parts. You use each part to apply SP4 to different SQL Server components:
All SQL Server service packs are cumulative. SQL Server SP4 includes the fixes delivered in SP1, SP2, SP3, and SP3a.
Analysis Services SP4 can only be used on installations of SQL Server 2000 Analysis Services. You must use the other parts of SP4 to apply SP4 to the other SQL Server 2000 components, such as the database engine, Desktop Engine, or SQL Server 2000 (64-bit). Separate Readme files describe the Database Components SP4, the MSDE 2000 SP4, and SQL Server 2000 64-bit. The other Readme files are available at this Microsoft Web site.
This section describes changes to system requirements and system related issues that affect the installation of Database Engine SP4. General information on system requirements for SQL Server 2000 can be found at this Microsoft Web site.
An Analysis Services SP4 installation will fail if either of the following security policies has been set to Do not allow installation:
If you use the Do not allow installation setting, you must change it to Silently succeed before installing Analysis Services SP4. If necessary, you can return the policy to its previous setting after the installation is complete.
Note Do not allow installation is not the default setting for these security policies.
To set security policies
Before running Setup, you must identify the version of the instance of Analysis Services 2000 that you want to upgrade.
To identify the installed version of Analysis Services 2000
| Analysis Services Version | Build Number in Help About |
| SQL Server 2000 Analysis Services Original Release | 8.0.194 |
| Analysis Services SP1 | 8.0.382 |
| Analysis Services SP2 | 8.0.534 |
| Analysis Services SP3 or SP3a | 8.0.760 |
| Analysis Services SP4 | 8.0.2039 |
Before you use Analysis Services SP4 to upgrade an existing instance of Analysis Services, it is advisable to plan how to return the instance to its previous state in case that becomes necessary later. To revert to the build that you were running before you installed Analysis Services SP4, you must first uninstall the instance of Analysis Services SP4 and then reinstall that instance. Second, if you ran a previous SQL Server 2000 service pack or applied any hotfixes, you must reapply the service pack and hotfixes to the instance that is being reverted.
To prepare for a later return to pre-SP4 SQL Server Analysis Services, you must back up the registry key HK_LOCAL_MACHINE\Software\Microsoft\OLAP Server and all of its subkeys before you install Analysis Services SP4. When you later uninstall Analysis Services SP4, you must delete this registry key and restore the pre-SP4 version from the backup.
Note Updates to MDAC 2.8 SP1 that are made during Analysis Services SP4 setup cannot be uninstalled. For more information, see Section 3.5 Uninstall Analysis Services SP4, and also Section 1.4 Verify the Version of Microsoft Data Access Components.
Analysis Services SP4 Setup determines whether to upgrade an installed version of Microsoft Data Access Components (MDAC) to MDAC 2.8 SP1:
Note If a computer on which Analysis Services SP4 is installed is later upgraded to a newer operating system platform, the version of MDAC installed by SP4 is no longer present.
Note See Microsoft Knowledge Base article 301202 for instructions on determining the version of MDAC on your computer.
When Analysis Services SP4 installs MDAC 2.8 SP1, the MDAC language version is the same as the language version of Analysis Services SP4. If you want to maintain a language version of MDAC that is different from that of Analysis Services SP4, you must download and install the intended language version of MDAC 2.8 SP1 before you run Analysis Services SP4 Setup. You can download language-specific versions of MDAC 2.8 SP1 from this Microsoft Web site.
MDAC 2.8 SP1 includes an upgrade to MSXML 3.0 SP7. MDAC 2.81 also updates SQLXML 1.0, which shipped with Microsoft SQL Server 2000. This service pack does not install or update SQLXML 3.0. If your application requires SQLXML 3.0, you must download and install it from this Microsoft Web site. For more information about MDAC 2.8 SP1, see this Microsoft Web site. For more information about MDAC versions, see Knowledge Base article 822758. Fixes included in MDAC 2.8 SP1 are documented in Knowledge Base article 884930.
Note Prerelease versions of SQL Server 2000 SP4 installed a prerelease version of MSXML 3.0 SP7. If you installed a prerelease version of SQL Server 2000 SP4, it is recommended that you download and install the final release version of MSXML 3.0 SP7 from this Microsoft Web site.
A list of the fixes contained in this service pack is be provided in Microsoft Knowledge Base article 888800. Each fix listed in 888800 has a link to a Knowledge Base article about the problem that a particular fix addresses. Follow the links to individual Knowledge Base articles to see information about each fix.
Any information relevant to SQL Server 2000 Service Pack 4 that was not available in time to be included in this Readme file will be published in Microsoft Knowledge Base article 884525.
The Knowledge Base articles cited in this Readme are available in the Microsoft Support Knowledge Base.
To find an article in the Knowledge Base
All publicly issued SQL Server 2000 SP3a and SQL Server 2000 (64-bit) security bulletins have been addressed in SP4.
If you received a SQL Server 2000 hotfix after December 2, 2004, that hotfix is unlikely to be included in SP4. Contact your primary support provider about obtaining the same hotfix for SQL Server 2000 SP4.
SQL Server 2000 SP4 includes serviceability enhancements that enable you to uninstall future hotfixes. For more information, see Section 5.4 Serviceability Enhancements.
SQL Server Books Online is the primary user documentation for Analysis Services 2000. Books Online is periodically updated with fixes and new information. Current versions of Books Online are at the following locations:
Samples for the SQL Server 2000 database engine that were updated for SP3 and SP3a are available from this Microsoft Web site.
Before you prepare to download and extract SQL Server 2000 SP4, read Download and Extraction Phase Guidelines later in this section. SQL Server 2000 SP4 is distributed in the following ways:
If you have a SQL Server 2000 SP4 CD, you can upgrade an instance of Analysis Services 2000 to Analysis Services 2000 SP4 by using the Analysis Services 2000 SP4 files directly from the CD.
Note LLL represents a designator that varies by language.
If you do not have a SQL Server SP4 CD, you can download SQL2000.AS-KB884525-SP4-x86-LLL.exe and then run it to extract the Analysis Services SP4 files onto your computer. SQL2000.AS-KB884525-SP4-x86-LLL.exe creates a set of folders and files on your hard disk that have the same organization as the Analysis Services folders and files on the SP4 CD. After this file extraction phase is complete, you can install Analysis Services SP4 from the folders on your disk.
SQL Server 2000 Analysis Services service packs are language-specific. To upgrade an instance of Analysis Services, you must obtain the service pack that has the same language as your instance. You get the service pack either on a SQL Server 2000 SP4 CD or by downloading the Analysis Services SP4 files. For example, if you upgrade a version of Analysis Services that uses Japanese, you must get the Japanese version of Analysis Services SP4.
If you are unsure of the language of an instance of Analysis Services:
| Language Registry Value (in Hexadecimal) | Language Registry Value (in Decimal) | Language of That Instance |
| 0x00000404 | 1028 | Traditional Chinese |
| 0x00000407 | 1031 | German |
| 0x00000409 | 1033 | English |
| 0x0000040a | 1034 | Spanish |
| 0x0000040c | 1036 | French |
| 0x00000410 | 1040 | Italian |
| 0x00000411 | 1041 | Japanese |
| 0x00000412 | 1042 | Korean |
| 0x00000804 | 2052 | Simplified Chinese |
Use the following instructions when downloading Analysis Services SP4.
To download Analysis Services SP4:
After you download the self-extracting file that contains the installation package, you must extract the Analysis Services SP4 files:
When you download and extract Analysis Services SP4 installation files from the Internet, use the following guidelines:
Note When you extract the service pack to a network shared directory, the path to the folder that you specify is relative to the folder from which you ran SQL2000.AS-KB884525-SP4-x86-LLL.exe.
To install Analysis Services SP4, use the installation instructions in the following sections. Review the material in Section 1.0 Introduction before you install Analysis Services SP4. The installation stages for Analysis Services SP4 are as follows:
You must do the following before you install Analysis Services SP4:
Before you install Analysis Services SP4, back up your Analysis Services databases by making a copy of the Microsoft Analysis Services\Data folder, which is installed by default under C:\Program Files. If you have not migrated your Analysis Services repository to SQL Server, make a backup copy of the file Msmdrep.mdb, which is located in the Microsoft Analysis Services\Bin folder. Also, save your Analysis Server registry entries.
To back up registry settings on a computer running on Windows 2000:
To back up registry settings on a computer running on Windows XP or Windows 2003 Server:
If you have migrated your Analysis Services repository to SQL Server, back up the database that contains the repository before you install SP4. For more information, see Section 3.5 Uninstall Analysis Services SP4.
You should stop all applications and services, including Control Panel, Add and Remove Programs, SQL Server 2000 Reporting Services, SQL Server 2000 Notification Services, and all applications that make connections to Analysis Services, before installing Analysis Services SP4.
You can apply Analysis Services SP4 without first shutting down services, but then some services will not start again without a system reboot. If you do not shut down services, you are prompted to reboot the computer when Setup is complete. If you do not reboot the system, the following services fail to start:
You can reduce the likelihood that you will need to restart your computer after you install Analysis Services SP4. To reduce this likelihood, stop the preceding services and applications before you run Setup.
You cannot stop the services in a clustered environment. For more information, see Section 3.4 Install on a Failover Cluster.
The following information applies only to Analysis Services.
To install Analysis Services SP4, run Setup.exe from one of the following locations:
Setup then performs the following tasks:
One or more of the following tasks may be required after you upgrade Analysis Services to SP4.
When Setup completes, it may prompt you to restart the system. Section 3.1.2 Stop Services and Applications Before You Run Analysis Services SP4 Setup provides guidelines on when a restart is required. 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 you applied the service pack are now running. Services you might have stopped before you applied the service pack include services such as DTC and the Microsoft Search and MSSQLServerOLAPService services.
Restart the applications you closed before you ran the service pack Setup program.
After you install Analysis Services SP4 you must also upgrade any computers that are used for remote administration to at least SP3. Otherwise, you receive the following error message when you attempt to connect remotely through Analysis Manager:
Unable to connect to the registry on the server (server_name), or you
are not a member of the OLAP Administrators group of this server.
Beginning with SP3, Meta Data Services has added a new dedicated role named RepositoryUser, which can be used to access and update repository information in the msdb database. The RepositoryUser role has create, read, update, delete, and execute permissions on the msdb repository. The public role has been replaced by this new role and no longer has permissions on this repository. If the following conditions are met, you must add the OLAP Administrators group to the RepositoryUser role so that members of this group can access the repository after the service pack is applied:
Note The addition of the RepositoryUser dedicated role also affects remote servers that access the Meta Data Services repository on a server that has been upgraded to SP3 or SP3a. You must also add remote server logins to the RepositoryUser role.
Note You must add the OLAP Administrators group to the RepositoryUser role before you restore a Meta Data Services repository that was backed up prior to upgrading to SP3 or SP3a; otherwise, the restore operation will fail.
For more information about the RepositoryUser role, see Section 5.3.3 New RepositoryUser Role for Accessing Repository Information.
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 you run SP4 Setup. For more information, see Section 5.1.10 Permissions Must be Modified on a Remote Data Folder.
The following information applies only to SQL Server 2000 components that are part of a failover cluster.
To install SP4 on an Analysis Services cluster
Note The Analysis Services SP4 installation must modify permissions on the Data folder that is located on the shared disk. The shared disk is only accessible to the active node at all times.
To be able to return to pre-SP4 versions of SQL Server 2000 Analysis Services, you must back up the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server registry subkey before you install SP4. For more information, see Section 3.1.1 Back Up Your Analysis Services Databases and Repository.
Note If you did not back up this registry key, you must follow the process documented in Microsoft Knowledge Base article 330244.
To return to a pre-SP4 version of Analysis Services 2000
Note When you uninstall SP4, MDAC updates are not uninstalled. For more information, see Section 1.4 Verify the Version of Microsoft Data Access Components.
You must reapply Analysis Services SP4 if the following occurs:
To reapply SP4, follow the steps in Section 3.0 Service Pack Installation.
This section documents additional service pack installation considerations that apply only in special cases.
When you start an installation of Analysis Services SP4 from the command prompt, you can specify to have the setup options written to the setup.iss file. This .iss file can be used later to run an unattended installation of Analysis Services SP4. Execute the following at the command prompt to run an attended installation that generates the setup.iss file in the default (Windows system) directory:
start /wait setup -rExecute the following at the command prompt to run an unattended installation of Analysis Services SP4:
start /wait setup -s -f1c:\windows\setup.issNote By default, Setup looks for the setup.iss file in the same directory as setup.exe.
For more information about performing unattended installations, see the topic "Setup Parameters and Silent Installation" in SQL Server 2000 Books Online.
The following considerations relate to unattended installations:
| Unattended setup switch | Description |
|---|---|
| EnableErrorReporting | (Optional) This switch is used to enable Error Reporting. To enable error reporting, set this switch to 1. For more information, see Section 5.2 Error Reporting. |
Database Components SP4 includes the self-extracting file Sqlredis.exe. When Sqlredis.exe runs, it:
You can redistribute the Sqlredis.exe file under the terms and conditions noted in the Redist.txt file that accompanies Analysis Services SP4.
This section covers issues that can occur after you apply Analysis Services SP4, and new features that are available in SP4. These issues apply when you run the service pack to upgrade from SQL Server 2000, SQL Server 2000 SP1, SQL Server 2000 SP2, SQL Server 2000 SP3, or SQL Server 2000 SP3a. This section is not meant to be a description of all of the fixes provided in SP4. For a complete list of these fixes, see Microsoft Knowledge Base article 888800.
Any information relevant to SQL Server 2000 Service Pack 4 that was not available in time to be included in this Readme file will be published in Microsoft Knowledge Base article 884525.
This section discusses enhancements to SQL Server 2000 Analysis Services that are included with SP4.
Introduced in SP1
When a remote partition is created on a local server that has SP1 or later installed on it, the remote server must use a domain user account that has full-access permissions to the parent cube on the local server. Any user account that is a member of the OLAP Administrators group on the local server has full-access permissions.
In addition, if the local server has SP1 or a later version installed on it, the remote server also must have SP1 or later installed on it so that the local server can create or administer remote partitions.
Introduced in SP1
Analysis Services SP1 and later versions include updated versions of the following client redistributable setup programs:
These files are located in the \Msolap\Install\PTS path of the service pack installation directory.
Note PTSFull.exe includes MDAC; PTSLite.exe does not.
Use these updated client setup programs in your applications to prevent or solve client setup issues that you may encounter when using Analysis Services and Microsoft Office XP.
Note When using Analysis Services with Office XP, upgrading the client is highly recommended.
Introduced in SP1
Analysis Services SP1 and later versions include support for the addition of third-party data mining algorithm providers. For more information about developing a data mining algorithm provider, see the OLE DB for Data Mining Resource Kit, which includes the code for a sample data mining algorithm provider.
Introduced in SP1
If you install SQL Server 2000 Analysis Services on a computer that contains updated client files, such as SQL Server 2000 SP1 or Office XP, you must apply Analysis Services SP1 or a later version to ensure that the client works properly and that you can browse through cubes.
Introduced in SP3
Virtual cubes can now reference up to 255 cubes. However, any virtual cube that references more than 64 cubes is not visible to any version of Microsoft PivotTable® Service released before SP3.
Introduced in SP3
Local cubes now support the intrinsic member property DESCRIPTION for measures and dimensions. The DESCRIPTION keyword, added to the CREATE CUBE Multidimensional Expressions (MDX) statement, is used to support the use of the DESCRIPTION intrinsic member property. The following BNF clauses describe the changes made to the CREATE CUBE statement:
<dimensions def> :: = DIMENSION <dimension name> [<time def>]
[DIMENSION_STRUCTURE <sub_type>] [<hidden def>]
[DESCRIPTION <description expression>]
<options def> <comma> <hierarchy def list>
<measures def> :: = MEASURE <measure name> <measure function def>
[<measure format def>] [<measure type def>] [<hidden def>]
[DESCRIPTION <description expression>] [<comma> <measures def>]Introduced in SP3
SP3 introduced a new PivotTable Service connection string property, Restricted Client. This property can be used to prevent PivotTable Service from using local cube functionality. Any attempt to use a statement that involves the creation or use of a local cube, such as the CREATE CUBE, CREATE GLOBAL CUBE, and CREATE SESSION CUBE statements, raises an error. Additionally, any statement that involves deep recursion, such as a series of nested DRILLDOWN statements, raises an error if the statement can potentially overflow the statement stack maintained by PivotTable Service.
This property stores a string value. If the value is set to any string value starting with the characters Y, y, T, or t, or any string value that can be converted to a numeric value other than 0, PivotTable Service is restricted as described earlier. If the value is set to any other string value, including an empty string (""), or any string value that can be converted to a numeric value equal to 0, PivotTable Service is unrestricted. The default value for this property is 0.
Note This property does not restrict the use of local data mining models.
Introduced in SP3
Setting the Safety Options property to DBPROP_MSMD_SAFETY_OPTIONS_ALLOW_SAFE also prevents usage of the PASSTHROUGH keyword in local cubes.
Introduced in SP3
The option to use the Meta Data Services repository format in the Migrate Repository Wizard has been disabled in SP3 and later versions, and using this format is not recommended. However, if this format is required for business reasons, you can enable the option through the EnableMigrationToMetaDataServicesFormat registry key.
By default, this registry key does not exist; it must be manually created at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server\Server Connection Info and set to enable repository migration to the Meta Data Services format. This registry key stores a case-sensitive string value. If the value is set to 1 or True, repository migration to the Meta Data Services format is enabled. If the value is set to any other string value, or if the registry key does not exist, repository migration to the Meta Data Services format is disabled.
Note If the value of this registry key is changed, the change takes effect immediately.
Introduced in SP3
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. On the remote computer, set the permissions on the folder to allow full control access by all members of the OLAP Administrators group on the computer running the Analysis server. Over time, as members are added to or removed from the OLAP Administrators group, be sure to modify the permissions on the remote Data folder to so that it reflects the current membership of the OLAP Administrators group. This will allow backup and restore to function properly.
Additionally, after running SP3a Setup, you must allow the account under which the Analysis server is running full control access to the remote Data folder.
If you apply SP3a to an instance of Analysis Services running in a clustered configuration, the domain-level OLAP Administrators group must be allowed full control access to the remote Data folder. For more information about creating and using a domain-level OLAP Administrators group, see Knowledge Base article 308023.
Introduced in SP3
The performance of cell writeback in Analysis Services has been improved by taking advantage of the bulk insert feature in SQL Server 2000 when performing permanent cell writeback operations on non-leaf cells. For more information, see the whitepaper "Optimizing Cell Writeback in Microsoft SQL Server 2000 Analysis Services" at this Microsoft Web site.
Introduced in SP4
Seven new registry entries have been introduced in SP4 to provide additional control over security, meta data, and memory management. For more information about using these new registry entries, see the white paper, "Registry Entries for Microsoft SQL Server 2000 Analysis Services," at this Microsoft Web site.
Introduced in SP4
When you run in Windows-on-Windows 64 (WOW) mode on Windows Server 2003 x64 SP1 or later, the default 64-bit version of Windows Performance Monitor cannot be used to access the Analysis Services Performance Counters that are used to monitor an instance of Analysis Services SP4. Instead, you must use the 32-bit version of Windows Performance Monitor. The 32-bit version is located at:
%systemdrive%\WINDOWS\SysWOW64\perfmon.exe
In WOW mode, Analysis Services Performance Counters can be viewed only when the 32-bit version of Performance Monitor is running on the same computer as the instance of SQL Server 2000 SP4.
This restriction does not apply to Windows Server 2003 for 64-Bit Itanium-based Systems.
Introduced in SP3
SQL Server error reporting is disabled by default. You can enable it during installation through SQL Server Setup or Analysis Services Setup, or after installation through the Server Properties dialog box in Enterprise Manager or the Server Properties dialog box in Analysis Manager. Enabling error reporting while you are running SQL Server Setup allows error reporting for the SQL Server database engine and SQL Server Agent. Enabling error reporting while you are running Analysis Services Setup allows error reporting for Analysis Services. If you want to enable error reporting for both SQL Server and Analysis Services, you must enable error reporting for SQL Server while running SQL Server Setup and Analysis Services while running Analysis Services Setup.
If you enable this feature, SQL Server is configured to send a report to Microsoft automatically if a fatal error occurs in the SQL Server database engine, in SQL Server Agent, or in SQL Server Analysis Services. Microsoft uses error reports to improve SQL Server functionality and treats all information as confidential.
Information about errors is sent over a secure (HTTPS) connection to Microsoft, where it is stored with limited access. Alternatively, this information can be sent to your own Corporate Error Reporting server. See this Microsoft Web site for more information about setting up a Corporate Error Reporting server.
The error report contains the following information:
Microsoft does not intentionally collect your files, name, address, e-mail address, or any other form of personal information. The error report can, however, contain customer-specific information from the memory or files of the process that caused the error. Although this information can potentially be used to determine your identity, Microsoft does not use this information for that purpose.
For the Microsoft error reporting data collection policy, see this Microsoft Web site.
If you enable error reporting and a fatal error occurs, you may see a response from Microsoft in the Windows Event log that points to a Microsoft Knowledge Base article about a particular error. A response may look similar to the following example:
Source = MSSQLServerOlapServicesDW
EventID = 1010
data = http://support.microsoft.com/support/misc/kblookup.asp?id=Q123456
&iBucketTable=1&iBucket=39980&Cab=21474432.cab&LCID=1033
&OS=5.1.2600.2.00010100.0.0To disable error reporting for the SQL Server database engine and SQL Server Agent, go to SQL Server Properties (General Tab) in Enterprise Manager and clear the Enable the error reporting check box. To disable error reporting for Analysis Services, go to Server Properties in Analysis Manager and clear the Enable Error Reporting check box. If error reporting is enabled for both SQL Server (database engine and SQL Server Agent) and Analysis Services, you must disable error reporting for SQL Server and Analysis Services individually.
This section discusses enhancements to SQL Server 2000 Meta Data Services that are included with SP4.
Important Updates to Meta Data Services are not installed with Analysis Services SP4. This information is provided in the Readme only because it relates to certain other changes in Analysis Services functionality. To obtain these updates to Meta Data Services, you must download and install Database Components SP4.
Introduced in SP1
Meta Data Browser now exports XML-based meta data in Unicode. Before SQL Server 2000 SP1, the browser exported ANSI code, which does not support non-English characters. This functional change is invisible to the user. As of this SP4 release, exported data is always expressed as Unicode. You can still export in ANSI code by setting the value of the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Repository\Engine\XMLExport to 0. The following list represents the values that you can set for this registry key:
For more information about each flag, see "IExport::Export Method" in SQL Server Books Online.
Introduced in SP3
Script support in information models has been disabled. After you installing SP3a or later, you receive the following error if your application accesses a property or method for which a script is defined:
EREP_SCRIPTS_NOTENABLEDTo enable script support
If you need to continue executing scripts, you can use the following procedure to create a registry setting that enables script support.
If you want to disable scripting later, set the value of this new registry key to 0.
Important You should always secure information models and the repository database to prevent unauthorized access.
Introduced in SP3
SQL Server includes in the msdb database a set of tables, stored procedures, and views that store information used by the Meta Data Services repository engine. In SP3, a new dedicated role named RepositoryUser was added and must be used to access and update repository information. This role has been granted create, read, update, delete, and execute permissions on these objects. The public role no longer has permissions on these objects.
This change affects existing repository objects in addition to any additional objects created by the repository engine in the future. Users and applications that access the repository through the public role must be added to the RepositoryUser role.
Introduced in SP4
SQL Server 2000 SP4 introduces new serviceability functionality that enables you to uninstall hotfixes applied to SP4 and later versions of SQL Server 2000 running on Windows XP and Windows Server 2003. (This same functionality was available with SQL Server 2000 SP3, but only after the application of an additional hotfix).