Showing posts with label Service Pack. Show all posts
Showing posts with label Service Pack. Show all posts

Tuesday, September 25, 2012

How to find on which node SQL Server instance was running before restart?

 

In situation, where SQL Server instance running on a node is restarted usually after Windows Operating System patching or for some other reason, there may be need to find to which node the SQL Server instance was running on before.

Here is the solution for this;

By default whenever SQL Server instance restarted on Clustered Environment, on SQL Server Error Log it will post the message below;

The NETBIOS name of the local node that is running the server is 'ClusterNode1'.

So, making use of the xp_ReadErrorLog we can query the ErrorLog and find the details.

-- To know the list available Error log files
exec xp_enumerrorlogs 1


-- Search the available error log files
exec xp_ReadErrorLog 0, 1 , 'NETBIOS name of the local node'
exec xp_ReadErrorLog 1, 1 , 'NETBIOS name of the local node'
exec xp_ReadErrorLog 2, 1 , 'NETBIOS name of the local node'
exec xp_ReadErrorLog 3, 1 , 'NETBIOS name of the local node'
exec xp_ReadErrorLog 4, 1 , 'NETBIOS name of the local node'
exec xp_ReadErrorLog 5, 1 , 'NETBIOS name of the local node'

Tuesday, July 12, 2011

Silent Mode Installation of SQL Server 2008 SP2


Here is the command for SQL Server 2008 Express Edition Silent mode installation of SP2.

SQLEXPR_x86_ENU.exe /Q /ACTION=PATCH /INSTANCENAME=SQLEXPRESS

Saturday, December 18, 2010

Download Microsoft SQL Server 2005 Service Pack 4 RTM

 

Service Pack 4 (SP4) for Microsoft SQL Server 2005 is now available for download.

SQL Server 2005 SP4 includes SQL Server 2005 SP3 cumulative update 1 to 11, customer requested fixes, along with instances of the SQL Server 2005 SP4 database Engine support for DAC operations.

It can be downloaded from

Microsoft SQL Server 2005 Service Pack 4 RTM

Thursday, October 14, 2010

Impact of renaming “sa” account on SQL Server 2008

 

Error: 912, Severity: 21, State: 2

