system of record vs operational database

In my environment the System of Record is the origination point for the data.  It may or may not be an OLTP system.

Maybe the data into my organization is a huge batch feed from another system.  Really not OLTP but still new data.

It is almost always 'Operational' in that some app submitted some data to some database for the first time.

Where OLTP and SORS aren't the same:  Can your SORS not send data to another system  where it is further processed but has no additional data added to the original record?  It can add additional data as it is processed as meta data but not modify the original.

SOR is simply whatever database is the final authority for data.  Where it originated isn't usually a factor.

That might be an OLTP system, it might be a data warehouse, it might be a set of flat files.

Thanks for your quick response.I was away so could not get back to this site soon enough. I am not still clear . The SORs are referenced by another system through ETL process and called authoritative source which is the data source that analytical tools such as Cognos, Business objects reporting tools use it to develop reports. For example a point of sale(POS) application at supermarkets, arent they the original source of data thus a SOR as well as the new data inserts every few seconds or minutes are OLTP?

original source and system of record are not the same thing.

so in your example - NO, the POS application is NOT a system of record.


the SOR is the FINAL system, not the first system.

I cant still understand clearly the SOR. I do understand OLTP system where CRUD operations can be performed. Can you please provide and example for example with scenario such as POS at a store and the backend system where data is stored , the datawarehouse that is populated from OLTP system. At what point and where can we call a system SOR?

Thanks,

Thanks, these examples helped me understand it well.