When installing this CTP release of SQL Server 2005 with Visual Studio 2005 Beta 2, 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 2.0 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:

• SQL Server 2005
  
  
• Visual Studio 2005
  
  
• .NET Framework 2.0
  
  

[Top]

Running Setup from a UNC path across the network may cause Setup to fail if the UNC path has been mapped to a drive letter. Instead of running Setup from a mapped drive, navigate to the UNC path where SQL Server installation files are located, and then run Setup.exe.

[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]

Reporting Services requires enabling ASP.NET on Windows Server 2003. However, ASP.NET is not enabled by default; therefore, before you install a report server on Windows Server 2003, you must manually enable ASP.NET. You can enable ASP.NET using the Configure Your Server Wizard or Add or Remove Programs in Control Panel.

[Top]

Because the Microsoft Distributed Transaction Coordinator (MS DTC) is not completely configured in Windows, applications may 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. In order to use SQL Server 2005 samples or to test sample code in 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]

Internet Information Services (IIS) 6.0 returns a "Service Unavailable" error message when you run Reporting Services in Windows-on-Windows 64 (WOW64) x86 emulation mode. To avoid this error, you must configure IIS to allow 32-bit ASP.NET applications to run.

[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 recreate 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]

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 using Add or Remove Programs. On a cluster, uninstall SQL Native Client from all nodes. Then, run SQL Server setup again.

[Top]

If you install SQL Server 2005 from a network share to a computer running Microsoft Windows Server 2003 Service Pack 1 (SP1) or later, or a version of Windows XP later than SP2, online Help topics may 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 on accessing the Setup documentation, see Section 3.1 Accessing Setup Documentation.

[Top]

Changing the Windows account under which any SQL Server service runs is not supported in this release. If you change any service account you may be unable to restart or uninstall the corresponding SQL Server component, and you may lose data. If you need to change a service account, you should uninstall and reinstall SQL Server.

[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 may 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 Access clients in SQL Server 2005, use SQL Server Configuration Manager. 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 topics "Password Complexity and Expiration" and "CREATE LOGIN (Transact-SQL)" in SQL Server Books Online.

[Top]

When an instance of SQL Server 2005 is uninstalled from a side-by-side configuration on a computer running on 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]

A system job category named Log Shipping has been added in this release. If a current installation of SQL Server already contains a user-created job category named Log Shipping, you must rename it before upgrading to this CTP release. Otherwise, the upgrade process will fail. For more information, see Section 3.2 Upgrading to SQL Server 2005.

[Top]

Setup will prevent you from upgrading SQL Server 2000 (64-bit) to SQL Server 2005 (IA64) when Database Engine components are installed with Analysis Services components. To upgrade the databases to SQL Server 2005, you must first install a new instance of SQL Server 2000 (64-bit) Database Components, migrate the existing databases to this new instance, and then upgrade this new instance. For more information, see "Using the Copy Database Wizard" in SQL Server Books Online for SQL Server 2000.

[Top]

Verify the SQL Server 2000 global proxy account login credentials, and set it to a valid Windows login account before upgrading from SQL Server 2000 to SQL Server 2005. For more information, see the "xp_sqlagent_proxy_account" reference topic in SQL Server Books Online for SQL Server 2000.

[Top]

When you install SQL Server 2005 on a French or German operating system that is not part of a domain, and you select Network Service account or Local Service account in the Service Account dialog box during Setup, the following error may occur: "Error 1068: The dependency service or the dependency group could not be started." To resolve this issue, restart Setup and select Local System account instead.

[Top]

[Top]

Setup from the command prompt may fail when you uninstall an earlier CTP release of SQL Server 2005 using SAVESYSDB and then install this release 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]

The DBCC CHECKDB, DBCC CHECKFILEGROUP, and DBCC CHECKTABLE statements now perform new checks if no errors are found in the database, filegroup, or table, respectively. These additional checks are logical validations of indexed views and XML indexes, and are run by default. You may notice an increase in the run times of these DBCC statements after you upgrade a database that contains indexed views to SQL Server 2005, or when you define an XML index on the database. To determine whether an increase in the run time of a DBCC statement may be the result of these new logical validations, check for the value "DBCC IVIEW CHECK" in the command column of the sys.dm_exec_requests dynamic management view. To avoid performing these new checks, specify the WITH PHYSICAL_ONLY option when executing these DBCC statements.

[Top]

