14 abril 2009

Bugs relacionados a Business Intelligence reparados con el SP1 de SQL 2008

A continuación una compilación de los “bugs” reparados con el Service Pack 1 de SQL 2008 que se documentan en http://support.microsoft.com/default.aspx/kb/968369. El listado va en inglés. Si a alguno de ustedes le ha ocurrido alguno de estos errores, ya pueden sonreir Open-mouthed:

  1. You cannot add a cluster node when you install SQL Server 2008 Analysis Services and you do not install the SQL Server 2008 Database Engine
  2. FIX: In a SQL Server 2008 Reporting Services report that contains several levels, some items disappear when you collapse another item
  3. FIX: The aggregate value is incorrect when you design a query that contains some entity groups by using the Report Model Query Designer in SQL Server 2008 or in SQL Server 2005
  4. A new trace event is added in SQL Server 2008 SP1 to better diagnose unexpected cancellation issues in SQL Server 2008 Analysis Services.
  5. Some trace events that are related to personalization extension are added to the SQL Server Profiler trace definitions in Analysis Services.
  6. When a client that is based on MSOLAP, Analysis Management Objects (AMO), or ADOMD.NET connects to Analysis Services over an HTTP connection, the client does not send back certain HTTP headers.
  7. In SQL Server 2008 SP1, more information is added to the minidump files that are generated for troubleshooting in Analysis Services.
  8. You cannot browse time series models that have nested tables by using the SQL Server Data Mining Add-ins for Office 2007.
  9. You receive an error message when you process an association rules mining model in SQL Server 2008 Standard Analysis Services: "Errors in the metadata manager. An error occurred when loading the <Mining Model Name> mining model."
  10. The decision tree algorithm returns a regression formula that contains valid floating-point regression coefficients in Analysis Services.
  11. You receive an incorrect result when you use the NON EMPTY statement and the CROSSJOIN function in a Multidimensional Expressions (MDX) statement that queries from a Sum-based measure and a LastNonEmpty-based measure in Analysis Services.
  12. A subselect clause that uses calculated members does not consider the granularity to determine whether a calculated member should be included in Analysis Services.
  13. In SQL Server 2008 SP1, improvements are made to help you troubleshoot unexpected cancellation issues in Analysis Services.
  14. When a polling query is querying a DateTime value, the proactive caching process crashes in Analysis Services.
  15. An access violation occurs when you process a dimension that has a calculated member that references another member that is defined later in the cube script in Analysis Services.
  16. The filter lookup list is not populated in Model Designer when you use a Teradata data source in SQL Server 2008 Reporting Services.
  17. Charts, gauges, and images may appear blurry when you view them in Business Intelligence Development Studio or in Report Builder 2.0 Preview mode.
  18. When you export a report in the comma separated values (CSV) format, Reporting Services may omit a row for a Tablix data region that has dynamic groups.
  19. Table group headings do not repeat when you render a report as a PDF, as a Print Preview, or as an image if a row does not completely fit on one page.
  20. A text box that splits across pages does not correctly display all the content in Reporting Services.
  21. The memory throttling behavior for different editions of Reporting Services is not enforced correctly.
  22. A SQL Server 2005 Reporting Services report that contains the SyncLock statement in the report code cannot be rendered in a fresh installation of SQL Server 2008.
  23. When you view a SQL Server 2008 Reporting Services report in a SQL Server 2005 viewer control, the viewer control shows an incorrect page count.
  24. In the SharePoint integrated mode, a report runs slower than the same report runs in the native mode in Reporting Services.
  25. Change data capture incorrectly reports an UPDATE statement as a DELETE statement that is followed by an INSERT statement in SQL Server 2008.

Como ven, la lista es para BI es bastante interesante.


No hay comentarios: