|
Chapter 2: Installing Analysis Services
Chapter 2 Installing Analysis ServicesThis chapter contains information about installing Microsoft SQL Server 2000 Analysis Services only. This chapter contains the following topics:
Related Documents The Readme.html file in the root directory of the SQL Server 2000 CD-ROM contains information about Analysis Services. You can also view the release notes by clicking Read the Release Notes on the SQL Server 2000 Setup program (Autorun.exe) menu.
Hardware and Software Requirements for Installing Analysis ServicesBefore you can install Microsoft SQL Server 2000 Analysis Services, your computer must meet the following requirements.
For more information about supported hardware, see the Microsoft Windows Hardware Compatibility List at www.microsoft.com/hcl/default.asp. For more information about Windows 2000-compatible hardware, use the Microsoft Windows 2000 compatible hardware devices search tool at www.microsoft.com/windows/windows2000/upgrade/compat/search/devices.asp.
Running SetupThis topic describes how to install Microsoft SQL Server 2000 Analysis Services.If you are upgrading from an earlier version of Analysis Services (formerly called OLAP Services), you should take certain steps before performing the following procedure. For more information, see Upgrading from an Earlier Version. If you are reinstalling Analysis Services, you should take certain steps before and after performing the following procedure. For more information, see Reinstalling Analysis Services. Although Analysis Services can connect to multiple instances of SQL Server running on a single computer, you cannot install multiple instances of Analysis Services on a single computer. To install Analysis Services, use the Analysis Services Setup program or the SQL Server 2000 Setup program. To install Analysis Services
Unless you are installing the client components on a client computer, installing all components is recommended. The following components are available for installation.
To change the destination drive or folder, click Browse. Although remote network drives are listed in these dialog boxes, installation to locations on remote network drives is not supported.
Space Required and Space Available indicate disk drive space and help you determine what components to install. If your current disk drive does not have enough space available, you can click Disk Space to determine which disks on your computer have enough space to install Analysis Services. After you select the components to install, click Next. The steps that follow may change depending on which components you selected to install. The default location for the Data folder is C:\Program Files\Microsoft Analysis Services\Data (unless you specified another location for Analysis Services in the previous step). You can specify a different location by clicking Browse. If you change the default folder or drive, be sure to enter a fully qualified path. To specify a data storage location other than the computer on which the server is installed, you must have full control access permissions on that computer.
IMPORTANT: The Data folder stores security files that control end users’ access to objects on the Analysis server. For this reason, the Data folder must be secured against unauthorized access.
After you select the location of the Data folder, click Next.
If in Step 10 you specified a data storage location other than the computer on which the server is installed, you must configure your Analysis server service (MSSQLServerOLAPService) to log on as your user account, instead of the default, which is to log on as the system account. To do this, use the Services application, which is in Control Panel in Windows NT 4.0 or the Administrative Tools folder in Control Panel in Windows 2000.
Setup Parameters and Silent InstallationYou can start the Analysis Services Setup program (\Msolap\Install\Setup.exe on the SQL Server CD-ROM) with the following optional command line parameters:-r This option causes Setup.exe to automatically generate a silent response file (.iss), which is a record of the installation input, in the systemroot folder (typically C:\WinNT). -s This option performs a silent (unattended) installation. -f1<path\ResponseFile> This option allows you to specify the alternate location and name of the response file (.iss file). If the -f1 switch is not used when you run silent installation, Setup searches for the response file Setup.iss in the same folder as Setup.exe. -f2<path\LogFile> This option allows you to specify an alternate location and name of the log file. By default, the Setup.log log file is created and stored in the systemroot folder (typically C:\Winnt). If you use the -r option you can create a record of any installation scenario. You can use this record to perform a silent (unattended) installation. For example, the following command initiates a silent installation of the components specified in the Setup.iss response file previously recorded when you used the -r option:
Setup.exe -s -f1C:\temp\setup.iss-z Prevents Setup.exe from checking the available memory during initialization. This switch is necessary when running Setup on a computer with more than 256 megabytes (MB) of memory. If it is not used, Setup.exe reports insufficient memory and exits.
Reinstalling Analysis ServicesTo reinstall Microsoft SQL Server 2000 Analysis Services, follow these steps:
NOTE: Reinstalling Analysis Services does not delete the Analysis Services repository (Msmdrep.mdb), which contains Analysis Services meta data. However, you must process all cubes in the repository after reinstallation. If you have backed up the FoodMart 2000 sample database before reinstallation, restore FoodMart2000.mdb to recover your changes to the file.
Stopping or Removing Analysis ServicesTo stop Microsoft SQL Server 2000 Analysis Services, follow these steps:
If your computer’s operating system is Windows NT 4.0, double-click Services. To remove Analysis Services, use the Add/Remove Programs application in Control Panel. Removing Analysis Services does not delete the Analysis Services repository (Msmdrep.mdb), which contains Analysis Services meta data, or the query log (Msmdqlog.mdb). If you want to fully remove Analysis Services, you must delete these files manually.
Upgrading from an Earlier VersionTo upgrade from an earlier version of Microsoft SQL Server 2000 Analysis Services (previously OLAP Services), perform the following actions:
Install Analysis Services by running the Analysis Services Setup program. For more information, see Running Setup. When you upgrade from an earlier version, Setup does not delete or replace the Analysis Services repository or the query log.
NOTE: The default location for Analysis Services has changed from C:\Program Files\OLAP Services in earlier versions of Analysis Services to C:\Program Files\Microsoft Analysis Services in this version of Analysis Services.
Backward CompatibilityMicrosoft SQL Server 2000 Analysis Services is compatible with SQL Server version 7.0 OLAP Services. Cubes that were created in SQL Server 7.0 OLAP Services need to be migrated to the updated meta data repository format and reprocessed. Otherwise, the existing structures for cubes, roles, shared dimensions, and so on do not need to be changed. For more information about migrating the SQL Server 7.0 OLAP Services repository to SQL Server 2000 Meta Data Services, see Migrating Analysis Services Repositories.The following sections concern backward compatibility with SQL Server 7.0 OLAP Services. Administration of Analysis Services Analysis Manager is backward compatible with SQL Server 7.0 OLAP Services. It is capable of administering both OLAP servers (the server that ships with SQL Server 7.0 OLAP Services), and Analysis servers (the server that ships with SQL Server 2000 Analysis Services) concurrently. When administering an OLAP server, the OLAP Services portion of SQL Server 7.0 Service Pack 2 code is used to assure complete backward compatibility. The add-in programs in Service Pack 2 are now integrated with Analysis Manager and do not need to be installed to administer OLAP servers. Client and Local Cube Support Some features in SQL Server 2000 Analysis Services are not supported by the SQL Server 7.0 OLAP Services client components or in a local cube. For more information, including a list of features, see 7.0 Analysis Services Client and Local Cube Support. Decision Support Objects Analysis Services now includes an updated version of Decision Support Objects (DSO), which is automatically installed during Setup. Programs must use this updated version of DSO when administering an Analysis server (the server that ships with SQL Server 2000 Analysis Services). No other change to these programs is necessary. Programs that use the updated version of DSO are compatible with and can administer OLAP servers (the server that ships with SQL Server 7.0 OLAP Services); however, new features will not be available on the OLAP server. PivotTable Service SQL Server 2000 Analysis Services includes an updated version of PivotTable Service. Client applications that use PivotTable Service do not need to use this new version when connecting to an Analysis server unless you need access to objects that include new features. The objects that use these new features (such as data mining models and cubes that include parent-child dimensions) are not seen by the client applications that use the earlier version of PivotTable Service. Client applications that use the updated version of PivotTable Service can connect to any server, regardless of its version. Client applications that use the updated version of PivotTable Service can configure their compatibility settings using the following properties:
Custom Add-in Programs Custom add-in programs that were developed for use with SQL Server 7.0 OLAP Services will continue to work with SQL Server 2000 Analysis Services. No changes are necessary to use them. Archiving, Restoring, and Migrating Data Analysis Services supports some but not all permutations of archiving and restoring databases and migrating repositories between versions of the product. For information about supported migration paths, see Supported Migration Paths for Analysis Services Repositories. For information about archiving and restoring data between versions of the product, see Archiving and Restoring Databases Between Versions of Analysis Services.
7.0 Analysis Services Client and Local Cube SupportThis table shows support for new server features by the Microsoft SQL Server 7.0 OLAP Services client components and in a SQL Server 2000 Analysis Services local cube. When a feature may cause data to be translated incorrectly by a 7.0 client application, the server prevents the cube from being visible and prevents the client connection to the cube. If the absence of a feature in a local cube might change data values presented to the user, then a local cube using the feature cannot be created.For each feature listed here, the table shows whether a cube containing a feature is visible on a 7.0 client application and if the cube is visible whether the feature itself is available on the 7.0 client application. For each feature, the table also shows whether a local cube can be created using the feature and whether the feature itself is supported in a local cube.
Supported Migration Paths for Analysis Services RepositoriesYou can migrate a Microsoft SQL Server 2000 Analysis Services repository from the default Microsoft Access (Microsoft Jet 3.5 or 4.0) database to a SQL Server database on the same or a different computer. You cannot migrate a SQL Server repository to a Microsoft Access repository. You can change the format from native to SQL Server 2000 Meta Data Services format when you migrate a database. To migrate a SQL Server database repository between native and Meta Data Services formats, you must migrate it from one SQL Server database to another. The following table shows supported migration paths for repository databases.
Related Topics Migrating Analysis Services Repositories, OLE DB Provider for Jet
Archiving and Restoring Databases Between Versions of Analysis ServicesOn an Analysis server (the server that ships with Microsoft SQL Server 2000 Analysis Services), you can restore databases that were archived using an OLAP server (the server that ships with SQL Server 7.0 OLAP Services) or an Analysis server. The following table shows all the restoration paths supported for databases archived while in SQL Server 7.0 OLAP Services or SQL Server 2000 Analysis Services using native or SQL Server 2000 Meta Data Services formats with SQL Server or the Microsoft Jet 3.5 or 4.0 OLE DB provider.
Related Topics Archiving and Restoring Databases, OLE DB Provider for Jet
Last Updated: Saturday, July 7, 2001 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||