Dear colleagues,

We are now testing Opmanager latest version for monitoring of our servers.

First of all we make installation using SQL 2008 R2 Standard.

Everything start normall, some small bugs was acceptible, but now we faced with such bug:

1) we added Hyper-V host server (that has 2 DNS records with the same IP).

2) we found a problem in DNS, fix it, and remove server from Opmanager.

3) by some reasons it was still in database, but cant be opened/deleted/readded.

When we try to re-add it - we saw problem like it is already in DB.

We found such solution

http://support.opmanager.com/sd/AddSolution.sd?solID=1808

But it was working only for MySQL (such DB solution is not a best option for us, because we have SQL admins, not mysql).

That is why we make a backup of DB, and try to remove it manually. Now it dissapear from Opmanagersystem, but cant be re-added :)

Script that was completed in DB is adopted for SQL from solution above:

    "delete from Alert where Source like '%" + devicename + "%'",
    "delete from CHILDRENSTATUS where KEYSTRING like '%" + devicename + "%'",
    "delete from DBINTERFACES where VALUESTRING like '%" + devicename + "%'",
    "delete from DBMAP where KEYSTRING like '%" + devicename + "%'",
    "delete from GroupTable where MEMBERNAME like '%" + devicename + "%'",
    "delete from InetService where NAME like '%" + devicename + "%'",
    "delete from IpAddress where NAME like '%" + devicename + "%'",
    "delete from ManagedObject where NAME like '%" + devicename + "%'",
    "delete from MapContainer where OBJNAME like '%" + devicename + "%'",
    "delete from MapSymbol where OBJNAME like '%" + devicename + "%'",
    "delete from Node where NAME like '%" + devicename + "%'",
    "delete from OpManagerObject where NAME like '%" + devicename + "%'",
    "delete from PolledData where AGENT like '%" + devicename + "%'",
    "delete from SnmpInterface where NAME like '%" + devicename + "%'",
    "delete from SnmpNode where NAME like '%" + devicename + "%'",
    "delete from SwitchObject where NAME like '%" + devicename + "%'",
    "delete from TOPODBSPECIALKEY where KEYSTRING like '%" + devicename + "%'",
    "delete from TopoObject where NAME like '%" + devicename + "%'",
    "delete from CHILDRENSTATUS where KEYSTRING like '%" + devicename + "%'",
    "delete from CLIDetails where AGENTNAME like '%" + devicename + "%'",
    "delete from CustomFieldsForDevices where DEVICENAME like '%" + devicename + "%'",
    "delete from CustomFieldsForInterfaces where DEVICENAME like '%" + devicename + "%'",
    "delete from DCObject where NAME like '%" + devicename + "%'",
    "delete from DeviceToEventLogRuleMap where DEVICENAME like '%" + devicename + "%'",
    "delete from EventLogDeviceInfo where DEVICENAME like '%" + devicename + "%'",
    "delete from EventLogRunnable where DEVICENAME like '%" + devicename + "%'",
    "delete from HRDetails where AGENTNAME like '%" + devicename + "%'",
    "delete from InterfacesToNotify where NAME like '%" + devicename + "%'",
    "delete from MaintenanceDevices where MD_NAME like '%" + devicename + "%'",
    "delete from MapLink where SOURCE like '%" + devicename + "%'",
    "delete from MapLink where DEST like '%" + devicename + "%'",
    "delete from NamedInstanceObject where PARENTDEVICENAME like '%" + devicename + "%'",
    "delete from NTServices where DEVICENAME like '%" + devicename + "%'",
    "delete from OBJECTSTOLINK where KEYSTRING like '%" + devicename + "%'",
    "delete from OpmObjectDomainController where DEVICENAME like '%" + devicename + "%'",
    "delete from POLLUSERPROPS where AGENT like '%" + devicename + "%'",
    "delete from Printer where NAME like '%" + devicename + "%'",
    "delete from ProfileCriteria where CRITERIANAME like '%" + devicename + "%'",
    "delete from Services where PARENTDEVICENAME like '%" + devicename + "%'",
    "delete from TOPOUSERPROPS where NAME like '%" + devicename + "%'",
    "delete from UPSObject where NAME like '%" + devicename + "%'" 

After this we start RepairDB, and then Opmanager started correctly. But as i tell before, we cant add such system into monitoring.

We are ready to recover test DB and start any solution if you have it, or please explain how we will fix such problems in future, if our customer will decide to order your solution.

Or Microsoft SQL is not recommended at all, because i cant see too much solutions for SQL at all.

Second that we found, when we try to remove "treshold" values for services from "servers" - we recieve white screen and error message. After several similar tries we complete such task. But i cant understand why it is appearing.

Second is not so critical as first part of our testing.