Integration with SQL for incident creation

[rai5]

Hello All, 

 What would be the best approach for creating incidents based on the content of a table on an on-premise SQL server used for logging errors?

[sachin_namjoshi]

you can configure JDBC data source , transform map for integrating with SQL instance.

In transcript script, you can write script to create incident based on row content.

Regards,

Sachin

[rai5]

Thanks Sachin, 

 I initially thought about import sets and putting the records into a table; then create some type of business logic via a scheduled script. I think you are suggesting I could use a transform script correct?

[Dan T_]

I've done this extensively with multiple JDBC data sources to synchronize ServiceNow with our in-house support ticketing system.  These scheduled data sources are run through a MID server so that SN can query the database server on our internal network.  

At a high level, I query the support system for all tickets assigned to our group.  In ServiceNow, we added a field to keep the "linked" support system ticket number.  When the query runs, it loads all of the records in the import table then runs the transform map and coalesces on the support number field in SN.  If there isn't one, a new incident gets created (as well as 23 other things in the field map).

For your error logging use case, if you had a unique ID for each of the errors, you could add that to the incident table and coalesce on that to prevent duplicates.

[DirkRedeker]

Hi

I think, it is easier to reach servicenow from the on premise server, than vice versa.

You could access the table API on ServiceNow to create new incidents from the SQL data.

That way, you need go implement some active part on premise running to access the SQL database and servicenow by web api.

Let me know if that answered your question and mark my answer as correct and helpful, please. 

BR 

Dirk