GoGreen PC Tune-Up™
Learn More

Insta-Install™
this is how ssl encrypt our websites
MTNCOMP | List View | Table View | myBlog (1775 Entries)
myBlog Home

Blog


Data Sets - which are most prevalent to what industry

by Mountain Computers Inc., Publication Date: Wednesday, August 28, 2019

View Count: 1569, Keywords: Datasets, Industry, Most Prevalent, Hashtags: #Datasets #Industry #MostPrevalent



Something that I go round and round with vendors on are the similarities in required data sets. i was just reading an AWS Red Shift article on query optimization and distribution keys, and prompted me to post this.
 
For example, regardless of the industry, you have the following:
 
1. clients / customers
2. vendors
3. suppliers
4. log history
 
1. everyone has a customer, in fact we have customers everywhere. a client is a long term customer, so just get that out of the way in terms of definitions. so just call them a client, a more formal way to introduce a customer.
 
2. & 3. then you always have someone supplying you, so let's just call them suppliers and then you some one or group helping you, much like suppliers, these are more bi-directional, so let's call them vendors, upstream or downstream, left or right, more input than output or vice-versa.
 
4. the log file is for all things considered, historical. yes, you can various log files for this and that, but really,  you just need one and have items and item types within, and keep this tight and keyed, and date/time coordinated with your other data sets.
 
what else?
 
now, if we expand to money and transactions, that is pretty easy.
 
5. transaction table
 
that is something you can consider as single or double entry depending on your preferences.
 
anything else?
 
oh yeah..
 
6. temp tables, local and global...
 
a bunch of global temp tables are handy. now remember, if you are in a parallel processing system, and not really a single user, single threaded system, you need to understand how to manage temp tables and temp data sets.. that's pretty easy to... remember, lock and unlock, and force release your temp tables when applicable... have some logic going on in there.. even as an admin or dba or sa... you need to know what is going on...
 
7. reports
 
then you have your reports table that are predefined and set for specific uses with permissions, some for business, some for processing, some for activities, and other for history.
 
I can come back and fill this in.. which more good wisdom and stuff...
 
8. META DATA - now let's talk about META data for WHAT YOU DO...
 
depending on your industry, you have data sensors, collectors, inputs and outputs. this can be unique per industry, business, etc..For example all things metrics, analog or digital, or something like that...
 
a. weather, water, dirt, earth, fire, wind, air and space everywhere
b. design and repair centers of all types everywhere
c. airlines and traffic controllers everywhere
d. transportation, distribution, warehousing, and logistics everywhere
e. medical in everything everywhere
f. homes, buildings, bridges and structures of everything everywhere
f. anything else?...oh yeah.. probably...
 
just look around and you will know what I mean.
 
 
more to come...
 

if you found this article helpful, consider contributing $10, 20 an Andrew Jackson or so..to the author. more authors coming soon
FYI we use paypal or patreon, patreon has 3x the transaction fees, so we don't, not yet.

© 2024 myBlog™ v1.1 All rights reserved. We count views as reads, so let's not over think it.