Purging production record data for a specific Production Record ID

use cases it might be necessary for users to remove an individual production record if it for example used the wrong triggers or other circumstance make the data unusable or invalid user can purge production record data for a specific production record 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 to obtain a production record id to purge, several options do exist such as explained in this document reading production record event data with utc timestamp docid\ zmrhs1q1rgiydzat6wf2z method execute stored procedure prorec misc processdata purge records by recordid input variables variable name datatype description example @startrecordid bigint this is either the single production record id to be purged or the first of a range of production record id's mandatory! can not be null or empty 124 @endrecordid bigint this is the optional last production record id if a range of production records has to be purge null @node varchar(50) the optional name of the root node and the name of the data model this is optional and mostly used for purging a range of production record id's for a specific data model for a single production record id, this value is not needed null how to use to purge a single production record id or a range of production record id's, call the stored procedure prorec misc processdata purge records by recordid 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 execute \[le productionrecord] \[dbo] \[prorec misc processdata purge records by recordid] @startrecordid = 124, @endrecordid = 130, @node = n' tooling shop status' ; note the system will always create a backup first before purging this way, the production record data can always be restored if an output window does exist, the progress can be observed result the stored procedure will verify that the provided values are correct and data exist then it will create the backup before purging the production record data the 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 misc processdata purge records by recordid ' order by logid desc; with the result returned