Introduction This article describes changes to the Microsoft SQL Server 2005 Readme file.
MORE INFORMATION The following information is either changed or newly provided since the release of the ReadmeSQL2005.htm file for SQL Server 2005.
SQL Server passwords are now case-sensitive In SQL Server 2005, passwords are tied to the operating system. Because of this change, login passwords for SQL Server 2005 are now case-sensitive.
You may receive an error message in the Error and Usage Reporting dialog box on a 64-bit computer If you are running SQL Server 2005 in a 64-bit environment, when you try to change the Error and Usage Reporting dialog box You may receive an error message when making settings on the Advanced Properties tab. You receive this error message when the "Error reporting location" field for the "Other (x86)" component is blank. We recommend providing a valid folder name in the "Bug Report Location" field on your local drive. This folder can be the same folder that you specify for the "Other" component.
You may receive a blank error message in SQL Server Management Studio You may upgrade a Microsoft Windows 2000-based computer that is running SQL Server 2005 to Microsoft Windows Server 2003 Service Pack 1 (SP1). When you do this, you receive a blank error message in SQL Server Management Studio.
To resolve this issue, repair Microsoft .NET Framework after you upgrade your operating system. To do this, follow these steps: 1. In Control Panel, open Add/Remove Programs.
2. Click Microsoft .NET Framework 2.0.
3. Click Change/Remove.
4. Click Repair, and then click Next.
5. After completing the repair process, restart your computer if prompted.
How to Use the DBCS Code Page If your operating system is configured to use a double-byte character set (DBCS) code page, select UNICODE encoding instead of ANSI encoding for the output file in the Generate SQL Server Script Wizard.
Missing backwards compatibility components in SQL Server Compact Edition
Microsoft SQL Server 2000 Desktop Engine Service Pack 4 (MSDE SP4) is based on Microsoft SQL Server 7.0. When you attempt to upgrade MSDE SP4 to SQL Server 2005 Compact Edition, you will receive backward-compatible component-related error messages during the installation process. At the same time, an error message will be written to the installation log file. This error message indicates that the SQLServer2005_BC.msi file does not exist in the SQL Server Compact Edition installation folder.
To complete the SQL Server Compact Edition installation, you must run the SQL Server Compact Edition Setup program in repair mode. For more information, see the "How to Install SQL Server 2005 from the Command Prompt" topic in SQL Server 2005 Books Online.
For more information about SQL Server 2005 Books Online, visit the following Microsoft website:
http://www.microsoft.com/downloads/details.aspx?displaylang=zh-cn&FamilyID=be6a2c5d-00df-4220-b133-29c1e0b6585f ( http://www.microsoft.com/downloads/details.aspx?displaylang= zh-cn&FamilyID=be6a2c5d-00df-4220-b133-29c1e0b6585f )
.
Invalid characters appear in some localized versions of the SQL Server Component Update dialog box. During the SQL Server 2005 installation, when the following conditions occur in the following order, "SQL Server Component Update" dialog box text will appear. Invalid characters such as \": • You have some localized versions of SQL Server components installed.
• You reinstalled these components without changing any settings.
This problem occurs in the following components: • Analysis Service
• Management and monitoring tools
The permissions required for full-text search in a clustered environment have changed. Changes have been made to the "Section 4.1.6 Reducing Permissions for Full-Text Search" topic in the readme file. The restriction requiring special permissions on the Microsoft Full-Text Engine for SQL Server (MSFTESQL) service account in clustered environments has been removed. In a clustered environment, the MSFTESQL service account no longer requires local administrator rights.
Note: As a best practice, we recommend setting up the MSFTESQL service to run under a low-privilege account.
How to copy SQL Server 2005 to a network share and run the installer from that location If you download SQL Server 2005 from the Microsoft Developer Network (MSDN) website, you will find that the product has been split into the following two downloads: • SQL Server 2005 - Developer Edition - Servers
• SQL Server 2005 - Developer Edition - Tools
To install SQL Server 2005, you must download the Servers and Tools files into folders named "Servers" and "Tools" respectively. Otherwise, Setup will fail when you install the tool components and SQL Server Books Online. At the same time, the following error message is written to the installer Core.log file:
CORE.LOG
=========
Error:Action "InstallToolsAction.10" threw an exception during execution.Error information reported during run:
Target collection includes the local machine.
Fatal Exception caught while installing package:"10"
Error Code:0x80070002 (2)
Windows Error Text:The system cannot find the file specified.
Source File Name:sqlchainingsqlprereqpackagemutator.cpp
Function Name:sqls::SqlPreReqPackageMutator::modifyRequest
Source Line Number:196
WinException caught while installing package.: 1603
Error Code:0x80070643 (1603)
Windows Error Text:Fatal error during installation.
Source File Name:packageengineinstallpackageaction.cpp
Function Name:sqls::InstallPackageAction::perform
Source Line Number:167
ForEachDirectory Sample readme file is incomplete
The readme file for ForEachDirectory Sample is incomplete. For the complete readme file, see the "ForEachDirectory Sample" topic in SQL Server 2005 Books Online.
SQL Server 2005 Setup requires 1.6 GB of disk space If your system drive has less than 1.6 GB of free disk space, you cannot install SQL Server 2005. Most spaces are only available for a short period of time. After running Setup, SQL Server 2005 requires 700 MB of disk space.
Unique nonclustered indexes cannot be created online In the final release version of SQL Server 2005, unique nonclustered indexes cannot be created online. This behavior only affects the following statements: • CREATE UNIQUE NONCLUSTERED INDEX
• CREATE UNIQUE NONCLUSTERED INDEX WITH DROP_EXISTING
• ALTER TABLE ADD CONSTRAINT PRIMARY KEY NONCLUSTERED
• ALTER TABLE ADD CONSTRAINT UNIQUE NONCLUSTERED
For more information, see Section 4.1.23 in the SQL Server 2005 Readme. For more information about supported online index operations, see SQL Server 2005 Books Online.
If you are using a ROLAP query, you may receive the error message If you are using a ROLAP query that conditions on a parent/child dimension using RootMemberIf=ParentIsMissing, you may receive the following error message:
Unable to display cell properties
Setup fails when installing SQL Server Analysis Services or Database Engine during upgrade SQL Server 2005 Setup does not collect shared drive information when upgrading SQL Server. This behavior may cause Setup to fail during an upgrade if any of the following conditions exist: • Adding SQL Server 2005 Analysis Services to an instance of the database engine.
• Add a database engine for an instance of SQL Server 2005 Analysis Services.
• Install a new instance of SQL Server Analysis Services and upgrade the database engine at the same time.
To resolve this issue, run the installer from a command prompt. If you are installing SQL Server 2005 Analysis Services, set the INSTALLASDATADIR parameter to the shared drive where the database engine data files are located. If you are installing the database engine, set the INSTALLSQLDATADIR parameter to the shared drive where the Analysis Services data files are located.
For example, use the following syntax to specify the same path for Analysis Services data files and Database Engine data files.
Note: You must provide information specific to your installation. start /wait <DVD Drive>:setup.exe /qn UPGRADE=SQL_Engine VS=<VSName> INSTALLVS=Analysis_Server
INSTANCENAME=MSSQLSERVER SQLACCOUNT=<DomainNameUserName> SQLPASSWORD=<StrongPassword>
ADMINPASSWORD=<StrongPassword> ADDLOCAL=Analysis_Server,AnalysisDataFiles,Client_Components
INSTALLASDATADIR="I:DATA" INSTALLSQLDATADIR="I:DATA" SQLCLUSTERGROUP="DomainNameGroupName"
ASCLUSTERGROUP="DomainNameGroupName" AGTCLUSTERGROUP="DomainNameGroupName"
FTSCLUSTERGROUP="DomainNameGroupName" SQLBROWSERACCOUNT=<DomainNameUserName>
SQLBROWSERPASSWORD=<StrongPassword> ASACCOUNT=<DomainNaneUserName> ASPASSWORD=<StrongPassword>
PIDKEY=<pidkey value without a "-">
When using ROLAP, you may receive an error message You are using ROLAP and your cube uses tables from more than one data source. When trying to browse multidimensional data, you may receive one of the following error messages:
Error Message 1
OLE DB Error: OLE DB or ODBC Error: SQL Server blocked access to STATEMENT 'OpenRowset/OpenDatasource' for component 'Ad Hoc Distributed Queries' because this component has been shut down as part of this server's security configuration.
System administrators can enable 'Ad Hoc Distributed Queries' by using sp_configure. For more information about enabling 'Ad Hoc Distributed Queries', see "Surface Application Configurator" in SQL Server Books Online. ; 42000.
Error message 2
OLE DB Error: OLE DB or ODBC error occurs because SQL Server 2005 only provides in-process access to a specific set of providers. SQLNCLI is a new native OLE DB provider for SQL Server 2005 that has access rights. However, SQLNCLI.1 is a version-specific SQLNCLI provider and is not in the list of providers. Therefore, SQLNCLI.1 has no access. Although SQLNCLI and SQLNCLI.1 are identical (because SQLNCLI points to SQLNCI.1), SQL Server 2005 does not recognize that they are the same. SQL Server 2005 blocks access to SQLNCLI.1.
To resolve this issue, use one of the following methods: • Use SQLNCLI instead of SQLNCLI.1 in the OLE DB connection string.
• In SQL Server, explicitly add SQLNCL.1 to the list of vendors with in-process access.
Assertions occur when you use the EXPORT MINING MODEL command. When you use the EXPORT MINING MODEL command against a local cube, you may experience assertions or other failures. To resolve this problem, close the connection to the local cube before issuing the EXPORT statement, and then reopen it.
Replication ActiveX controls cannot be called from applications created using the .NET Framework 1.1 or .NET Framework 1.0 Replication ActiveX controls do not support Replication Management Object (RMO) programming in managed code. If you want to call ActiveX controls from managed code, you must use the .NET Framework 2.0. If using an older version of the .NET Framework, an exception will be thrown.
Do not change the sa account name on servers in a replication topology In SQL Server 2005, you can use the ALTER LOGIN command to change the sa account to a different name. Changing names is not supported on servers in a replication topology and may cause replication to fail.
msdb database is not upgraded during upgrade from MSDE to SQL Server Express If you upgrade MSDE to SQL Server Express, the msdb database is not upgraded. The following replication features will be affected: • Replicate databases cannot be connected to or restored from an MSDE instance to an upgraded SQL Server Express instance. The database can be connected to or restored to a new SQL Server Express instance.
• The following are considerations for creating subscriptions on an upgraded SQL Server Express instance: • You cannot use the New Subscription wizard to create subscriptions on an upgraded instance.
• If subscriptions are enabled for Windows Synchronization Manager, you cannot use Replication Management Object (RMO) or Transact-SQL stored procedures to create subscriptions on the upgraded instance.
Subscriptions can be created on a new instance of SQL Server Express using the New Subscription wizard, RMO, or Transact-SQL stored procedures.
During upgrade from SQL Server 2000 or SQL Server 7.0, SA's default database changes to MASTER
If you upgrade from SQL Server 2000 or SQL Server 7.0 to a release version of SQL Server 2005, the default database for SA changes to MASTER. This issue occurs because the SA account is a special case account and the SA account is cached. To resolve this issue, run the dbcc freesystemcache command or restart the SQL Server service.