Cookies op Tweakers

Tweakers maakt gebruik van cookies, onder andere om de website te analyseren, het gebruiksgemak te vergroten en advertenties te tonen. Door gebruik te maken van deze website, of door op 'Ga verder' te klikken, geef je toestemming voor het gebruik van cookies. Wil je meer informatie over cookies en hoe ze worden gebruikt, bekijk dan ons cookiebeleid.

Meer informatie

Door , , 2 reacties
Bron: Microsoft, submitter: howbizar

Windows logo (75 pix)Microsoft heeft verleden week service pack 2 voor versie 2008 van SQL Server uitgebracht. Downloads zijn beschikbaar voor 32bit-, 64bit- en ia64-omgevingen, en zijn rond de 350MB groot. Nieuw in de service pack zijn onder andere ondersteuning voor 15k-partitioning, rapportering van SharePoint-services en het managen van meer dan één server. Daarnaast zijn er natuurlijk ook een hoop bugfixes doorgevoerd. De release notes voor SP2 zijn hieronder te vinden.

What's New:
  • 15K partitioning Improvement. Introduced support for a maximum of 15,000 partitions in tables and indexes in Microsoft SQL Server 2008 Service Pack 2 in the Enterprise, Developer and Evaluation Editions. For details on how this support can be enabled and disabled, along with recommended operation paramaters, see the white paper Support for 15000 Partitions.
  • Reporting Services in SharePoint Integrated Mode. SQL Server 2008 SP2 provides updates for Reporting Services integration with SharePoint products. SQL Server 2008 SP2 report servers can integrate with SharePoint 2010 products. SQL Server 2008 SP2 also provides a new add-in to support the integration of SQL Server 2008 R2 report servers with SharePoint 2007 products. For more information see the “What’s New in SharePoint Integration and SQL Server 2008 Service Pack 2 (SP2)” section in What's New (Reporting Services).
  • SQL Server 2008 R2 Application and Multi-Server Management Compatibility with SQL Server 2008:
  • SQL Server 2008 Instance Management. With SP2 applied, an instance of the SQL Server 2008 Database Engine can be enrolled with a SQL Server 2008 R2 Utility Control Point as a managed instance of SQL Server. For more information, see Overview of SQL Server Utility in SQL Server 2008 R2 Books Online.
  • Data-tier Application (DAC) Support. Instances of the SQL Server 2008 Database Engine support all DAC operations delivered in SQL Server 2008 R2 after SP2 has been applied. You can deploy, upgrade, register, extract, and delete DACs. SP2 does not upgrade the SQL Server 2008 client tools to support DACs. You must use the SQL Server 2008 R2 client tools, such as SQL Server Management Studio, to perform DAC operations. A data-tier application is an entity that contains all of the database objects and instance objects used by an application. A DAC provides a single unit for authoring, deploying, and managing the data-tier objects. For more information, see Designing and Implementing Data-tier Applications.