For this release, optimal database mirroring performance will be obtained using SAFETY=OFF. Users evaluating high-availability workloads (with SAFETY=FULL) that generate large amounts of transaction log data may experience slower performance

[Top]

Books Online incorrectly states that point-in-time restore is supported only in the Enterprise Edition. Point-in-time restore is supported in all editions of SQL server 2005.

[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 Enterprise, Standard, or Workgroup Edition or if a previous installation of SQL Server is present. Named Pipes connectivity is only available 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]

If a pre-June CTP Database Engine Tuning Advisor (DTA) client was used to tune SQL Server 2000 or pre-June CTP release of SQL Server 2005 (including SQL Server 2005 Beta 2), there may be problems if a June 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 only be executed by a member of the sysadmin fixed server role.

[Top]

Client connections to an instance of the SQL Server Database Engine running on Windows Server 2003 Service Pack 1 may fail with the following error: "ProviderNum: 7, Error: 10054, ErrorMessage: "TCP Provider: An existing connection was forcibly closed by the remote host"." This may 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 Books Online, the dynamic management view topic "sys.dm_db_session_space_usage" contains incorrect column names. The last two columns should be internal_objects_alloc_page_count and internal_objects_dealloc_page_count, respectively. The descriptions for the columns are correct.

[Top]

In this release, the partition_number column in the sys.dm_db_index_operational_stats dynamic management function returns incorrect values.

DML operations on an index do not correctly update the following columns. However, these columns do return correct values when the table is a heap:

• leaf_insert_count
  
  
• nonleaf_insert_count
  
  
• row_lock_count
  
  
• page_lock_count
  
  

[Top]

If you use a 64-bit MDAC client to connect to a local 32-bit named instance of SQL Server 2005 or a 32-bit MDAC client to connect to a local 64-bit named instance of SQL Server 2005, either the SQL Browser service must be running or the client must specify the full connection string, including the port.

[Top]

In SQL Server Books Online, the topic "Serialization of XML Data" 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]

In this release, online index operations may wait for database mirroring log transactions to complete before completing the index operation. An S lock or SCH-M lock is held during this time.

[Top]

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 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]

There must be only one serialization of a user-defined type (UDT) object. 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 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 ('@udt'): Data type 0xF0 has invalid data specified."
  
  
• During DBCC, the bytes stored in a 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 Multidimensional Expressions (MDX) Aggregate function now supports semi-additive measures contained by cubes in Analysis Services. The Aggregate function lets you aggregate such measures while preserving their semi-additive functionality.

[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]

The following MDX functions are either new or have updated functionality in this release of Analysis Services.

In previous versions of Analysis Services, an error occurred if the WHERE clause resolved to an empty set. Analysis Services now supports MDX SELECT statements in which the WHERE clause resolves to an empty set. If a WHERE clauses resolves to an empty set, the MDX SELECT statement returns an empty cellset.

[Top]

Applying time intelligence to a cube containing role-playing dimensions (a single database dimension with multiple cube dimensions) causes the processing of other objects based on the database dimension, including cubes and mining models, to fail. For example, the AdventureWorks sample Analysis Services database has a cube with role-playing dimensions. Applying time intelligence to this sample cube will cause the processing of the mining models contained in the sample database to fail.

The Business Intelligence Wizard targets a single cube dimension when applying time intelligence. The wizard creates an attribute in the corresponding database dimension for the targeted cube dimension to hold the time intelligence calulations and specifies an unqualified default member for the attribute. The wizard then disables the attribute in all other cube dimensions based on the database dimension. As a result, other objects based on the database dimension, including cubes and mining models, fail while processing because these other objects have not disabled the attribute included in the database dimension.

To resolve this issue, apply time intelligence with the Business Intelligence Wizard and then disable the calculated attribute where applicable in other objects that use the database dimension.

[Top]

Processing fails if a mining model uses the Microsoft Time Series algorithm and the model's AllowDrillthrough property is set to true (the default setting). To process a mining model that uses the Microsoft Time Series algorithm, set the mining model's AllowDrillthrough property to false. Setting this property to false does not prevent the drillthrough operation on a mining model that was created with the Microsoft Time Series algorithm. You can set the AllowDrillthrough property on either the Completing the Wizard page of the Data Mining Wizard or in the Properties pane of Data Mining Designer.

[Top]

When saving a package to the SQL Server, you may receive the following error: "Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum) A connection was successfully established with the server, but an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The certificate's CN name does not match the passed value.) (.Net SqlClient Data Provider)" To avoid this problem, you must enable Secure Socket Layer (SSL) encryption on SQL Server 2005. Knowledge Base article 276553 describes how to enable SSL encryption.

[Top]

In this release, the following issues exist for transfer tasks:

• The Transfer SQL Objects task transfers objects to the master database, regardless of which database you specify in the DestinationDatabase property of the task. The task succeeds although the transfer did not copy the objects to the correct database.
  
  
• The Transfer Error messages task transfers messages only from SQL Server 2005 to SQL Server 2000. Transfers between other versions of SQL Server fail, including transfers from SQL Server 2000 to SQL Server 2005.
  
  
• The Transfer Databases task fails if a database with the same name exists at the destination, even if the DestinationOverwrite property has been set to True. To avoid this problem, include an Execute SQL task to run an SQL statement that drops the database in the package.
  
  
• Migration of SQL Server 2000 transfer tasks to SQL Server 2005 is incomplete. In SQL Server 2000, all transfer tasks use OLE DB connections, whereas in SQL Server 2005, all transfer tasks use SMO connection managers. The Package Migration Wizard does not migrate the connections in the transfer task; therefore, the migrated transfer tasks will not work. To repair the tasks, you must add SMO connection managers to the migrated package and configure the transfer tasks to use the SMO connection managers.
  
  

[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]

The source files for the Notification Services tutorial were not updated with the product documentation. If you attempt to use the source files as documented, you will receive errors when using the tutorial. To use the Notification Services tutorial with this release, you must make the following changes to the source files:

• In TutorialICF.xml, add the following code before the InstanceName element:
  
  

  <ParameterDefaults> <Parameter> <Name>_DBEngineInstance_</Name> <Value>%COMPUTERNAME%</Value> </Parameter> <Parameter> <Name>_ServerName_</Name> <Value>%COMPUTERNAME%</Value> </Parameter> <Parameter> <Name>_InstancePath_</Name> <Value>%ProgramFiles%\Microsoft SQL Server\90\Samples\Notification Services\tutorial\</Value> </Parameter> </ParameterDefaults>

• In the ApplicationDefinitionFilePath element in TutorialICF.xml, change "FinalWeatherADF.xml" to "WeatherADF.xml".
  
  
• Make the following replacements in all subscription, event, and notification script files:
  
  
  • Replace "WeatherEvents" with "WeatherData".
    
    
  • Replace "WeatherSubscriptions" with "WeatherCity".
    
    
  • Replace "WeatherNotifications" with "WeatherAlerts".
    
    
  • Replace "WeatherSPs" with "WeatherSPEventProvider".
    
    

[Top]

In Notification Services 2.0 instances, event views are materialized when needed. If you disable and stop an instance when the view is not materialized, and then migrate the instance to SQL Server 2005, you will receive the following error message during the update step of the migration process: "An attempt to run a Transact-SQL CREATE TRIGGER statement failed." If this happens, run the following Transact-SQL statements to create the missing view. Replace the angle-bracket text with the names for your instance and application:

USE [<InstanceName><ApplicationName>];
GO
CREATE VIEW [dbo].[<EventClassName>] AS 
SELECT * FROM [dbo].[NS<EventClassName>Events];
GO

You need to perform this step for all event classes for which the view does not exist. Because the view is materialized at different times for different event classes and applications, the view may exist for some event classes and not for others. After creating the view or views, resume the migration by running the update step again.

[Top]

The topic "Retrieving XML Data" in SQL Server Books Online includes syntax and an example that shows how to retrieve data from an XML Web service or URL. The syntax and example in the documentation are incorrect. This readme item provides the correct syntax and example strings.

The connection string must contain only the URL to the Web service or XML document. Do not include the "URL=" attribute in the connection string. Do not specify SoapAction as a connection string parameter. The correct connection string syntax is as follows:

http://<URL to Web service or XML document>

The following example shows how to connect to the Report Server Web service:

http://localhost/reportserver/reportservice2005.asmx

The query must include a single SoapAction element if you are retrieving XML data from a Web service. Optionally, you can also specify an element path and a namespace on the Query element. The correct query syntax is as follows:

<Query xmlns=namespace>
    <SoapAction>Web service namespace/SOAP method</SoapAction>
    <Element Path />
</Query>

The following example shows how to return the contents of the report server database using the ListChildren SOAP method:

<Query>
    <SoapAction>http://schemas.microsoft.com/sqlserver/2005/03/23/reporting/reportingservices/ListChildren</SoapAction>
</Query>

For this example to work, you must have items stored in the report server. The credential type must be integrated security. All parameters on a SOAP method must be specified as a Dataset parameter (in Report Designer, use the Parameters tab of the Datasets dialog box). For the ListChildren method, the parameters are Item and Recursive. Item should be set to /. Recursive should be set to Null.

[Top]

Users who perform a files-only installation of Reporting Services will get an error when attempting to set the Report Server Windows service account. A files-only installation is performed when you select the Install but do not configure the server option in the SQL Server Installation Wizard. To deploy a report server after a files-only installation, you must use the Reporting Services Configuration tool. When using the Reporting Services Configuration tool, a database access rights error occurs when you attempt to configure the Report Server Windows service before the report server database is created. The error that occurs is "The Reporting Services rights were not applied properly. The user may still not have appropriate access to the Reporting Services resources." The Exception details dialog box provides the following message: "Incorrect syntax near 'USER' ". The workaround is to configure the report server database first. To configure the report server database, use the Database Setup page in the Reporting Services Configuration tool.

[Top]

Undo operations in Model Designer do not work when focus is set on the Properties window in Business Intelligence Management Studio. To undo an operation, click in the Model Design window before attempting an undo operation.

[Top]

• End user sorting on Report Builder reports with more than one group may result in the wrong sort order. No data is lost or incorrectly reported. To turn off the end user sorting option for a report, on the Report menu, select Report Properties and then clear the User Sorting check box.
  
  
• When using the Report Builder Sort and Group dialog box, selected page break options are not saved unless the user also specifies sorting on the group.
  
  

[Top]

You can build a report that uses data from a SQL Server 2000 Analysis Services MDX query. However, you must manually add ConnectTo=8.0 to the data source connection string. You must type the property information into the connection string. The Data Source dialog box does not add the property for you.

The following example illustrates the syntax you must use:

Data Source="(Local)"; Initial Catalog="Adventure Works AS"; ConnectTo="8.0"

[Top]

Analysis Services and Report Builder are now integrated. Below are known issues:

• When selecting an Analysis Services-based report model, select a perspective within the model and not the top-level model itself.
  
  
• Users are limited to the number of entities and their relationships that can be explored.
  
  
• The parent-child attribute relationships are not visible.
  
  
• The sort order applied by Analysis Services is not preserved.
  
  
• Reports that contain Key Performance Indicator (KPI) images cannot be rendered or saved.
  
  

For more information about Analysis Services and Report Builder in this release, see Knowledge Base Article 899825.

[Top]

In this release, publishing an Oracle database will fail if you use the Oracle Publication Wizard on a Distributor running on a 64-bit instance of SQL Server 2005 unless the registry has been preset to allow the Oracle OLEDB Provider to run in process with SQL Server. To preset the registry, use the regedit.exe utility to set the AllowInProcess DWORD value in the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Providers\OraOledb.Oracle" at the Distributor to a data value of 00000001.

[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]

Upgrade Advisor is available in English only. Upgrade Advisor will be available in all supported languages when SQL Server 2005 is released.

[Top]

When you install Upgrade Advisor, its Setup program does not check for all Upgrade Advisor prerequisites. For a list of prerequisites, see "Using Upgrade Advisor to Prepare for Upgrades" in the SQL Server Setup documentation.

[Top]

You can run Upgrade Advisor against remote servers. However, you cannot analyze instances of Reporting Services on remote servers in this release.

[Top]

In this release, you cannot use Upgrade Advisor to analyze an instance of SQL Server 7.0.

[Top]

Clicking How Do I? on the Help menu in Business Intelligence Development Studio may cause both Microsoft Document Explorer and Business Intelligence Development Studio to quit. This problem only arises if this CTP release is installed, uninstalled, and then reinstalled. To solve this problem, open Microsoft Visual Studio 2005 Documentation once from the Microsoft Visual Studio 2005 Beta 2 program group in the Start Menu.

[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]

To solve this problem for Help in SQL Server Management Studio, open SQL Server Books Online once from the Microsoft SQL Server 2005 CTP program group in the Start menu. To solve this problem for Help in Business Intelligence Development Studio, open Microsoft Visual Studio 2005 Documentation once from the Microsoft Visual Studio 2005 Beta 2 program group in the Start menu.

[Top]

In Japanese builds, search does not work properly for local Help topics. To use Help search, you must configure Help search to use online content and disable local content.

[Top]

