none
看到有这么多的SQL Server 2008 R2的补丁,我应该选哪个?(下面的都是64位的) RRS feed

  • 问题

  • 现在我的SQL Server还是最原始的R2版本

    Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)   Apr  2 2010 15:48:46   Copyright (c) Microsoft Corporation  Enterprise Edition (64-bit) on Windows NT 5.2 <X64> (Build 3790: Service Pack 2)

     SQL Server 2008 R2    All (Global)    x64    nosp    2008R2_RTM_SNAC_CU5_2438347_10_50_1753_x64
     SQL Server 2008 R2    All (Global)    x64    nosp    2008R2_RTM_MDS_CU5_2438347_10_50_1753_x64
     SQL Server 2008 R2    All (Global)    x64    nosp    2008R2_RTM_PPExcel_CU4_2438347_10_50_1753_x64
     SQL Server 2008 R2    All (Global)    x64    nosp    2008R2_RTM_RSShrPnt_CU5_2438347_10_50_1753_x64
     SQL Server 2008 R2    All (Global)    x64    nosp    2008R2_RTM_SapBI_CU5_2438347_10_50_1753_x64
     SQL Server 2008 R2    All (Global)    x64    nosp    SQLServer2008R2_RTM_CU5_2438347_10_50_1753_x64

    打这些补丁有什么需要特别注意的吗?


    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.

    2011年6月1日 3:12

答案

