system of record vs operational database

Just wanted to confirm with the experts here.

If I understand correctly system of records(SORS) is where the data element first appears and is stored.  Operational database or OLTP is where data you manage dynamic data in real time where insert, delete , update can be done in real time.
 
Now my question is , isn't System of Record and OLTP basically the same? I am bit confused with SORs which is where data first appears but then OLTP system also houses data whenever any inserts, updates, deletes are perfomed.
techEverestAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

slightwv (䄆 Netminder) Commented:
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.
0
sdstuberCommented:
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.
0
techEverestAuthor Commented:
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?
0
Powerful Yet Easy-to-Use Network Monitoring

Identify excessive bandwidth utilization or unexpected application traffic with SolarWinds Bandwidth Analyzer Pack.

sdstuberCommented:
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.
0
techEverestAuthor Commented:
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,
0
slightwv (䄆 Netminder) Commented:
In a nutshell an SOR is what your organization defines it as.  For me I tend to think of them as the first 'permanent' home for a piece of data.  When I mentioned 'origination point for the data' I sort of misspoke.  I sort of meant 'original permanent source'.

To me a POS system captures data real-time and eventually feeds it into a centralized system and once 'confirmed', it is removed from the POS system.  To me that centralized system should the to SOR since it is the first 'permanent' location.

Then the data can be further dispersed to ancillary systems for whatever purposes like marketing, sales, etc...  (your data warehouse).  These ancillary systems are working only on a 'copy' of the data and not the source.

Start with:
http://en.wikipedia.org/wiki/System_of_record
0
sdstuberCommented:
POS example:

POS collects sales info: items, quantity, price, time, method of payment, discounts applied, etc.

POS is NOT the SOR.

Each day at midnight, POS data is transferred to the "Sales History" database which maintains all of the above information for all sales, for all stores for all time (or as far back as legally required.)

"Sales History" IS the SOR.


Each month, ETL process pulls data from Sales History and loads to Data Warehouse with aggregates of items, stores, discounts etc.  Reporting tables/materialized views are populated with data.  Data cubes are constructed for analysis of sales trends,  event/price/discount impacts and inter-item purchase correlations.

Warehouse is NOT the SOR (mostly)

I add the "mostly" part because some data analysis may be too complicated to run on the SOR directly, thus necessitating the warehouse.  In these cases, the specific results of a Warehouse run may implicitly become the SOR.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
techEverestAuthor Commented:
Thanks, these examples helped me understand it well.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Databases

From novice to tech pro — start learning today.