Deleting an Event definition

use cases litmus production record database is capable of monitoring tag data for production events and then record these events this does require to setup and manage these event definitions, which does include the deletion of entire event definitions, or parts of an event definition user can do this either by using applications such as microsoft sql server management studio mssql cli this can also be used for building custom solutions based on applications which allow for an odbc connection such as excel c# net python method execute stored procedure prorec event manageeventconfiguration note do learn more about the event monitoring concept and how to define it, please read the document input variables 155,141,239,219,133,114 false true false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type how to use to delete an event definition, trigger or item, call the stored procedure prorec event manageeventconfiguration using the t sql exec or execute keyword and provide the input variables below is an example using t sql in sql server management studio read out all events and their id execute \[le productionrecord] \[dbo] \[prorec event manageeventconfiguration] @action = 1, @identifier = null; delete an entire event definiton execute \[le productionrecord] \[dbo] \[prorec event manageeventconfiguration] @action = 2, @identifier = 3; delete a trigger execute \[le productionrecord] \[dbo] \[prorec event manageeventconfiguration] @action = 3, @identifier = 2; delete an item execute \[le productionrecord] \[dbo] \[prorec event manageeventconfiguration] @action = 4, @identifier = 2; result the function returns for action 1 a table as result the first three columns provide the id's which are to be used with the other actions for action = 2, use the values from column "event identifier" for action = 3, use the values from column "trigger identifier" for action = 4, use the values from column "item identifier" the function will write for the action 2, 3 and 4 t he result can be read back from the log table prorec misc log below is an example using t sql in sql server management studio select top (100) \[logid] ,\[logtype] ,\[logprocedure] ,\[logentry] ,\[logtime] from \[le productionrecord] \[dbo] \[prorec misc log] where \[logprocedure] = ' prorec event manageeventconfiguration ' order by logid desc with the result returned