Cireson Analytics DB Extension

Mikhail_Scherbakov

Hi,
Today we once again fought with our DataWarehouse. All of you know that this is a very strange thing and it is very difficult to troubleshoot it. Then I remembered that in the minimum form the necessary information is stored in the Cireson Analytics DB. To say the truth, those data are almost enough for us. But the key word here is ALMOST. Is there a way to expand the set of data that is stored in this database? As for example i wont to add ImplementationNotes property for Service Requests.

Justin_Workman

You could add the ImplementationNotes field in the SM_WorkItem_ServiceRequest and alter the Insert and Update Service Request jobs.  I would test thoroughly.  
Another route would be to have a Runbook copy the ImplementationNotes to a field that gets backed up already(i.e. Description)

Mikhail_Scherbakov

Justin_Workman said:

You could add the ImplementationNotes field in the SM_WorkItem_ServiceRequest and alter the Insert and Update Service Request jobs.  I would test thoroughly.  
Another route would be to have a Runbook copy the ImplementationNotes to a field that gets backed up already(i.e. Description)

Insert and Update jobs essentially perform the synchronization between SM_WorkItem_ServiceRequest  and ServiceManagement.dbo.WorkItem. WorkItem table does not contain ImplementationNotes property. In the service manager schema this property is named Notes. The only way to get this data is to contact the ServiceManager database directly. I can do this, but there are a few questions left:

1) This will require you to change the Insert and Update jobs. Will these changes be lost when the portal is updated?

2) What will be the result of changing the set of fields in SM_WorkItem_ServiceRequest?

Conner_Wood

Mikhail_Scherbakov said:

Today we once again fought with our DataWarehouse. All of you know that this is a very strange thing and it is very difficult to troubleshoot it.

Perhaps one of my TechNet Articles can be of assistance?

SCSM: Install Fresh Data Warehouse on Post UR Updated Environment

SCSM: Perfect the SSAS Cubes

SCSM: restoring Data Warehouse and Registering to SCSM when Cube Process Jobs have gone Bad

SCSM - Verify AlwaysOn for ServiceManager - Hell Difficulty (In case you use AlwaysOn on your DW you could learn from this)

SCSM Data Warehouse: Fact Groom Retention - Prevent Relationships Getting Marked As Deleted

SCSM Data Warehouse: Fact Groom Retention - Recover Tickets Latest Relationships Marked Deleted

 

Besides my articles, this one is deemed worthy as well:

SCSM: Datawarehouse Jobs Failing

Also if you wish to learn the way the DW knows to turn the Live Data into Archived Data, I recommend SCSM - Relationships and Classes archived into Facts and Dims as this is the missing link

Justin_Workman

I didn't realize the WorkItem table didn't have the notes!  I'd still opt for copying them to another field with a runbook to avoid altering the jobs,schema,etc.

Mikhail_Scherbakov

Justin_Workman said:

I didn't realize the WorkItem table didn't have the notes!  I'd still opt for copying them to another field with a runbook to avoid altering the jobs,schema,etc.

I was also surprised when I did not find notes field in the Workitem table. Theoretically, we can add this field to another, but what about the rest, especially custom ones?