|
 |
|
| |
|
Announcements from SQLUG.be
|
| |
SQL2005 SP3 released
|
What's New in SQL Server 2005 SP3
Microsoft SQL Server 2005 Service Pack 3 (SP3) contains all the
cumulative updates for SQL Server 2005, and fixes to issues that have
been reported through our customer feedback platforms. These include
supportability enhancements and issues that have been reported through
Windows Error Reporting.
Additionally, the following components have new or improved features.
 Database Engine
-
By default, when you use the DBCC CHECKDB, DBCC CHECKALLOC, DBCC
CHECKTABLE, or DBCC CHECKFILEGROUP commands on a server that is running
SQL Server 2005 SP3, all error messages are displayed. If you specify
or omit the ALL_ERRORMSGS option, it has no effect. In earlier versions
of SQL Server, only the first 200 error messages for each object are
displayed if you do not specify ALL_ERRORMSGS.
Notification Services
-
This release of the SQL Server 2005 Notification Services components
provides support for running SQL Server 2005 Notification Services
against either an instance of the SQL Server 2005 Database Engine or
the SQL Server 2008 Database Engine.
Replication
-
The sp_showpendingchanges stored procedure was updated with a new parameter, @show_rows. This parameter helps identify the pending changes of subscribers. For more information, see sp_showpendingchanges (Transact-SQL).
Reporting Services
-
Introduces support for creating report models that are based on
Teradata databases. You can generate report models that are based on a
Teradata database that is running version 12.00 or version 6.20 by
using Model Designer in Business Intelligence Development Studio and
Report Manager. For more information, see Creating and Using Teradata-Based Report Models.
-
Introduces changes to the PDF rendering extension, which supports ANSI
characters and can translate Unicode characters from Japanese, Korean,
Traditional Chinese, Simplified Chinese, Cyrillic, Hebrew, and Arabic.
When it is possible, the PDF rendering extension now embeds the subset
of each font that is needed to display the report in the PDF file. For
more information, see Designing for PDF Output.
-
In SharePoint integrated mode, reports typically run slower than the
same reports run in native mode. The main cause of this latency can be
attributed to SharePoint object model calls that are made. In SQL
Server 2005 SP3, the number of SharePoint object model calls that SQL
Server 2005 Reporting Services (SSRS) makes are optimized. This
optimization reduces some of the latency when you compare report
performance with native mode.
Additional Information
|
| |
|
|
|
|
|
|
|
|
|