Microsoft has confirmed that this is a problem in the Microsoft products that are listed 

  • Microsoft SQL Server 2008 Workgroup
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Standard
  • This problem was first corrected in SQL Server 2008 Service Pack 1

    Cause:

    The upgrade process includes a script to create the SP_Syspolicy_Create_Purge_job stored procedure. The procedure creates the syspolicy_purge_history job and hardcodes the owner of the job to be the sa account. Because the sa account is renamed, the job creation fails.

    Workaround:  recreate the sa account

    Reference:  FIX: Error message when you try to upgrade an instance of SQL Server 2005 to SQL Server 2008: "Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes"

    SQL Server 2008 Service Pack 2 - Installation

     

    Here Let me show the step by step on SQL Server 2008 SP 2 Installation

    image

    image

    image

    image

    image

    image

     

    image

    image

    image

    Wednesday, September 29, 2010

    SQL Server 2008 Service Pack 2 released

     

    SQL Server 2008 SP 2 released on 29 Sep 2010.

    To download the SQL Server 2008 SP2 release please select from the links below:

    Tuesday, May 04, 2010

    How to apply Service pack on SQL Server 2005 Cluster

     

    1. Backup of all the System + User Database

    2.Windows Login account with "Local Administrator" privileges on all the nodes involved

    3. Ensure all the recourses part of the SQL Server Cluster resource group are online.
       I recommend to reboot both nodes before installation. (to avoid pending reboot, hanging installers, terminal sessions etc. problems.)

    4. Cross check if the cluster failover on the nodes involved successfully.

    5. shut down all applications that use SQLServer (because you know the instance(s) will get offline at some point(s) during the upgrade)

    6. Disable if any DDL Triggers

    7. Verify if following services online on the nodes involved.

    • Task Scheduler
    • Com+ System Application Service
    • Cryptographic Services
    • Remote Registry Service 

    8. Pause Database Mirroring

    Log on the active node, apply the Service pack. ( It is opposite in case of SQL Server 2008 ! ). You cannot install SP3 from any passive nodes in the failover cluster.

    Please note SP will not update the client tools on the passive node. you need to do that manually; though it is cluster aware.

    Reference: 

    How to install SQL Server 2005 SP3

    SQL Server 2005 SP3 Release Notes

    SQL Server 2008 failover cluster rolling patch and service pack process

    Saturday, May 01, 2010

    SQL Server 2005 Service Pack 4

    SQL Server 2005 Service Pack 4 ( SQL Server 2005 SP4 ) will be released by end of the year 2010 ( Quarter 4 of 2010 ). It will be the last Service pack for the SQL Server 2005.


    SQL Server 2008 Service Pack 1 ( SQL Server 2008 SP1 ) will be released by third quarter of the year 2010 ( Quarter 3 of 2010 ). It will be the last Service pack for the SQL Server 2005.


    Source: Shared by the Microsoft SQL Server release services group manager.

    Thursday, April 22, 2010

    SQL Server Latest Service Pack and Security Hot fixes

              

    Applies to

    Version Range

    Type

    Description

    Target Version

    Release Date

    Security Bulletins

    KB

    Download

     

    SQL Server 2000

    Below 8.00.2039

    Service Pack

    SQL Server 2000 SP4

    8.00.2039

    6-Jun-05

    MS03-031

    KB884525

    http://www.microsoft.com/downloads/details.aspx?familyid=8E2DFC8D-C20E-4446-99A9-B7F0213F8BC5&displaylang=en

     

    SQL Server 2000

    8.00.2039-8.00.2054

    GDR

    SQL Server 2000 SP4 GDR

    8.00.2055

    10-Feb-09

    MS09-004

    KB960082

    http://www.microsoft.com/downloads/details.aspx?familyid=d5bb816a-6e1a-47cb-92be-51c565ee184c&displaylang=en

     

    SQL Server 2000

    8.00.2148-8.00.2281

    QFE

    SQL Server 2000 SP4 QFE

    8.00.2282

    10-Feb-09

    MS09-004

    KB960083

    http://www.microsoft.com/downloads/details.aspx?familyid=A93F3CFE-18C9-4218-A551-13BF415E418A&displaylang=en

     

    SQL Server 2005

    Below 9.00.4035

    Service Pack

    SQL Server 2005 SP3

    9.00.4035

    15-Dec-08

    N/A

    KB955706

    http://www.microsoft.com/downloads/details.aspx?FamilyID=ae7387c3-348c-4faa-8ae5-949fdfbe59c4&displaylang=en

     

    SQL Server 2005

    9.00.4035-9.00.4052

    GDR

    SQL Server 2005 SP3 GDR

    9.00.4053

    12-Oct-09

    MS09-062

    KB970892

    http://www.microsoft.com/downloads/details.aspx?familyid=0d878f4b-71e8-4170-9a14-1bce684811ce&displaylang=en

     

    SQL Server 2005

    9.00.4205-9.00.4261

    QFE

    SQL Server 2005 SP3 QFE

    9.00.4262

    12-Oct-09

    MS09-062

    KB970894

    http://www.microsoft.com/downloads/details.aspx?familyid=e6f307c1-8b21-406e-9c6f-b1a3a1e9a98f&displaylang=en

     

    SQL Server 2008

    Below 10.00.2531

    Service Pack

    SQL Server 2008 SP1

    10.00.2531.00

    27-Aug-09

    N/A

      

    http://www.microsoft.com/downloads/details.aspx?FamilyID=66ab3dbb-bf3e-4f46-9559-ccc6a4f9dc19&displaylang=en

     
              
     

    It lists only the latest SQL Server Service Pack and Security Hot fixes as on 22nd April 2010

         

    Saturday, July 19, 2008

    SQL Server 2005 SP2 installation failed on Active/Passive Cluster

    SP2 fails to install database services - MSP Error: 29512 “Unable to install Windows Installer MSP file”
    Errors from Summary.log
    ----------------------------------------------------------------------------------
    Product : Database Services (SQL084)
    Product Version (Previous): 2153
    Product Version (Final) :
    Status : Failure
    Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
    Error Number : 29512
    Error Description : MSP Error: 29512 SQL Server Setup was unable add user pbs\csparq_service to local group AU\SGG-GM_ServiceAccounts.
    ----------------------------------------------------------------------------------

    Configuration failed.

    One or more products failed to install, see above for details
    Exit Code Returned: 29512

    Errors from SQL9_Hotfix_KB921896_sqlrun_sql.msp.log

    MSI (s) (68:4C) [00:21:37:156]: Product: Microsoft SQL Server 2005 (64-bit) - Update 'Service Pack 2 for SQL Server Database Services 2005 (64-bit) ENU (KB921896)' could not be installed. Error code 1603.

    Additional information is available in the log file C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log.

    Local group AU\SGG-GMRISK_ServiceAccounts doesn't exist
    Failure adding user pbs\acoe_csparq_service to local group AU\GMRISK_ServiceAccounts (5)
    Error Code: 0x80070005 (5)
    Windows Error Text: Access is denied.
    Source File Name: sqlca\sqlsecurityca.cpp
    Compiler Timestamp: Sat Oct 7 09:43:41 2006
    Function Name: Do_sqlGroupMember
    Source Line Number: 1132

    MSI (s) (68:4C) [00:21:37:156]: Note: 1: 1729
    MSI (s) (68:4C) [00:21:37:156]: Transforming table Error.

    MSI (s) (68:4C) [00:21:37:156]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (68:4C) [00:21:37:188]: Transforming table Error.

    MSI (s) (68:4C) [00:21:37:188]: Transforming table Error.



    Workaround: