Uh Oh. Operations Database is full!


<!--[if lt IE 9]>

<![endif]-->


Comments (5)

  1. Kevin Holman says:

    You cannot delete alerts.  No manual deletion is supported of ANYTHING in the databases.

    The "old fasioned way" is to groom using the built in stored procedures.  If you are running out of space – the recommendation is to add space for tempDB.  You can use tricks like setting the grooming to 60 days, and then un-resolving alerts like you have been doing…. to make what will be groomed smaller.  But at the end of the day – the only supported method is to groom.

    Another alternative – if this is not possible…. is to uninstall OpsMgr – drop the database – reinstall OpsMgr with the same server names and management group name – and import all your MP's, including your previous overrides, and then approve all the agents.  That is drastic – but I have seem some people opt for that as opposed to a cleanup

  2. Hello,

    How can we groom the OperationsManagerDW database?

  3. Joe says:

    Very informative post.  Can u provide some insights about cleaning the alerts "the old fashioned way"?  Grooming has totally died in my OpsMgr DB because of an alert flood.  I have tried running p_AlertGrooming procedure, but tempdb fills up every time.  I also tried changing some of the alerts back to unresolved to reduce the number that needed to be groomed (and then I was planning to add them back in batches), but still no luck.  

    Can I just delete the alerts in batches if i don't care about them?  What about alert history?

    Thanks!

    Joe Guglielmo

  4. Dominique says:

    Hello,

    This is excellent I already cleared the Operations Databse

    Now I am looking for the same thing for the Data warehouse database.

    Thanks,

    Dom

  5. Jasper Van Damme says:

    Came a little late to the party, but a DBA helped me with this script, it will run the stored procedure 62 times, so you don’t have to do it manually.

    declare @teller int
    declare @delay int
    SET @teller = 1
    while @teller < 63
    BEGIN
    BEGIN TRY
    WAITFOR DELAY ’00:00:05′
    PRINT ‘START EXECUTION: ‘ + cast(@teller as varchar)
    execute p_PartitioningAndGrooming
    PRINT ‘FINISHED EXECUTION: ‘ + cast(@teller as varchar)
    SET @teller = @teller + 1
    END TRY
    BEGIN CATCH
    SELECT ERROR_MESSAGE()
    return;
    END CATCH
    END

Skip to main content