When installing this CTP release of SQL Server 2005 with the Visual Studio 2005 Release Candidate (RC), you must always install SQL Server 2005 before installing Visual Studio 2005.

You must also remove all previous builds of SQL Server 2005, Visual Studio 2005, and the .NET Framework before installing this CTP release. Because both products depend on the same version of the .NET Framework, they must be uninstalled in the following order:

1. SQL Server 2005
   
   
2. Visual Studio 2005
   
   
3. .NET Framework 2.0
   
   

For more information about using Visual Studio 2005 RC with this CTP release of SQL Server 2005, see section 5.7 Microsoft Visual Studio 2005.

[Top]

System Configuration Checker (SCC) verifies the value of the Performance Monitor Counter registry key before SQL Server installation begins. If SCC cannot verify the existing registry key, or if SCC cannot run the Lodctr.exe system program, the SCC check fails, and Setup is blocked. To complete setup, you must manually increment the registry key.

[Top]

Windows Cryptographic Service Provider (CSP) is code that performs authentication, encoding, and encryption services that Windows-based applications access through CryptoAPI on Windows Server 2003. If the CSP service is stopped or disabled, SQL Server Setup fails and displays a Windows Logo Requirement message.

[Top]

Because the Microsoft Distributed Transaction Coordinator (MS DTC) is not completely configured in Windows, applications might fail to enlist SQL Server 2005 resources in a distributed transaction. This problem can affect linked servers, distributed queries, and remote stored procedures that use distributed transactions. To prevent such problems, you must fully enable MS DTC services on the server where SQL Server 2005 is installed.

[Top]

The Northwind and pubs sample databases are not installed by default in SQL Server 2005. These databases can be downloaded from this Microsoft Web site.

[Top]

AdventureWorks, AdventureWorksDW, and AdventureWorksAS sample databases and companion samples are not installed by default. To use SQL Server 2005 samples or to test sample code in SQL Server 2005 Books Online, you must install these databases.

Setup installs the samples in the installer package SqlServerSamples.msi. Use the following procedure to extract samples from the installer package and complete the installation of samples.

In unattended installations, if you want to attach the sample databases and samples to a specific instance of SQL Server, use the following command-line switch, where instancename is not required for the default instance:

SAMPLEDATABASESERVER=<servername>\<instancename>. 

The instance to which you attach the sample database must be a local instance. If you do not specify the switch, the files are installed to the \Tools\Samples directory. Otherwise, they are installed to the data directory of the specified instance and attached to the server.

[Top]

When an instance of SQL Server 2005 that hosts the report server database for an instance of Reporting Services is uninstalled by running Setup from the command prompt with the SAVESYSDB parameter, the report server database files are left behind with the rest of the system database files. By default, these files are named ReportServer$Instancename and ReportServer$InstancenameTempdb. If you then reinstall SQL Server 2005 with the USESYSDB Setup parameter and specify that the instance host the report server database, Setup will be unable to re-create these database files because they already exist. This can also occur when you use the Build Cleanup Wizard to uninstall an instance of SQL Server 2005 that hosts the report server database.

To correct this problem, do one of the following:

• Drop report server databases before uninstalling using SAVESYSDB.
  
  
• Do not install Reporting Services along with SQL Server when using the SAVESYSDB Setup parameter.
  
  
• Use the RSDATABASENAME Setup parameter to specify a new name for the report server database when installing Reporting Services.
  
  

[Top]

MS DTC cluster resources must be created on all Windows Server 2003 32-bit and 64-bit clusters before installing SQL Server 2005 CTP. If MS DTC is not set up as a cluster resource on Windows Server 2003, a warning is displayed.

[Top]

On a cluster server, if you add SQL Server and Analysis Services to one node of the cluster and later add SQL Server to another node, Analysis Services will not function properly. To work around this problem, uninstall SQL Server and Analysis Services, and then reinstall SQL Server and Analysis Services to both nodes of the cluster.

[Top]

If you install SQL Server 2005 from a network share to a computer that is running Microsoft Windows Server 2003 Service Pack 1 (SP1) or later, or a version of Windows XP later than SP2, online Help topics might not display properly during Setup. To view these topics, you must first copy setupsql9.chm to the local computer, open it, and then search for desired specific topics. For information about accessing the Setup documentation, see section 3.1 Accessing Setup Documentation.

[Top]

If your computer has SQL Server 2000 Management Tools and a default instance of SQL Server 2005 installed, SQL Server Setup will permit you to install a SQL Server 2000 default instance. However, doing so will disable the installed instance of SQL Server 2005. Therefore, do not install a default instance of SQL Server 2000 when SQL Server 2000 Management Tools and a default instance of SQL Server 2005 already exist on the computer.

[Top]

Setup might fail if an existing SQL Server client installation is configured with the "force encryption" option enabled. To work around this issue, disable the option on any SQL Server clients. For Microsoft Data Access Components (MDAC) clients in SQL Server 2000, use the SQL Server 2000 Client Network Utility. For SQL Native Client, uninstall SQL Native Client by using Add or Remove Programs. On a cluster, uninstall SQL Native Client from all nodes. Then run SQL Server 2005 Setup again.

[Top]

Password expiration policy is not enforced by default in this CTP release. This is a change of behavior from earlier CTP releases. For information about configuring password expiration, see the "Password Complexity and Expiration" and "CREATE LOGIN (Transact-SQL)" topics in SQL Server Books Online.

[Top]

When an instance of SQL Server 2005 is uninstalled from a side-by-side configuration on a computer that is running Windows Server 2003 x64 or Windows XP Professional x64, the SQL Server Active Directory® Helper service is deleted. SQL Server Active Directory Helper is a service installed with SQL Server that handles Active Directory objects. There is only one SQL Server Active Directory Helper service instance for all instances of SQL Server installed on the computer.

[Top]

During setup, SQL Server 2005 adds the following security groups to Windows:

• SQLServer2005DTSUser$ComputerName
  
  
• SQLServer2005MSFTEUser$ComputerName$InstanceName
  
  
• SQLServer2005MSOLAPUser$ComputerName$InstanceName
  
  
• SQLServer2005MSSQLServerADHelperUser$ComputerName
  
  
• SQLServer2005MSSQLUser$ComputerName$InstanceName
  
  
• SQLServer2005NotificationServicesUser$ComputerName
  
  
• SQLServer2005ReportingServicesWebServiceUser$ComputerName$InstanceName
  
  
• SQLServer2005ReportServerUser$ComputerName$InstanceName
  
  
• SQLServer2005SQLAgentUser$ComputerName$InstanceName
  
  
• SQLServer2005SQLBrowserUser$ComputerName
  
  

These groups simplify granting permissions required to run SQL Server Windows services and other executables. They also help secure SQL Server files.

In SQL Server Books Online, $ComputerName was omitted from the names. The computer name has since been added to the group names to uniquely identify each group. Unique group names are necessary if SQL Server 2005 is installed on domain controllers. For all references to security groups that start with "SQLServer2005," substitute the appropriate group name listed above.

[Top]

It is possible to install SQL Server 2005 on a Windows domain controller; however, it cannot run on a Windows Server 2003 domain controller as Local Service or Network Service. SQL Server service accounts should run as Windows domain user accounts. It is also possible to install SQL Server service accounts to run as Local System, but this option is not recommended.

Do not change the role of the server after you install SQL Server 2005. For example, if you install SQL Server 2005 on a member server, do not use the Dcpromo tool to promote the server to a domain controller. Or, if you install SQL Server 2005 on a domain controller, do not use Dcpromo to demote the server to a member server. Changing the role of a server after you install SQL Server 2005 can result in loss of functionality and is not supported.

[Top]

SQL Server service, SQL Server Agent service, Analysis Services service, and Full-Text Search service must run as domain accounts that are members of the built-in Administrators group on each node of the cluster.

[Top]

This readme item provides an updated version of the "How to: Configure IIS to Run 32-bit Reporting Services in WOW64 Mode" topic. Use the following steps to run Reporting Services in Windows-on-Windows 64 (WOW64) x86 emulation mode. Use the version of ASP.NET 2.0 that is provided through dotnetfx64.exe.

[Top]

Remote Setup of SQL Server 2005 is not supported in this release. If you use the TARGETCOMPUTER parameter to install SQL Server 2005 on a remote computer, SQL Server Setup will fail. To install SQL Server 2005 on a remote computer, use a remote connection to run the SQL Server Setup program in user interface mode or from the command prompt.

[Top]

If you uninstall an instance of SQL Server 2005 using the Build Cleanup Wizard or by running Setup from the command prompt with the SAVESYSDB parameter, system databases are retained. In this case, when you remove multiple instances of SQL Server 2005 from the same computer, you must reinstall the instances in the same order that they were originally installed. Otherwise, existing jobs may not run because of agent job information stored in the retained system databases.

[Top]

Setup installs management tools only on the primary node of a failover cluster. To make the tools accessible from secondary nodes of a failover cluster, install them separately on each secondary node.

[Top]

When upgrading from any edition of the Spanish version of SQL Server 2000 to any edition of the Spanish version of SQL Server 2005, Setup fails, and an error message displays that instructs you to correct the problem and re-run Setup. To correct the problem, exit Setup and re-run it to continue upgrading.

[Top]

If you specify a non-default installation path for SQL Server components, you must include at least one directory in the installation path. Installing directly to the root directory (C:\, for example) will install WOW64 components to %<root>% (X86)\ and cause Setup to fail.

[Top]

Setup might fail and roll back with the following error message: "An installation package for the product Microsoft SQL Native Client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli.msi'." To work around this problem, uninstall SQL Native Client by using Add or Remove Programs. On a cluster, uninstall SQL Native Client from all nodes. Then, run SQL Server Setup again.

[Top]

Setup from the command prompt might fail when you uninstall an earlier CTP release of SQL Server 2005 by using SAVESYSDB, and then install this release by using USESYSDB, if the sp_configure options SMO and DMO XPs or Agent XPs are disabled on the earlier instance. To resolve this issue, ensure that these options are enabled before using Setup to upgrade system databases. For more information, see "Setting Server Configuration Options" in SQL Server Books Online.

[Top]

If a pre-June CTP Database Engine Tuning Advisor (DTA) client was used to tune SQL Server 2000 or the pre-June CTP release of SQL Server 2005 (including SQL Server 2005 Beta 2), there might be problems if a September CTP DTA client is used to tune these servers. Knowledge Base article 899634 contains a Transact-SQL script that is used to remove DTA client metadata from the msdb database on these servers. This script can be executed only by a member of the sysadmin fixed server role.

[Top]

If you uninstall an instance of SQL Server 2005 earlier than the June CTP by using the Build Cleanup Wizard or by running Setup from the command prompt with the SAVESYSDB parameter, and then install this release, some jobs might fail. Jobs will fail for users who are not members of the sysadmin fixed server role if the jobs contain job steps that use active scripting subsystem proxies. When this problem occurs, you receive the following error message:

sqlstubss90.exe - Unable To Locate Component
The application failed to initialize properly(0xc0000022). 
Click on OK to terminate the application

To resolve this problem, execute the following script:

USE [msdb]
GO

create table #tmp_sp_help_proxy(proxy_id int null, name nvarchar(128) null, 
    credential_identity nvarchar(128) null, enabled tinyint null, description 
    nvarchar(1024) null, user_sid varbinary(40) null, credential_id int null, 
    credential_identity_exists int null)
insert into #tmp_sp_help_proxy(proxy_id, name, credential_identity, enabled, description, 
    user_sid, credential_id, credential_identity_exists) exec msdb.dbo.sp_help_proxy
GO

DECLARE @cred_id int
DECLARE @name sysname
DECLARE proxy_cursor CURSOR LOCAL
FOR
   SELECT name, credential_id FROM msdb.dbo.sysproxysubsystem sps
   JOIN #tmp_sp_help_proxy t on (t.proxy_id=sps.proxy_id) WHERE subsystem_id=2
OPEN proxy_cursor
FETCH NEXT FROM proxy_cursor INTO @name, @cred_id
WHILE (@@fetch_status = 0)
BEGIN
      SET @name = (N'____Copy'+@name)
      EXEC msdb.dbo.sp_add_proxy @proxy_name=@name, @credential_id=@cred_id,@enabled=1
      EXEC msdb.dbo.sp_grant_proxy_to_subsystem @proxy_name=@name, @subsystem_id=2
      EXEC msdb.dbo.sp_delete_proxy @proxy_name=@name
      FETCH NEXT FROM proxy_cursor INTO @name, @cred_id
END
CLOSE proxy_cursor
DEALLOCATE proxy_cursor
GO

drop table #tmp_sp_help_proxy
GO

[Top]

The Report Builder role has changed permissions in this release. Reports created using a previous release of SQL Server 2005 may fail to load in this CTP release because of insufficient permissions.

[Top]

If you deployed instances of Notification Services on the June CTP, and you want to migrate those instances to this release of SQL Server 2005, you must manually migrate the instances of Notification Services. However, because of an incorrect version number in the June CTP, you must perform an additional step of manually updating version numbers before you can migrate the instances.

[Top]

To enhance security, SQL Server 2005 disables network connectivity for some new installations. Network connectivity using TCP/IP is not disabled if you are using SQL Server Enterprise, Standard, or Workgroup Edition, or if a previous installation of SQL Server is present. Named Pipes connectivity is available only for local connections unless a previous installation of SQL Server is present. For all installations, the shared memory protocol is enabled to allow local connections to the server. The SQL Browser service might be stopped, depending on installation conditions and installation options.

[Top]

Client connections to an instance of the SQL Server Database Engine running on Windows Server 2003 Service Pack 1 might fail with the following error: "ProviderNum: 7, Error: 10054, ErrorMessage: "TCP Provider: An existing connection was forcibly closed by the remote host"." This can occur when you are testing scalability with a large number of client connection attempts. To resolve this issue, use the regedit.exe utility to add a new DWORD value named SynAttackProtect to the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ with value data of 00000000.

