Post reply

Getting Cpu Alert like warnings 99 % and 92 % in a sqlserver instance [no blocking no deadlocks and its occuring nite time when user load is less ]

  • April 23, 2015 at 5:41 am

    #148887

    Hi all

    Getting Cpu Alert like warnings 99 % and 92 % in a sqlserver instance

    1. what do we check at the particular time and these alerts are coming from nagios tool which is configured for sqlserver

    2. we see in the sqlserver logs [we found the snapmanager logs which are used for backup at the particular time when we got alerts ] other than that where can we see the logs apart from event viewer, sqlserver logs

    Thanks
    Naga.Rohitkumar

  • April 28, 2015 at 3:29 pm

    #1794128

    Any scheduled jobs running at the time?

  • May 4, 2015 at 11:33 pm

    #1795511

    Backups jobs which run from netapp its daily occurring but its should come evry time if we assume its the issue. this cpu issue is coming recently and the scheduled backupjobs runs from starting

    Thanks
    Naga.Rohitkumar

  • May 5, 2015 at 3:12 am

    #1795533

    Yeah, I wouldn't expect backup jobs to hammer the cpu, is there anything else running on the server other than the SQL instance? Any applications?

    What about any index maintenance jobs, are they running at the time?

  • May 5, 2015 at 5:29 am

    #1795548

    Is SQL the thing using the cpu?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • June 15, 2015 at 2:12 am

    #1805395

    yes its using both CPU and Ram

    Thanks
    Naga.Rohitkumar

  • June 15, 2015 at 2:16 am

    #1805397

    In that server other than SQL server app severs will run and connect to sql from their aliases to get data and also to dump some [select insert update operations runs through users ]

    There is no index maintenance jobs as it is a standard edition and the size of the database is more that 4tb so if we have

    index maintenance jobs it will eat up the space or the drive and database will be hangged.

    Thanks
    Naga.Rohitkumar

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply