22 Apr 06 SQL Server 2005 SP1 Released

微软今天release 了 SQL Server 2005 SP1。
链接在这里 SQL Server 2005 SP1。
上去看了看，连中文版都有了，微软这帮人真是迅速。不过根据安装说明，SP1将会占用1G空间。联想起前几次试用Sql Server 2005 ，那感觉怎一个恐怖了得。几个小小的查询就弄得占用了大概500+的内存，直接把我的 Vmware GSX Server Virtural Host down掉。后来勉强设置了内存上限，居然仍然超限50m+。另外跑了个小查询居然跟我说

A list of the bugs that have been fixed in SQL Server 2005 Service Pack 1

View products that this article applies to.

Article ID	:	913090
Last Review	:	April 18, 2006
Revision	:	2.0

INTRODUCTION

This article contains information about the bugs that have been fixed in Microsoft SQL Server 2005 Service Pack 1.

Note

•	Other fixes may be included in the service pack that are not documented.
•	This list will be updated as more articles are released.

For more information about how to obtain SQL Server 2005 service packs, click the following article number to view the article in the Microsoft Knowledge Base:

913089 (http://support.microsoft.com/kb/913089/) How to obtain the latest service pack for SQL Server 2005

MORE INFORMATION

For more information about the bugs that have been fixed in SQL Server 2005 Service Pack 1, click the following article numbers to view the articles in the Microsoft Knowledge Base:

910375 (http://support.microsoft.com/kb/910375/)	FIX: No table headers appear in the Excel report when you use SQL Server 2005 Reporting Services to export information to Excel
910376 (http://support.microsoft.com/kb/910376/)	FIX: You may unexpectedly receive a zero or null return value when you run an MDX query on relational OLAP partitions in SQL Server 2005 Analysis Services
910414 (http://support.microsoft.com/kb/910414/)	FIX: You may receive an error message when you try to load data by using CLR functions in a Transact-SQL job in SQL Server 2005
910416 (http://support.microsoft.com/kb/910416/)	FIX: Error message when you run certain queries or certain stored procedures in SQL Server 2005: “A severe error occurred on the current command”
910418 (http://support.microsoft.com/kb/910418/)	FIX: You may receive an error message when you try to connect to SQL Server 2005 Analysis Services by using an ADO connection string that uses the CustomData property
911912 (http://support.microsoft.com/kb/911912/)	FIX: You experience low CPU spikes at set intervals even when there is no user activity in SQL Server 2005
911937 (http://support.microsoft.com/kb/911937/)	FIX: The schema that indicates the Identity column in the source database is not transferred to the destination database when you try to transfer objects from a source database to a destination database by using SQL Management Objects in SQL Server 2005
912001 (http://support.microsoft.com/kb/912001/)	FIX: Error message when you design aggregations in the Aggregation Design Wizard in SQL Server 2005 Analysis Services: “Internal error an unexpected exception occurred”
912016 (http://support.microsoft.com/kb/912016/)	FIX: Error message when you process a dimension by using the Process Update processing option or the Process Default processing option in SQL Server 2005 Analysis Services: “Operation has been cancelled”
912017 (http://support.microsoft.com/kb/912017/)	FIX: Error message when you connect to an instance of SQL Server 2005 Analysis Services: “A connection cannot be made. Ensure that the server is running.”
912021 (http://support.microsoft.com/kb/912021/)	FIX: You may receive an error message when you try to use backup software to back up a database in SQL Server 2005 for Itanium-based Systems
912136 (http://support.microsoft.com/kb/912136/)	You may experience problems after you run the Business Intelligence Wizard to add time calculations in SQL Server 2005 Analysis Services
912322 (http://support.microsoft.com/kb/912322/)	FIX: An application query that reads lots of data may be slow, and the SQL Server service may take a long time to start in SQL Server 2005
912419 (http://support.microsoft.com/kb/912419/)	FIX: The attribute hierarchy for an attribute still appears when you browse a cube even if you set the value of the AttributeHierarchyVisible property for the attribute to False in SQL Server 2005 Analysis Services
912422 (http://support.microsoft.com/kb/912422/)	FIX: The synchronous database mirroring session status may remain disconnected when you set up synchronous database mirroring but do not configure a witness database and you run a DBCC STACKDUMP command in SQL Server 2005
912423 (http://support.microsoft.com/kb/912423/)	FIX: Memory leaks occur when you use Fuzzy Lookup and Fuzzy Grouping to transform a SQL Server 2005 Integration Services package
912429 (http://support.microsoft.com/kb/912429/)	FIX: Error message when you run an MDX statement to query data from a SQL Server 2005 Analysis Services database: “Internal error An unexpected exception occurred”
912439 (http://support.microsoft.com/kb/912439/)	FIX: Error message when you try to run several queries on large data sets at the same time in SQL Server 2005: “701 There is insufficient system memory to run this query”
912446 (http://support.microsoft.com/kb/912446/)	FIX: You receive an incorrect result when you execute a DISCOVER request or call the AdomdConnection.GetSchemaDataSet method against a SQL Server 2005 Analysis Services server
912450 (http://support.microsoft.com/kb/912450/)	FIX: You may receive a null value for a calculated member when you run an MDX query in SQL Server 2005 Analysis Services
912459 (http://support.microsoft.com/kb/912459/)	FIX: Error message when you query data from a SQL Server 2005 Analysis Services database by using the HTTP protocol: “Xml Parsing failed”
912471 (http://support.microsoft.com/kb/912471/)	FIX: The replication on the server does not work any longer when you manually fail over databases in SQL Server 2005
912472 (http://support.microsoft.com/kb/912472/)	FIX: An incorrect result may appear in the subscribing database when you set database mirroring for a database and database failover occurs in SQL Server 2005
912702 (http://support.microsoft.com/kb/912702/)	FIX: Error message when you run an MDX query in SQL Server 2005 Analysis Services: “Dimension attribute was not found”
912705 (http://support.microsoft.com/kb/912705/)	FIX: Error message when you try to drill through a report in SQL Server 2005 Reporting Services: “An internal error occurred on the report server. See the error log for more details”
912885 (http://support.microsoft.com/kb/912885/)	FIX: You may receive an access violation error message when you run a parallel execution plan in SQL Server 2005
913363 (http://support.microsoft.com/kb/913363/)	FIX: You receive an error message when you use SQL Server 2005 Reporting Services to run a report that has two or more parameters

Tags: Reviews