[Top]

In SQL Server 2005 Books Online, the "Serialization of XML Data" topic states that the syntax CONVERT(stringtype, xmlvalue, 1) can be used to avoid the entitization of white-space characters. This feature is not implemented in this CTP release.

[Top]

SQL Server 2005 Books Online incorrectly states that when a conversation using dialog security spans databases, SQL Server creates a session key encrypted with the master key for the database. Actually, the session key is encrypted with the master key for the database for all conversations that use dialog security. If a database master key is not available, messages for the conversation remain in the transmission_queue with an error until a database master key is created, or until the conversation times out. Either use the ENCRYPTION = OFF parameter to create an unencrypted dialog, or use the following command to create a database master key:

CREATE MASTER KEY ENCRYPTION BY PASSWORD = '<password>'

[Top]

Each instance of a byte-ordered user-defined type (UDT) object can have only one serialized representation. If the serialize or de-serialize routines recognize more than one representation of a particular object, you may see errors in the following cases:

• During validation of a byte-ordered UDT passed through RPC, UDT validation performs de-serialization/re-serialization of the UDT and requires that the resulting bytes be exactly the same as the original. If the validation fails, you will see the error: "System.Data.SqlClient.SqlException, Incoming TDS RPC protocol stream is incorrect. Parameter 1 ("<ParameterName>"): The supplied value is not a valid instance of data type <TypeName>. Check the source data for invalid values."
  
  
• During DBCC, the bytes stored in a byte-ordered UDT column must be equal to the computed serialization of the UDT value. If this is not true, the DBCC CHECKTABLE routine will report a consistency error.
  
  

[Top]

The autorecovered shadow copy feature of the Volume Shadow Copy Service (VSS) has the following limitations.

SQL Server does not allow registering different versions of an assembly with the same name, culture, and public key. If you plan to retain databases from a version of SQL Server 2005 earlier than the September CTP release, you must drop all but one instance of an assembly that has multiple registrations before you install the September CTP release.

[Top]

In releases prior to SQL Server 2005, the Full-Text Search service ran under the NT AUTHORITY\LOCAL SYSTEM account, which has a high degree of privileges. In SQL Server 2005, the service account selected for the SQL Server Database Engine is used to run the MSFTESQL service that supports Full-Text Search. By doing this, MSFTESQL runs with lower privileges than before.

Because the MSFTESQL service account requires fewer privileges than the Database Engine service account, in SQL Server 2005, you can change the MSFTESQL service account. If you do so, we strongly recommend using the following guidelines:

• Always use the SQL Server Configuration Manager to change the service account. This helps ensure that the service account is placed in the proper Windows local group that supports Full-Text Search security.
  
  
• Use a Windows user account that belongs only to the Windows Users group on the local computer system.
  
  
• Use a different Windows user account for each MSFTESQL instance. This ensures least privileges for each service account by limiting it to only one instance of SQL Server.
  
  

[Top]

To create an EXTERNAL_ACCESS or UNSAFE assembly in SQL Server, or to load an assembly, one of the following two conditions must be met:

• The assembly is strong name signed or authenticode signed with a certificate. This strong name (or certificate) is created inside SQL Server as an asymmetric key (or certificate) and has a corresponding logon with EXTERNAL ACCESS ASSEMBLY permission (for external access assemblies) or UNSAFE ASSEMBLY permission (for unsafe assemblies).
  
  
• The database owner (DBO) has EXTERNAL ACCESS ASSEMBLY (for EXTERNAL ACCESS assemblies) or UNSAFE ASSEMBLY (for UNSAFE assemblies) permission, and the database has the TRUSTWORTHY database property set to ON.
  
  

We recommend that the TRUSTWORTHY property on a database not be set to ON only to run common language runtime (CLR) code in the server process. Instead, we recommend that an asymmetric key be created from the assembly file in the master database. A logon mapped to this asymmetric key must then be created, and the logon must be granted EXTERNAL ACCESS ASSEMBLY or UNSAFE ASSEMBLY permissions.

The following Transact-SQL statements perform the steps that are required to create an asymmetric key, map a logon to this key, and then grant EXTERNAL_ACCESS ASSEMBLY permission to the logon. You must execute the following Transact-SQL statements before executing the CREATE ASSEMBLY statement.

USE master
GO  

CREATE ASYMMETRIC KEY HelloWorldKey FROM EXECUTABLE FILE = 'C:\HelloWorld.dll'  
CREATE LOGIN HelloWorldLogin FROM ASYMMETRIC KEY HelloWorldKey  
GRANT EXTERNAL ACCESS ASSEMBLY TO HelloWorldLogin
GO

[Top]

On upgrade to SQL Server 2005, Full-Text Search uses enhanced noise word files to populate full-text indexes. If you customized the noise word files in the previous version of SQL Server and you want Full-Text Search to continue using the customized files after upgrade, you must replace the SQL Server 2005 noise word files with the customized files.

The SQL Server 2005 noise word files are located in the <InstallDirectory>\Microsoft SQL Server\MSSQL.1\MSSQL\FTDATA\ folder, where InstallDirectory is the installation folder. Noise word files from previous versions of SQL Server are located in the <InstallDirectory>\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\FTERef folder. For information about how to replace the SQL Server 2005 noise word files with the noise word files from the previous version of SQL Server, see Microsoft Knowledge Base article 905617.

[Top]

Database mirroring has the following limitations.

The behavior of programs that run under an application role might change because, by default, SQL Server 2005 limits the visibility of master database metadata to application roles. As a temporary workaround, you can enable trace flag #4616. For more information, see Knowledge Base article 906549.

[Top]

SQL Server 2005 Books Online incorrectly lists the editions of SQL Server that are supported by the Database Engine Tuning Advisor graphical user interface (GUI) and dta utility tuning options. Tuning options that involve indexed views, partitioning, and generating recommendations online are not supported by the Standard Edition of either SQL Server 2005 or SQL Server 2000. In addition, tuning options that involve partitioning and generating recommendations online are not supported by the Enterprise, Developer, and Enterprise Evaluation editions of SQL Server 2000. These limitations apply to both the 32-bit and 64-bit versions of SQL Server. For detailed information about which tuning options are not supported, see Knowledge Base article 906649.

[Top]

The SUPPLEMENTAL_LOGGING database option is not implemented in this release of SQL Server. This option can be set but has no effect.

[Top]

Cloned databases may be left behind unexpectedly on the test server after a successful test server/production server tuning session using Database Tuning Advisor even if you have not used the RetainShellDB option. These cloned databases may interfere with subsequent tuning sessions and should be dropped before performing another test server/production server tuning session. In addition, if a tuning session exits unexpectedly, the databases cloned to the test servers and objects within those databases may be left behind on the test server. You should also delete these databases and objects before starting a new test server/production server tuning session.

[Top]

Assemblies that fail to load into the server address space for any reason will still appear in the sys.dm_clr_loaded_assemblies dynamic management view.

[Top]

For distributed queries from 64-bit SQL Server 2005 clients to 32-bit SQL Server 2000 servers, SQL Server 2000 SP3 or later is required. Distributed queries include references to linked server entries that you define by using sp_addlinkedserver and the OPENROWSET and OPENQUERY functions. In addition, system stored procedures, known as catalog stored procedures, must be manually upgraded on SQL Server 2000 SP3 and SP4 servers.

If the versions of the catalog stored procedures on the 32-bit instance of SQL Server 2000 are not updated with the versions that shipped with the service pack, you will receive the following error:

"The stored procedure required to complete this operation could not be found on the server. 
Please contact your system administrator."
Msg 7311, Level 16, State 2, Line 1
Cannot obtain the schema rowset "DBSCHEMA_TABLES_INFO" for OLE DB provider "SQLNCLI" for linked 
server "<ServerName>". The provider supports the interface, but returns a failure code when it is used.

To correct this issue, you must run the instcat.sql script from the service pack against the 32-bit instance of SQL Server 2000 or MSDE.

[Top]

The following aspects of the SQL Server 2005 XQuery implementation are not documented in Books Online:

• Characters that are generated by CDATA sections are not considered to be white-space characters. For example, select cast(''as xml).query('<a> <![CDATA[ ]]> {"abc"}</a>') returns <a> abc</a>.
  
  
• Construction of empty elements and attributes is supported.
  
  
• The namespace prefix xmlns identifies a namespace declaration attribute and cannot be redeclared in an XQuery expression. This behavior is required by the XQuery specification.
  
  
• Using 'for' with source expression () yields a static error.
  
  
• In an XML document that is constructed by using the query() method on the xml data type, a carriage return within a CDATA section becomes a line feed. The line feed is used instead of the earlier carriage-return entity reference (&#x0d;) for uniformity with text XML parsing.
  
  
• Transact-SQL user-defined functions that contain local-name() and namespace-uri() are deterministic.
  
  

[Top]

A string representation of an xsd:dateTime value that does not contain a date and time separator T or a time zone can be converted to an SQL datetime type in a value() method, as in the following example:

declare @aaa xml
set @aaa = '<AAA MyDate="2005/1/1 00:00:00"/>'
select @aaa.value('(//AAA)[1]/@MyDate', 'datetime')

[Top]

The following aspects of the SQL Server 2005 support for XML Schema are not documented in Books Online:

• The XML schema for Reporting Services (RDL) can be loaded into an XML schema collection.
  
  
• Values of type xsd:dateTime and xsd:time that contain second values that have more than three fractional digits do not return an error. Instead they are rounded off.
  
  
• An XML schema is rejected if maxInclusive is redefined in a derived type when base type has fixed="true".
  
  
• Trailing spaces in minInclusive, minExclusive, maxInclusive, and maxExclusive facets are ignored in derived types that restrict the xsd:dateTime, xsd:data, and xsd:time data types.
  
  

[Top]

Remote connections to a SOAP/HTTP endpoint may fail when the SQL Server service account is a domain account and authentication for the endpoint is set to INTEGRATED, even though local connections succeed. The problem can occur when the Service Principal Name (SPN) is registered to the local system account. You can work around the issue by either registering an SPN for the SQL Server Service account or specifying NTLM authentication for the endpoint. For more information about registering an SPN, see "Registering Kerberos Service Principal Names by Using Http.sys" in Books Online.

[Top]

In this release, Analysis Services uses an access control list (ACL) to secure the instance encryption key file. An ACL is an integral part of Windows security, and lets you more easily change the user account associated with the Windows service for an Analysis Services instance. The askeymgmt utility (askeymgmt.exe), which provided Data Protection API (DPAPI) management functionality for the instance encryption key file, is no longer necessary.

[Top]

When you write applications that use ADOMD.NET, you must redistribute ADOMD.NET along with your application. The ADOMD.NET installation file (SQLServer2005_ADOMD.msi) is available for download from this Microsoft Web site.

[Top]

If you install Excel (or any other client application) after installing Microsoft SQL Server 2005 Analysis Services, you can no longer reference the Analysis Services 9.0 OLE DB Provider by using the MSOLAP provider name. This happens because the client application installs the older PivoTable Service that overwrites the version-independent ProgID. For example, if you are using "provider=MSOLAP" in a connection string, the provider for SQL Server 2000 Analysis Services will be invoked. As a result, you may not be able to connect to a SQL Server 2005 Analysis Services server by using Excel. In the future, there will be an Office XP and Office 2003 update that you can use to update the provider that Excel uses. For now, to resolve this problem, repair the existing installation by running the following command at the command line:

setup.exe /qb INSTANCENAME=MSSQLSERVER REINSTALL=ALL

[Top]

If you have installed a 32-bit version of the instance rename tool on a 64-bit computer, you must uninstall the 32-bit version of the instance rename tool, and reinstall the 64-bit version of the tool from the SQL Server 2005 product CD. For more information, see Knowledge Base article 906161.

[Top]

If a local cube contains a password, the local cube itself must also be password encrypted. To encrypt a local cube, enter a password in the password connection string property named "Encryption Password." Creating the local cube in encrypted format helps protect sensitive information stored in local cube files, such as passwords and keys.

[Top]

If you upgrade the Database Engine to SQL Server 2005, you must migrate your Notification Services instances to SQL Server 2005. For more information about migrating Notification Services instances, see "Migrating Notification Services Instances" in the SQL Server 2005 Setup documentation or in SQL Server 2005 Books Online.

[Top]

If you use SQL Server Authentication when hosting the Notification Services engine or managing subscriptions, you must do one of the following when creating an instance of and initializing the Microsoft.SqlServer.NotificationServices.NSInstance class:

• Use the undocumented NSInstance(string instanceName, string sqlUser, string sqlPassword) constructor to create an instance of and initialize the NSInstance object;
  
  
• Use the default constructor and then use the undocumented Initialize(string instanceName, string sqlUser, string sqlPassword) method to initialize the NSInstance object; or
  
  
• If using COM interop, use the default constructor, set credentials using the SqlUser and SqlPassword properties, and then use the Initialize(string instanceName) method to initialize the NSInstance object.
  
  

Using the NSInstance class in these ways ensures that Notification Services has the SQL Server Authentication information before it attempts to obtain information about the instance from the Database Engine.

[Top]

When using SQL Server Authentication to connect to a Notification Services instance via Notification Services Management Objects (NMO), you use a Server object to obtain a NotificationServices reference, and then use this reference to get a Notification Services instance. When creating an instance of the Server object, you can specify a ServerConnection object that uses a SqlConnection object.

If you are using SQL Server Authentication to call instance and application management methods such as Create, Update, Drop, Enable, or Disable, the SqlConnection must not already be open. If it is, logon will fail because NMO management operations attempt to open the connection independently.

Therefore, make sure the SqlConnection is not opened before the Server object instance is created, or else use another ServerConnection constructor that does not use a SqlConnection object.

[Top]

Report Builder can run in either full trust mode or partial trust mode using a URL. The URL path used to launch report builder determines the trust mode.

If you are launching Report Builder in a full trust environment, use the following URL:

http://<localhost>/reportserver/reportbuilder/reportbuilder.application

If you are launching Report Builder in a partial trust environment, use the following URL:

http://<localhost>/reportserver/reportbuilder/reportbuilderlocalintranet.application

where <localhost> is the name of the computer that is running Report Server.

Depending on which URL you want the Report Builder button in Report Manager to launch, specify one of the following values for the ReportBuilderTrustLevel element in the RSWebApplication.config file: FullTrust or PartialTrust. This file can be found in the Report Manager installation directory. By default, FullTrust is specified.

In a partial trust environment, the Report Builder Help file (ReportBuilder.chm) cannot be accessed from Report Builder. However, the administrator can provide Report Builder users with a copy of the Help file.

[Top]

In the Reporting Services Managed Programming Reference Documentation, especially in the Reporting Services Web Services Class Library, some API topic syntax blocks include attribute descriptions before the class or method name. These attribute descriptions are an artifact of the process used to generate the documentation and can be ignored.

[Top]

To enable the Microsoft .NET Framework Data Provider for mySAP Business Suite for Reporting Services, you must perform the following steps to modify installed configuration files. These steps replace those documented in the "Microsoft .NET Data Provider for SAP" topic in Books Online. The actions are described in the steps below, followed by the feature and specific .config files on which to perform the steps.

1. Remove the comment marks (delete <!-- and --> characters from the beginning and end of the line) for this entry in the Extensions/Data section and save the file:
   
   

   <!-- <Extension Name="SAP" Type="Microsoft.Adapter.SAP.SAPConnection,Microsoft.Adapter.SAP.SAPProvider, Version=1.0.0.0, Culture=neutral, PublicKeyToken= 31bf3856ad364e35"/> -->

   Note:
   Line breaks have been added to improve readability. The Type value must be specified on a single line in the .config file.

2. Insert the following code in the PolicyLevel/CodeGroup section at the same level as the Microsoft_Strong_Name entry, and then save the file:
   
   

   <CodeGroup class="UnionCodeGroup" version="1" PermissionSetName="FullTrust" Name="Microsoft_Generic_Signing" Description="This code group grants code signed with the generic Microsoft key full trust. Used by the Microsoft .Net Data Provider for mySAP Business Suite."> <IMembershipCondition class="StrongNameMembershipCondition" version="1" PublicKeyBlob="00240000048000009400000006020000002400005253413100040000010001 00b5fc90e7027f67871e773a8fde8938c81dd402ba65b9201d60593e96c492651e889cc13f14 15ebb53fac1131ae0bd333c5ee6021672d9718ea31a8aebd0da0072f25d87dba6fc90ffd598e d4da35e44c398c454307e8e33b8426143daec9f596836f97c8f74750e5975c64e2189f45def4 6b2a2b1247adc3652bf5c308055da9" /> </CodeGroup>

   Note:
   Line breaks have been added to improve readability. The PublicKeyBlob value must be specified on a single line in the policy file.

To enable the data provider on the report server, perform step 1 on rsreportserver.config and step 2 on rssrvpolicy.config. The default installation directory for these files is C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer.

To enable the data provider in Report Designer, perform step 1 on RSReportDesigner.config and step 2 on RSPreviewPolicy.config. The default installation directory for these files is C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies.

[Top]

SQL Server 2005 Management Studio does not support enabling SQL Server 2000 publications for non-SQL Server Subscribers. To enable a SQL Server 2000 publication for non-SQL Server Subscribers, use the Create Publication Wizard, which is available in SQL Server 2000 Enterprise Manager. In the Create Publication Wizard, on the Specify Subscriber Types page, select Heterogeneous data sources, such as Oracle or Microsoft Access.

[Top]

For more information, see section 3.5.20 Existing Jobs May Fail When You Reinstall Multiple Instances on the Same Computer.

[Top]

With SQL Server 2005 Developer or Standard Edition installed, you can install the SQL Server Mobile Server Tools.

[Top]

When you run the SQL Server Mobile Server Tools Setup, the readme (ssmreadme.htm) file is installed by default in C:\Program Files\Microsoft SQL Server 2005 Mobile Edition\Docs\xx, where xx is a two-character designator for the installed language. The readme file is installed in the subdirectory of the installation directory that is specified in the Microsoft SQL Server Version page of Microsoft SQL Server Mobile Server Tools setup.

[Top]

In SQL Server 2005, database diagram support objects are installed on a database in which the support objects have not yet been installed if a member of the db_owner fixed database role performs one of the following operations:

• Expands the Database Diagrams folder
  
  
• Creates a new diagram
  
  
• Explicitly chooses to install the objects from the context menu
  
  

The installation of these support objects can fail on a database that has been attached or restored from another instance of SQL Server. This can occur when the database owner name (stored in the database) is not a valid logon for the instance of SQL Server the database is being attached or restored to.

Use the following Transact-SQL expression to change the database owner to a valid logon for the instance of SQL Server. Then, retry the database diagram operation.

ALTER AUTHORIZATION ON DATABASE::database_name TO valid_login 

[Top]

64-bit SQL Server 2005 installs 32-bit versions of some tools. When run on 64-bit operating systems, these tools run in the WOW environment and in some conditions may perform slowly. To improve the performance of 32-bit tools, connect to 64-bit SQL Server with tools running on a 32-bit operating system. SQL Server 2005 Business Intelligence Development Studio, the 32-bit development environment for business intelligence solutions, is not designed to run on the IA64 64-bit architecture and is not installed on IA64 servers. For additional information concerning SQL Server tools on 64-bit operating systems, see Knowledge Base article 906892.

[Top]

If Help is configured to prefer online versions of topics in Help results, F1 Help might return incorrect topics. To reconfigure Help to prefer local versions, on the Tools menu, click Options, click the Online page under Help, click Try local first, then online, and then click OK.

[Top]

The readme files for Visual Studio-based SQL Server samples instruct you to create a key file named samplekey.snk in the "install directory." You should create this file in the root folder of each sample that requires it.

[Top]

The following information applies to Notification Services samples:

• If you are deploying a Notification Services sample using an account that is the database owner or a system administrator, you do not have to grant SQL Server permissions to the account. Granting these permissions might now result in an error, which you can ignore. When you deploy your own applications, you should use accounts with lower privileges to help improve security.
  
  
• The Notification Services samples refer to a dialog box named "Database Access." This dialog box is now named User Mapping.
  
  

[Top]

SQL Server 2005 Business Intelligence Development Studio, the 32-bit development environment for business intelligence solutions, is not designed to run on the IA64 64-bit architecture and is not installed on IA64 servers. This prevents samples that require Business Intelligence Development Studio from being run on IA64 servers. For additional information, see Knowledge Base article 906892.

[Top]

Use the following procedure to run the Build Cleanup Wizard.

[Top]

If you have installed SQL Server as a failover cluster, you must record the group name before running the Build Cleanup Wizard. We also recommend that you record the list of nodes if you want to install SQL Server later with the same node configuration.

When the Build Cleanup Wizard runs, you will be prompted to enter the remote logon password for the current logged-on user to uninstall all nodes of the failover cluster. The logged-on user must be an administrator on all nodes. When prompted by the wizard, enter the password, and then click Next.

[Top]

If the Build Cleanup Wizard indicates that an instance of SQL Server 2005 failed to uninstall, rerun the Wizard until no SQL Server instances are detected. To view the results of the uninstall process, open the summary.txt for each instance, located in C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG.

In some cases, the Build Cleanup Wizard might incorrectly report a failure due to an error in uninstalling MSXML. This is a known issue that affects SQL Server 2005 Beta installations prior to IDW13.

SQL Server 2005 Database services installation might fail with the error, "1603 Fatal error." If you encounter this error, click OK and continue. This is a known issue that affects SQL Server 2005 Beta installations prior to CTP February 2005. To verify that the components uninstalled successfully, click the link on the status bar, view the summary.txt file, and make sure that each component says "Uninstall: Successful."

If you find a failure, you must view the log files of the failed component for troubleshooting purposes. The summary.txt file has the location of the log for the failed component. The SQLDATAROOT will not be recorded if the uninstall returns failure. Note that the .NET Framework and SQL Native Client will be uninstalled only if all components are uninstalled successfully.

To save an existing Full-Text Search configuration, back up the Windows registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSearch\GlobalAdminBlob. Back up any customized noise word and thesaurus files from C:\Program Files\Microsoft SQL Server\MSSQL.X\MSSQL\FTData.

To save the configuration files for a Reporting Services installation, use the Internet Information Services plug-in for SQL Server Configuration Manager to back up any customized virtual directory settings. Also, back up the following files in the report server installation folders C:\Program Files\Microsoft SQL Server\MSSQL.X\ReportServer and C:\Program Files\Microsoft SQL Server\MSSQL.X\ReportManager:

• rsreportserver.config
  
  
• rssrvpolicy.config
  
  
• rswebapplication.config
  
  
• rsmgrpolicy.config.
  
  

[Top]