empty analytics views

Silas_Sulser

some of our analytics views are completely empty like:



Did we miss something?

thanks and best regards
Silas

Brian_Wiest

Check your SQL jobs for Analytics. There have been a few releases that SQL jobs are failing to copy content into the Analytics tables. 

john_doyle

Hi @Silas_Sulser  

It sounds like the ServiceManager and ServiceManagement databases are on different server instances. This is not a scenario that Cireson Analytics can accommodate. If this is the case, then you will have to add the SQL instance which is hosting the ServiceManager db as a linked server on the SQL Server hosting the ServiceManagement and CiresonAnalytics databases. You will then have to modify the jobs so that they refer to the linked server. You can either query the linked server directly or rewrite the SQL using the OPENROWSET commands to access the data in ServiceManager. The latter is a little more complicated.

Brian_Wiest

Check your SQL jobs for Analytics. There have been a few releases that SQL jobs are failing to copy content into the Analytics tables. 

Silas_Sulser

@Brian_Wiest thanks for your hint!
I've just checked these jobs. Youre talking about these, right (this is on our data warehouse server)?



Unfortunately I cannot see any analytics-related jobs. Are there any missing?
I also recognized some job errors like:



There were error messages like "Invalid object name 'ServiceManager.dbo.Relationship'...." what makes no sense, because this table exists on that specific server.
Can this may be related to my problem?



Many thanks
Silas

john_doyle

Hi @Silas_Sulser  

It sounds like the ServiceManager and ServiceManagement databases are on different server instances. This is not a scenario that Cireson Analytics can accommodate. If this is the case, then you will have to add the SQL instance which is hosting the ServiceManager db as a linked server on the SQL Server hosting the ServiceManagement and CiresonAnalytics databases. You will then have to modify the jobs so that they refer to the linked server. You can either query the linked server directly or rewrite the SQL using the OPENROWSET commands to access the data in ServiceManager. The latter is a little more complicated.

Silas_Sulser

Hi @john_doyle
Im thinking about setting up a SCSM 2016 environment.
Would you recommend to have both DBs on the primary server (no Data Warehouse)?

Thanks and best regards
Silas