全部回复

  • 服务器的话,最后一个
    想不想时已是想,不如不想都不想。
    2011年6月1日 3:58
    版主
  • 注意下载的补丁语言版本和已安装的SQL Server语言版本一致。

    请注意目前SQL Server 2008 R2的累积更新包已经是7的版本了。

    请参考

    http://support.microsoft.com/kb/2507770

    下面这个人几个月前问的和你相同的问题

    http://social.msdn.microsoft.com/Forums/en-GB/sqldocumentation/thread/88ece37c-6997-494f-874f-368ae929aa01

    2011年6月1日 5:31
  • 这个先在inactive节点安装补丁,转移之后,再到新的inactive的节点安装补丁吗?

    是直接安装就可以了吧?不需要其他什么特别的设置吧?


    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.

    2011年6月1日 5:54
  • 没听说需要特别设置
    2011年6月1日 6:16
  • 没听说需要特别设置

    OK.那就好~
    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.
    2011年6月1日 6:25
  • 再做一点解释,这样大家知道了命名规则和含义,就会一眼看出哪个补丁是什么,该装哪个了:

     

    ·         RTM: Released To Manufacturing, 也就是新产品的正式发布版本,比如SQL 2008 RTM.其后的补丁都是基于这个之上的.

    ·         CU: Cumulative Update, 也就是积累的更新,其中会包含多个hotfix,同一个SP的多个CU,后面的CU会包含前面的CU,因此打最新的CU即可. 多个CU之后,微软会出SP, Service Pack,即服务补丁包,其会包含之前的SP CU,例如,SQL 2008 SP2 CU5,安装顺序是SQL 2008 RTM, 然后打上补丁包2,然后打上CU5. (不必先装CU1,CU2…)  ,但这个CU是基于补丁包2的.而2008R2_RTM_SNAC_CU5是针对SNAC(SQL Native Client)的积累更新5.

    ·         CTP: Community Technology Preview, 也就是社区预览版.

     

    关于Release的详细信息,见SQL Server Release Services Team blog http://blogs.msdn.com/b/sqlreleaseservices/, 和SQL Version DB: http://www.sqlsecurity.com/FAQs/SQLServerVersionDatabase/tabid/63/Default.aspx http://www.sqlteam.com/article/sql-server-versions

     

    希望这样大家就明白了.

     

    [Dannol]

     

    2011年6月1日 8:38
  • 你的意思是:我可以直接在当前RTM版本上打CU7?


    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.
    2011年6月1日 8:46
  • 对的.


    Mark as Answer if it helps. This posting is provided "AS IS" with no warranties, confers no rights.
    2011年6月1日 8:50
  • 对的.


    Mark as Answer if it helps. This posting is provided "AS IS" with no warranties, confers no rights.

    那cluster 上装这个补丁的时候,先在inactive的节点上安装,然后再故障转移到另外一个节点,最后再在新的inactive的节点上安装即可吧。应该是这个顺序吧?
    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.
    2011年6月1日 8:53
  • Installing SQL Server 2008 rolling updates on a failover cluster

    <script type="text/javascript">// <![CDATA[ loadTOCNode(2, 'moreinformation'); ]]></script>
    1. Before you start updates, make sure that you collect a list of possible owners for the specific SQL Server clustered instance. To find a specific SQL Server network resource name, run the following command:
      cluster.exe resource
      You see output that resembles the following:
      Resource             Group               Node       Status
      --------------------       --------------------       ----------    ------
      Cluster Disk 1          Cluster Group           NODE1       Online
      Cluster Disk 2          SQL Server (INST1)        NODE1       Online
      Cluster Disk 3          SQL Server (INST2)        NODE1       Online
      Cluster Disk 4          Available Storage         NODE1       Online
      Cluster IP Address        Cluster Group           NODE1       Online
      Cluster Name           Cluster Group           NODE1       Online
      SQL IP Address 1 (SQLVS1)     SQL Server (INST1)        NODE1       Online
      SQL Network Name (SQLVS1)     SQL Server (INST1)        NODE1       Online
      SQL Server            SQL Server (INST1)        NODE1       Online
      SQL Server Agent         SQL Server (INST1)        NODE1       Online
      SQL IP Address 2 (SQLVS2)     SQL Server (INST2)        NODE1       Online
      SQL Network Name (SQLVS2)     SQL Server (INST2)        NODE1       Online
      SQL Server            SQL Server (INST2)        NODE1       Online
      SQL Server Agent         SQL Server (INST2)        NODE1       Online
      
      In this example, you can use the following commands to create a list of possible owners for each SQL Network Name resource:
      • cluster.exe resource “SQL Network Name (SQLVS1)” /listofowners > c:\SQLVS1_list_of_owners.txt
      • cluster.exe resource “SQL Network Name (SQLVS2)” /listofowners > c:\SQLVS2_list_of_owners.txt
    2. In the Cluster Administrator tool, use the corresponding SQL Network Name resource to remove half of the nodes from the possible owners list in the failover cluster instances on which you want to apply the updates. Remove the passive nodes first from the possible owners. Keep the list of nodes that you remove from the possible owners for future reference during this update process.

      Note We recommend that you remove half of the nodes from the possible owners to maintain high availability.
    3. After you have removed the nodes from the possible owners list in the failover cluster instance, apply the SQL Server update on the nodes that you removed in step 2. To apply the update on each node that has been removed from the possible owners, refer to the documentation that is supplied within the update package that you are applying.

      Note If this is the first time that you are applying the update on an instance for a node, move any active resource groups to another node before you apply the update. This helps avoid downtime or a restart operation that may occur when shared components that are being used are updated.
    4. After the update has been applied on the nodes that were removed from the possible owners, use the SQL Network Name resource on the Cluster Administrator tool to add the updated nodes back to the possible owners list in the failover cluster instance.

      To make sure that you will add back nodes for the correct SQL Server instances, use the list of possible owners that you collected before you performed the update. Make sure that you mark nodes that were already updated in your list.
    5. Based on the SQL Network Name resource, find the correct resource group, application, or services in Windows Server 2008, and then move that group, application, or service to one of the nodes that was updated.
    6. Verify that all SQL Server resources are online on the currently active node.
    7. In the Cluster Administrator tool, use the SQL Network Name resource to remove the nodes that were not updated from the possible owners in the failover cluster instance.
    8. Apply the SQL Server update to the nodes that you removed in step 7.
    9. Repeat step 4 to add all the nodes that were updated back to the possible owners for the failover cluster instance that you updated.
    10. Verify that the cluster is running without any issues. Try to move the instance of SQL Server between nodes in the cluster.

    详见http://support.microsoft.com/kb/958734


    Mark as Answer if it helps. This posting is provided "AS IS" with no warranties, confers no rights.
    2011年6月1日 9:02
  • 按照你上面的说法:

    第一步:

    首先将所有的资源转移到一个节点上,当然一般资源都是在一个节点上。

    第二步:

    在群集管理工具中,在所有服务的可能所有者中将非活动节点剔除掉。我看了下,不能直接在组上进行这个操作,只能在资源上进行处理。

    像SQLServer 群集服务中,有很多资源,比如SQLAgent,SQL Server等,难道要一个一个的进行这样的处理吗?

    另外Windows的cluster中是否也要进行这样的处理?(cluster IP address和Cluster Name等)

    第三步:

    将可能的所有者中剔除该节点之后,就在该节点上安装补丁

    第四步:

    打完补丁之后,将这个节点加入到节点可能的所有者中,然后故障转移到之前的那个节点,

    第五步:

    在新的非活动节点上进行第二步和第三步。

    最后一步:

    安装完补丁之后,将这个节点加入到可能的所有者列表中

     

    是这样吗?

    怎么感觉比以前SQL Server 2000和2005复杂多了。


    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.

    2011年6月1日 9:19
  • 对的.当然您要做好计划和准备工作,包括万一失败,如何回滚和解决. 这个在http://support.microsoft.com/kb/958734中也有所陈述.


    Mark as Answer if it helps. This posting is provided "AS IS" with no warranties, confers no rights.
    2011年6月2日 6:39