Bugs that are fixed in this service pack:
  • FIX: Error message when you run the ProcessAdd command after you make changes to the partition on a server that is running SQL Server 2008: "Internal Error: An unexpected exception occurred"
  • FIX: Incorrect results if you use parentheses around SELECT in a statement that has a common table expression in SQL Server 2008
  • FIX: SQL Server 2008 Service Pack 2 enhancements to the “Operation has been cancelled” error message text in Analysis Services
  • Error message when you try to open a project in SQL Server 2008: "The located assembly's manifest definition does not match the assembly reference"
  • SQL Server 2008 setup fails to install on a Windows Server 2008-based cluster mount point
  • Error message when you try to use the binaries from the SQL Server System CLR Types package (SQLSysClrTypes.msi): "Unable to load DLL 'SqlServerSpatial.dll': This application has failed to start because the application configuration is incorrect"
  • Slipstream installation of SQL Server 2008 fails if the /PCUSOURCE or /CUSOURCE has a space in the path
  • A SQL Server 2005 Analysis Services drillthrough statement result is empty
  • FIX: You may experience some loss of data when you use an UPDATE statement with a SET clause that uses the time, datetime2 and datetimeoffset types in SQL Server 2008
  • Error message when you run Get-Command in a PowerShell version 2 environment on a server that is running SQL Server 2008: "Object reference not set to an instance of an object"
  • FIX: The margins are not retained in a report when the report is exported to Excel on a server that is running SQL Server 2008, and then you preview the report in Excel
  • FIX: Error message when you export a report to Excel in Report Manager on a server that is running SQL Server 2008: "Unhandled managed exception: Type = System.ArgumentOutOfRangeException"
  • FIX: Resource Monitor enters a non-yielding condition on a SQL Server 2008 server
  • The SQL Dumper utility cannot generate error dump files on a SQL Server 2008 failover cluster on an Advanced/Enterprise Failover Cluster install
  • Correcting the lack of cryptographic salt variation on SQL Server sa login hash
  • No mapping between account names and security IDs was done" error when adding a node to a SQL Server 2008 Failover Cluster
  • You cannot enroll a SQL Server 2008 database instance into a SQL Server Utility
  • You cannot deploy a Data-Tier application to a SQL Server 2008 database instance
  • FIX: Multiserver jobs are not downloaded from a SQL Server 2000 in the MSX role on to a SQL Server 2008 in the TSX role
  • FIX: Incorrect results if you use parentheses around SELECT in a statement that has a common table expression in SQL Server 2008
  • FIX: A hotfix is available that enables SQL Server 2008 R2 Reporting Services to use a 2048-bit RSA key to encrypt a Reporting Services key for FIPS compliancy
Additional issues that are fixed in this service pack:
  • DBCC corruption errors occur during SQL Server 2008 collations when strings that have Jamo sequences that follow the Japanese prolonged sign are used.
  • FIX: The syscolpars system base table displayed duplicate rows. This fix distinguishes them by adding the procedure number in DBCC checkcatalog.
  • When query has a filter that references a column in the sys.dm_server_audit_status view, the filter is ignored, and all the rows are returned from sys.dm_server_audit_status.
  • The asynchronous bucketing target shows incorrect value/string pairs for mapped fields when compared to the information that is available in dm_xe_map_values.
  • FIX: The Mismatched view can contain multiple views that have different numbers of indexes. This fix forces a deterministic order of views to compare, based on matched functions and on the number of matched indexes.
  • Users receive an "Access Denied" error message when they navigate to Report Manager locally if UAC is enabled. Adding an updated "Access Denied" message to mention UAC could allow users to address the setting accordingly.
  • In a given database, using a server cursor that is declared for a select statement that contains any system view may give incorrect results after that database is attached and reattached.
  • Radial Gauge users who try to use “RateOfChange” or “Integral” as the formula type for the MaximumValue or MinimumValue on the gauge do not see a value in the property grid dropdown list.
  • FIX: The FailoverAnalysis.sql file is installed during a SQL Server Failover Cluster setup. This script will be called automatically when failure occurs. The SqlDMVScriptTimeout private property controls for how many milliseconds the script can take to finish.
  • Users receive a validation error when they are upgrading Shared Data Sources that have a space in the name. The error indicates that the name cannot contain spaces.
  • Installation of Service Pack 1 for SQL Server Business Intelligence Development Studio 2008 fails because of a missing configuration file.
  • The ring buffer displays incomplete event data (events output from dm_xe_session_targets) when it reaches the size limit for the XML output.
  • Users cannot return multiple cookies in their HTTP module. This affect users when they try implement custom authentication.
  • The sqlsos.task_address, sqlsos.worker_address, and sqlsos.scheduler_address Extended Events actions display an incorrect address.
  • Reporting Services 2008 Designer converts centimeters to inches in the Tablix. This causes a loss of layout precision.
  • Uninstalling the first of two named AS instances disables the SQL Browser. This causes the second named instance to be unreachable.
  • Users cannot use stored credentials in their data sources if a Smart Card is required.
  • A query that has a subselect clause that uses a set expression that does not return any calculated members returns an error saying that subselects that have calculated members are not allowed.
  • In Analysis Services, setting a dimension default member by using an MDX expression that has a NonEmpty function causes the server to return an internal error when it tries to open the cube.
  • The sys.dm_os_wait_stats view displays duplicate rows for the MISCELLANEOUS wait type. This can cause problems for monitoring tools.
  • Integer value gets incorrectly rounded in the SQL Server Reporting Services Reusable Query Designer.
  • FIX: A new error code (6257) is returned when a user tries to register a CLR assembly that is built against a newer runtime, such as CLR v4. The previous error message (code 6218) was confusing and did not state the actual issue. See the bug for details.
  • An edge case inserts an identity value outside the current range in "set identity_insert TABLE_NAME on" mode. This issue also occurs in backup/restore operations.
  • If parameters that are bound by the SQLBindParameter function specify a length of SQL_DATA_AT_EXEC, the SQL Server 2008 Native Client ODC driver causes an access violation if the SQLPutData function specifies a length of SQL_NULL_DATA when the parameter value is supplied for execution.
  • SQL Server Reporting Services 2008 experiences a connection leak when a user uses the SOAP interface to run and export a report.
  • SQL Server sometimes generates a "There is insufficient system memory in resource pool 'internal' to run this query" error message. This situation is often preventable.
  • Users receive a "Page Expired" error message when they try to refersh a rendered report after the report remains idle for one hour.
  • Error 955 occurs when users tried to configure Management Data Warehouse if they have databases on their server that are not online.
  • ReportBuilder 2.0 ClickOnce displays a blank report at startup if a user edits the report by using ReportBuilder 2.0 from a SharePoint 12 website.
  • If MARS is used, the sys.dm_os_tasks view displays the same value in the request_id column for all tasks instead of reporting the correct value associated with each task.
  • FIX: A new error message indicates the cause of an access violation that occurs if the bucketizer target parameters are set incorrectly.
  • Incorrect column collation information is returned when BCP.exe retrieves column metadata information.
  • Subscriptions fail during execution because of an in-memory data structure problem during the attempted email delivery of an MHTLML-rendered report.
  • BIDS 2008 Report Designer running together with SQL Server Reporting Services 2008 crashes when users resize a table row.
  • The TO, CC, and BCC fields of the "Report Delivery Options" dialog box are cleared after users cancel or close the "Schedule Details" dialog box to return to "Report Delivery Options."
  • Collection sets work incorrectly when they collecting performance counters on a cluster if the SQL instance name is the same as the virtual network name.
  • FIX: Improved and additional information is logged for InvalidReportParameterException in Verbose output if certain conditions occur during parameter processing.
  • When users clear the selection of one or more months in a monthly schedule, SSRS creates separate schedules for each month that is still selecteded. In some cases, this can cause an "@active_end_date cannot be before @active_start_date" error.
  • Data-Driven subscription fails if a NULL value is returned when it is mapped to the report parameter, which accepts a NULL value.
  • Subscription and Delivery issues are difficult to diagnose in the Reporting Services trace file. More verbose logging is required.
  • Users receive an "Index was out of range. Must be non-negative and less than the size of the collection" error message when they export to PDF.
  • Users cannot use custom authentication in the SQL Server 2008 Web SKU.
  • If a user creates a user-defined type and a table valued function in the same transaction, and if the function has a return table containing a column of the user-defined type, a self-deadlock occurs. Additionally, the connection that tries to perform these operations is terminated.
  • FIX: Support is provided for a maximum of 15,000 partitions in tables and in indexes in the Enterprise, Developer, and Evaluation editions of Microsoft SQL Server 2008 SP2. For more information about how this support can be enabled and disabled, about its limitations, and about some known issues and workarounds, see the "Support for 15,000 Partitions" white paper (http://go.microsoft.com/fwlink/?LinkId=199773).
  • In Analysis Services, some customers may experience access violation when they use a parent-child hierarchy in the condition of an IIF function.
  • Using a PeriodsToDate function that has a Null member parameter may cause an "Unexpected exception" error.
  • An incorrect version number is displayed in SQL Server Management Studio and in SQL Server Reporting Services. This causes confusion because the displayed number does not vary from the RTM version number after an upgrade is performed.
  • A secondary exception may occur when Analysis Services generates a Watson dump. This is true whether the Watson dump is generated because of an actual exception or because of an explicit request to dump on certain errors. If the secondary exception occurs, the server can experience infinite recursion. This generates many dumps, and then shuts down the server.
  • FIX: In SSRS 2008 Service Pack 2, the RS add-in for SharePoint 2007 for communicating with SSRS 2008 R2 report server is updated. This enables access to certain functionality in ReportBuilder 3.0, ReportParts, and ATOM Renderer, including the new Report preview in ReportBuilder 3.0.
  • Processing objects in a database that contains thousands of metadata objects takes a long time to begin importing the data. This occurs because the server has to build a job schedule before the data import begins. Additionally, the algorithm that is used to determine dependencies causes slow performance when many metadata objects exist in the database.
  • A spatial index cannot be safely created in a table that uses CELL_ID, CELL_ATTRIBUTES or SRID for column names.
  • In certain conditions, the partitioned column name in error message 11405 may be wrong. This causes an incorrect column name to be printed.
  • Using cell security together with calculations yields incorrect results when a NON EMPTY clause is used.
  • Read access violation occurs during a commit process if two transactions run simultaneously: one to modify or create a partition, and one to process a dimension.
  • When Microsoft Office 12 is integrated with SQL Server 2008 Reporting Services, the SharePoint integration does not default to the Report Builder clickonce URL, preventing Report Builder from starting.
  • FIX: Localization issue in the Turkish SKU: bread crumbs are now localized on new reportpart library pages.
  • FIX: An accessibility issue that occurs because the MSAA name of "Symbol" is null. MSAA names are updated and are now discoverable.
  • FIX: Improved the performance of index creation by DDL statements for tables that have many partitions and that contain no data. Previously, the time required for this process increased in a geometric progression as the number of partitions increased. The time required now increases in a linear progression.
  • Using table valued parameters for LOB columns may cause an access violation on the server.
  • MSAA names for the Radial Scale Properties dialog box are incorrect and are not accessibility compliant.
  • During a check for a granular audit, the algorithm that is used to list any audits that include the event may experience memory leaks of the list of audits. This continues until out-of-memory errors occur and the service has to be restarted to reclaim the memory.

Microsoft SQL Server 2008 logo (481 pix)

Versienummer:SP2
Releasestatus:Final
Besturingssystemen:Windows 7, Windows 7 x64, Windows Server 2003, Windows Server 2003 x64, Windows Server 2008
Website:Microsoft
Download:http://www.microsoft.com/downloads/en/details.aspx?FamilyID=8fbfc1de-d25e-4790-88b5-7dda1f1d4e17&displaylang=en
Bestandsgroottes:284,80MB t/m 349,80MB
Licentietype:Freeware
Moderatie-faq Wijzig weergave

Reacties (2)

Je zou nu toch wel zeggen dat SQL-Server, bug-vrij zou moeten zijn, na meer dat 15 jaar door ontwikkeling (1995) - maar als ik deze was-lijst zie, is het net of het een "eerste release zie van een totaal nieuw product".
Dat doet mij toch wel een beetje vreemd overkomen... ;)
Desalniettemin vind ik het n van de beste producten van Microsoft! _/-\o_
Vergeet je nu niet dat ze eigenlijk sinds SQL2005 redelijk opnieuw zijn begonnen met een grotendeels op Managed Code (.NET vereiste) gebaseerde versie + dat de uitbreidingen op de basisfunctionaliteiten (AD integratie, SPS functies, Spatial data) vaak de oorzaak zijn voor fixes?

En het SQL Team is dan nog behoorlijk behoudend geweest - ooit een SP voor SQL7 of 2000 moeten installeren? Die jongens zijn pas met 2005 mee gaan hobbelen met de rest van de wereld. Voor die tijd was de installer een zootje batchfiles.

Op dit item kan niet meer gereageerd worden.



Apple iOS 10 Google Pixel Apple iPhone 7 Sony PlayStation VR AMD Radeon RX 480 4GB Battlefield 1 Google Android Nougat Watch Dogs 2

© 1998 - 2016 de Persgroep Online Services B.V. Tweakers vormt samen met o.a. Autotrack en Carsom.nl de Persgroep Online Services B.V. Hosting door True