The MARS data access sample, which is located at C:\Program Files\Microsoft SQL Server\90\Samples\Engine\Data Access\ADO\MARS when SQL Server 2005 Samples are installed, does not run correctly in this release due to late-breaking product changes.

[Top]

The shared data source contains a syntax error that causes a connection error at run time. To work around the error, edit the shared data source so that it includes quotation marks around the data source name.

[Top]

Support for the 64-bit platform is limited in this release. 64-bit support is as follows:

• Supported components include Database Engine, Replication, and Notification Services.
  
  
• Core RDBMS functionality is supported on the 64-bit platform.
  
  
• SQL Server Native Client is available on the 64-bit platform. MDAC has been removed for this release.
  
  
• SQL Server Integration Services (SSIS) packages are platform independent, so a package can be created on a 32-bit platform and executed through a 64-bit command prompt tool. There is no 64-bit DTExecUI to launch SSIS packages in this release. The DTExecUI installed with 64-bit tools always launches packages in a 32-bit process.
  
  
• Replication supports 32-bit and 64-bit versions of SQL Server in the same topology. All replication features are supported on the 64-bit version with the following considerations:
  
  
  • Push subscriptions from a 64-bit Distributor require the appropriate 64-bit OLEDB provider or ODBC driver at the Distributor; pull subscriptions from a 64-bit Subscriber require the appropriate 64-bit provider or driver at the Subscriber. For more information about push and pull subscriptions, see "Subscribing to Publications" in SQL Server 2005 Books Online.
    
    
  • To use Windows Synchronization Manager on a 64-bit Subscriber running in Windows on Windows mode (WOW64), you must launch the executable mobsync.exe directly from the \Windows\Syswow64 directory, rather than from the Start menu. Launching the executable directly ensures that the correct version is used. For more information about WOW64 support, see "Hardware and Software Requirements for Installing SQL Server in SQL Server 2005 Setup Help." For more information about Windows Synchronization Manager, see "Windows Synchronization Manager" in SQL Server 2005 Books Online.
    
    
  • Transformable push subscriptions from a 64-bit Distributor are not supported, because the necessary 64-bit Data Transformation Services (DTS) components are not available. Pull subscriptions from a 32-bit installation of SQL Server 2005 should work with a 64-bit Publisher or Distributor. For more information about transformable subscriptions, see "Transforming Published Data" in SQL Server 2005 Books Online.
    
    

[Top]

The Surface Area Configuration tool may produce unhandled exceptions when managing services and connections on a 64-bit server. This may happen in the following circumstances:

• You are running the Surface Area Configuration tool on a 64-bit server and you attempt to change the local service or connection settings.
  
  
• You are running the Surface Area Configuration tool to manage a remote server, the remote SQL Server instance is running in Windows on Windows (Wow) mode, and you attempt to change service or connection settings on the remote server.
  
  

To change service and connection settings in these circumstances, use SQL Server Configuration Manager.

[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 may 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 may fail with 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 hyperlink 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]

If you change Error Reporting and Feature Usage settings on the passive node of a failover cluster, the changes may be overwritten when services from the active node fail over to the passive node. We therefore recommend that you change Error and Usage Reporting settings only on the active node of the cluster. For more information, see "Error and Usage Report Settings" in Books Online.

[Top]

SQL Server Error and Usage Reporting will incorrectly report that SQL Server registry keys related to feature usage and error reporting are corrupt in the following cases:

• If you do not install Database Engine, Analysis Services, or Reporting Services components as part of your SQL Server 2005 installation. To resolve this issue, do not enable the SQL Server Error and Usage Reporting feature during Setup if at least one of these components is not being installed.
  
  
• If you install a 32-bit instance of SQL Server 2005 on a computer running on a 64-bit operating system in Windows-on-Windows 64 (WOW) mode. To resolve this issue, do not enable the SQL Server Error and Usage Reporting feature when installing SQL Server 2005 32-bit in WOW mode.
  
  

When these errors occur, you will not be able to manage the Error Reporting and Feature Usage Reporting settings after installation.

[Top]

You can use the Surface Area Configuration tools to configure the surface area of a SQL Server failover cluster. However, you must connect the tool to the cluster's virtual server.

[Top]

In SQL Server 2005, database diagram support objects are installed on a database in which the support objects have not yet been installed and 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 may occur when the database owner name (stored in the database) is not a valid login in 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 login in the instance of SQL Server. Then retry the database diagram operation.

ALTER AUTHORIZATION ON DATABASE::database_name TO valid_login 

[Top]