none
SQL SERVER 2008 R2 SP2 RRS feed

  • Pregunta

  • Hola. Buenos dias. Deseo ampliar las soluciones (FIX), para sql server 2008 r2 sp2.

    852397 Updates UpgradeIncompleteFeatureConfigEventHandler.cs to include RebuildDatabase scenario when you reset ConfigurationState.
    887672 For document libraries with the "Opening Documents in the Browser" setting set to "Open in the client application," GetSnapshot.exe ignores the configuration and always displays the workbook by using Excel Services as if the setting was "Open in the browser."
    820805 FIX: On a Russian localized build of the Reporting Services Configuration Manager, Execution Account information contains clipped strings.
    718430 The ExpectedCount and ExpectedElapsedMs usage counts are updated to reflect the actual counts.
    737914 Fixes an issue in which SQL Server 2008 R2 Analysis Services crashes during database synchronization.
    788389 Trace flag 1264 is removed so that the process name is collected by default in non-yielding scenario dumps. The number of thread records in non-yielding scenario dump files is increased from 1K to 16K.
    820762 SQL Server 2008 R2 changes the FireAgain parameter to True if an event should be logged. However, after some codes are removed by mistake, some logs are missing because the FireAgain parameter is determined only by the external event listener. After you apply this hotfix, the issue is resolved.
    820764 Consider the following scenario. You have indexed view projects columns from base and non-base tables in SQL Server 2008 R2. A column from the non-base table has the same order ID and type as a column of the base table. In this scenario, SQL Server 2008 R2 switches the partitions. After you apply the hotfix, SQL Server 2008 R2 experiences an error instead of switching the partitions.
    820792 Fixes an issue in which an object that is allocated on a SOS_Task PMO could be also used by another TASK that has a different life span. This service pack uses the correct PMO for allocating the object.
    820796 After you apply the hotfix, the optimizer understands that CRYPT_GEN_RANDOM can return different outputs for the same input.
    820859 Fixes an issue in which an incorrect value is returned when you run SCOPE_IDENTITY().
    820864 Fixes an issue in which the SQL Server 2008 R2 setup crashes when you install SxS with Shiloh OLAP SP3a. This issue occurs because Shiloh OLAP SP3a incorrectly writes the version registry key as "Service Pack 3.0."
    820873 Fixes an issue in which an incorrect CPU time is reported by sys.dm_exec_query_stats when parallel query plans are involved.
    820880 Fixes an issue that occurs when internal asynchronous file-reading buffers are splitting the multi-character column delimiter in two parts. The fix is to correctly reset the current parsing pointer after buffers are switched.
    847805 Uses the synchronization only if the SQLWixCompilerExtension operation runs in candle.
    890643 Changes the HierarchyGet operation to avoid a certain code path for the explicit cap that applies only to the derived part of the hierarchy. The update is a one-line update that is low risk.
    731796 Fixes an issue in which you receive errors in a statement when you purge from snapshots.notable_query_text.
    820829 Bad GUID values that are parsed from flat files could cause errors. The fix is to fall back into a truncation mode if the source buffer is larger than the maximum size of a GUID string.
    677173 Recalculates latch promotion threshold periodically to avoid variation because of a calculation error at startup.
    725819 The suggested fix is matching calling conventions between caller and the person who is called.
    769975 Fixes a crash during startup when the computer has an empty processor slots or the restart option /setgroupsize is used.
    788233 Reduces the time during which the latch backs off when it experiences spinlock. This helps improve performance
    840461 Fixes a race condition during XE session startup that could cause SQL Server crashes.
    martes, 5 de agosto de 2014 17:12

Respuestas

  • Saludos,

    No entiendo realmente que es lo que deseas hacer, pero primero que nada necesitamos saber en que versión estas "Select @@version" veras un numero parecido a 10.50.xxxx 

    Checa en sqlserverbuilds.blogspot.com y podras ver hasta que version esta publicada de sql server.  

    martes, 12 de agosto de 2014 20:36