{"id":29030,"date":"2020-05-28T09:22:45","date_gmt":"2020-05-28T07:22:45","guid":{"rendered":"https:\/\/blog.scalefree.com\/?p=13363"},"modified":"2026-04-16T11:54:27","modified_gmt":"2026-04-16T09:54:27","slug":"benennungskonventionen-2","status":"publish","type":"post","link":"https:\/\/www.scalefree.com\/de\/blog\/architecture\/naming-conventions-2\/","title":{"rendered":"Was bei der Namensgebung in Data Warehousing zu beachten ist - Teil 2"},"content":{"rendered":"\n\t\t<div id=\"fws_69fa25d69bef6\"  data-column-margin=\"default\" data-midnight=\"dark\"  class=\"wpb_row vc_row-fluid vc_row\"  style=\"padding-top: 0px; padding-bottom: 0px; \"><div class=\"row-bg-wrap\" data-bg-animation=\"none\" data-bg-animation-delay=\"\" data-bg-overlay=\"false\"><div class=\"inner-wrap row-bg-layer\" ><div class=\"row-bg viewport-desktop\"  style=\"\"><\/div><\/div><\/div><div class=\"row_col_wrap_12 col span_12 dark left\">\n\t<div  class=\"vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone \"  data-padding-pos=\"all\" data-has-bg-color=\"false\" data-bg-color=\"\" data-bg-opacity=\"1\" data-animation=\"\" data-delay=\"0\" >\n\t\t<div class=\"vc_column-inner\" >\n\t\t\t<div class=\"wpb_wrapper\">\n\t\t\t\t\n<div class=\"wpb_text_column wpb_content_element \" >\n\t<div class=\"wpb_wrapper\">\n\t\t<h2><span style=\"font-weight: 400;\">Naming Conventions in Data Warehousing<\/span><\/h2>\n<p><!--more--><\/p>\n\t<\/div>\n<\/div>\n\n\n\n<div class=\"divider-wrap\" data-alignment=\"default\"><div style=\"height: 25px;\" class=\"divider\"><\/div><\/div>\n<div class=\"wpb_text_column wpb_content_element \" >\n\t<div class=\"wpb_wrapper\">\n\t\t<p><span style=\"font-weight: 400;\">Throughout this article, we will continue presenting our suggestions for naming conventions in a data warehouse solution, as well as sharing examples for naming standards, which both our team and our customers utilize internally. You can also find our <a href=\"https:\/\/blog.scalefree.com\/2019\/05\/07\/naming-conventions\/\">previous blog post<\/a>, where discussed the different aspects of a naming <\/span><span style=\"font-weight: 400;\">standard documentation &#8211; from letter case types to the consideration between using prefixes or suffixes in database object names.\u00a0<\/span><\/p>\n<div class=\"content-list-wrapper\"><p class=\"content-heading\">In this article:<\/p><ul class=\"content-list\"><li><a href=\"#layer-schema\">Layer Schema<\/a><li><a href=\"#edw-data-vault-entities\">EDW\/Data vault entities<\/a><li><a href=\"#more-about-naming-conventions-for-satellite-entities\">More about naming conventions for satellite entities<\/a><li><a href=\"#conclusion\">Conclusion<\/a><\/ul><\/div>\n<p><!--more--><\/p>\n\t<\/div>\n<\/div>\n\n\n\n<div class=\"divider-wrap\" data-alignment=\"default\"><div style=\"height: 25px;\" class=\"divider\"><\/div><\/div>\n<div class=\"wpb_text_column wpb_content_element \" >\n\t<div class=\"wpb_wrapper\">\n\t\t<h2><span style=\"font-weight: 400;\">Layer Schema<\/span><\/h2>\n<p><!--more--><\/p>\n\t<\/div>\n<\/div>\n\n\n\n<div class=\"divider-wrap\" data-alignment=\"default\"><div style=\"height: 25px;\" class=\"divider\"><\/div><\/div>\n<div class=\"wpb_text_column wpb_content_element \" >\n\t<div class=\"wpb_wrapper\">\n\t\t<p><span style=\"font-weight: 400;\">For layer schema names, we prefer using prefixes. <\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">As discussed in the previous blog post, this convention boosts visibility in data exploration within the <a href=\"https:\/\/www.scalefree.com\/scalefree-newsletter\/write-backs-in-the-enterprise-data-warehouse-architecture\/\">Enterprise Data Warehouse<\/a> for developers and business users by grouping schemas of the same data warehouse layer together. <\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">The following is a list of common Enterprise Data Warehouse layers and our associated recommendations regarding naming conventions:<\/span><!--more--><\/p>\n\t<\/div>\n<\/div>\n\n\n\n<div class=\"divider-wrap\" data-alignment=\"default\"><div style=\"height: 25px;\" class=\"divider\"><\/div><\/div><div class=\"img-with-aniamtion-wrap \" data-max-width=\"100%\" data-max-width-mobile=\"default\" data-shadow=\"none\" data-animation=\"none\" >\n      <div class=\"inner\">\n        <div class=\"hover-wrap\"> \n          <div class=\"hover-wrap-inner\">\n            <img loading=\"lazy\" decoding=\"async\" class=\"img-with-animation skip-lazy nectar-lazy\" data-delay=\"0\" height=\"679\" width=\"606\" data-animation=\"none\" data-nectar-img-src=\"https:\/\/www.scalefree.com\/wp-content\/uploads\/2020\/05\/Naming-conventions-Layer-Schemas.png\" src=\"data:image\/svg+xml;charset=utf-8,%3Csvg%20xmlns%3D'http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg'%20viewBox%3D'0%200%20606%20679'%2F%3E\" alt=\"Recommended Naming Conventions for EDW layers\" data-nectar-img-srcset=\"https:\/\/www.scalefree.com\/wp-content\/uploads\/2020\/05\/Naming-conventions-Layer-Schemas.png 606w, https:\/\/www.scalefree.com\/wp-content\/uploads\/2020\/05\/Naming-conventions-Layer-Schemas-268x300.png 268w, https:\/\/www.scalefree.com\/wp-content\/uploads\/2020\/05\/Naming-conventions-Layer-Schemas-320x359.png 320w, https:\/\/www.scalefree.com\/wp-content\/uploads\/2020\/05\/Naming-conventions-Layer-Schemas-360x403.png 360w, https:\/\/www.scalefree.com\/wp-content\/uploads\/2020\/05\/Naming-conventions-Layer-Schemas-600x672.png 600w\" sizes=\"auto, (max-width: 606px) 100vw, 606px\" \/>\n          <\/div>\n        <\/div>\n      <\/div>\n    <\/div>\n<div class=\"wpb_text_column wpb_content_element \" >\n\t<div class=\"wpb_wrapper\">\n\t\t<p style=\"text-align: center;\"><em>Figure 1: Recommended Naming Conventions for Common Enterprise Data Warehouse Layers<\/em><\/p>\n\t<\/div>\n<\/div>\n\n\n\n<div class=\"divider-wrap\" data-alignment=\"default\"><div style=\"height: 25px;\" class=\"divider\"><\/div><\/div>\n<div class=\"wpb_text_column wpb_content_element \" >\n\t<div class=\"wpb_wrapper\">\n\t\t<h2><span style=\"font-weight: 400;\">EDW\/Data vault entities<\/span><\/h2>\n\t<\/div>\n<\/div>\n\n\n\n<div class=\"divider-wrap\" data-alignment=\"default\"><div style=\"height: 25px;\" class=\"divider\"><\/div><\/div>\n<div class=\"wpb_text_column wpb_content_element \" >\n\t<div class=\"wpb_wrapper\">\n\t\t<p><span style=\"font-weight: 400;\">As discussed in the previous section, we do not separate the Raw Data Vault and the <a href=\"https:\/\/www.scalefree.com\/consulting\/data-vault-2-0\/#business-vault\">Business Vault<\/a> into different database schemas. Instead, users will be able to distinguish between a Raw Vault entity and a computed one via the entity name. <\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">The following is a list of naming conventions for standard <a href=\"https:\/\/www.scalefree.com\/consulting\/data-vault-2-0\/\">Data Vault 2.0<\/a> entities in addition to more advanced entity types.<\/span><\/p>\n\t<\/div>\n<\/div>\n\n\n\n<div class=\"divider-wrap\" data-alignment=\"default\"><div style=\"height: 25px;\" class=\"divider\"><\/div><\/div><div class=\"img-with-aniamtion-wrap \" data-max-width=\"100%\" data-max-width-mobile=\"default\" data-shadow=\"none\" data-animation=\"none\" >\n      <div class=\"inner\">\n        <div class=\"hover-wrap\"> \n          <div class=\"hover-wrap-inner\">\n            <img loading=\"lazy\" decoding=\"async\" class=\"img-with-animation skip-lazy nectar-lazy\" data-delay=\"0\" height=\"654\" width=\"585\" data-animation=\"none\" data-nectar-img-src=\"https:\/\/www.scalefree.com\/wp-content\/uploads\/2020\/05\/Figure-2-Naming-Conventions-for-Standard-Data-Vault-Entities.png\" src=\"data:image\/svg+xml;charset=utf-8,%3Csvg%20xmlns%3D'http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg'%20viewBox%3D'0%200%20585%20654'%2F%3E\" alt=\"Naming Conventions for Standard Data Vault Entities\" data-nectar-img-srcset=\"https:\/\/www.scalefree.com\/wp-content\/uploads\/2020\/05\/Figure-2-Naming-Conventions-for-Standard-Data-Vault-Entities.png 585w, https:\/\/www.scalefree.com\/wp-content\/uploads\/2020\/05\/Figure-2-Naming-Conventions-for-Standard-Data-Vault-Entities-268x300.png 268w, https:\/\/www.scalefree.com\/wp-content\/uploads\/2020\/05\/Figure-2-Naming-Conventions-for-Standard-Data-Vault-Entities-320x358.png 320w, https:\/\/www.scalefree.com\/wp-content\/uploads\/2020\/05\/Figure-2-Naming-Conventions-for-Standard-Data-Vault-Entities-360x402.png 360w\" sizes=\"auto, (max-width: 585px) 100vw, 585px\" \/>\n          <\/div>\n        <\/div>\n      <\/div>\n    <\/div>\n<div class=\"wpb_text_column wpb_content_element \" >\n\t<div class=\"wpb_wrapper\">\n\t\t<p><span style=\"font-weight: 400;\">**Note: <a href=\"https:\/\/www.scalefree.com\/blog\/data-vault\/point-in-time-tables-insurance\/\">PIT<\/a> and <a href=\"https:\/\/www.scalefree.com\/blog\/data-vault\/bridge-tables-101\/\" target=\"_blank\" rel=\"noopener\">bridge tables<\/a> are only available in Business Vault<\/span><\/p>\n<p style=\"text-align: center;\"><em>Figure 2: Naming Conventions for Standard Data Vault Entities<\/em><\/p>\n\t<\/div>\n<\/div>\n\n\n\n<div class=\"divider-wrap\" data-alignment=\"default\"><div style=\"height: 25px;\" class=\"divider\"><\/div><\/div>\n<div class=\"wpb_text_column wpb_content_element \" >\n\t<div class=\"wpb_wrapper\">\n\t\t<h2><span style=\"font-weight: 400;\">More about naming conventions for satellite entities<\/span><\/h2>\n\t<\/div>\n<\/div>\n\n\n\n<div class=\"divider-wrap\" data-alignment=\"default\"><div style=\"height: 25px;\" class=\"divider\"><\/div><\/div>\n<div class=\"wpb_text_column wpb_content_element \" >\n\t<div class=\"wpb_wrapper\">\n\t\t<p><em><span style=\"font-weight: 400;\">Satellite splitting criteria play a vital role in the naming conventions for satellite structures. In fact, it is not recommended that all <a href=\"https:\/\/www.scalefree.com\/scalefree-newsletter\/capturing-semi-structured-descriptive-data\/\">descriptive data<\/a> of a business object be stored in a single satellite structure &#8211; instead, raw data should preferably be split by certain criteria<\/span><span style=\"font-weight: 400;\">. ( Linstedt, D., &amp; Olschimke, M. (2016). Building a scalable Data Warehouse with Data Vault 2.0. P114-115)<\/span><\/em><\/p>\n<p><span style=\"font-weight: 400;\">At Scalefree, we have defined three types of satellite splits:\u00a0<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">split by source system\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">technical split by rate of change, security level and privacy level<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">and business-driven split<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">A satellite split by <a href=\"https:\/\/www.scalefree.com\/scalefree-newsletter\/satellite-modeling-for-any-structural-changes-in-the-source-system\/\">source system<\/a> and the technical split by rate of change of data are common, recommended practices when it comes to splitting descriptive attributes. However, we have decided to split raw data even further, both technically and by business meaning. <\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">As such, our full naming convention for satellite entities is as follows:<\/span><\/p>\n<p><span style=\"font-weight: 400;\">[parent-obj]_[biz-split]_[src]_[tech-split]_[satellite-type-suffix]<\/span><\/p>\n<p><span style=\"font-weight: 400;\">With:<\/span><\/p>\n<p style=\"padding-left: 40px;\"><span style=\"font-weight: 400;\">[parent-obj]<\/span> <span style=\"font-weight: 400;\">= the name of the satellite parent\u2019s business object<\/span><\/p>\n<p style=\"padding-left: 40px;\"><span style=\"font-weight: 400;\">[biz-split]<\/span> <span style=\"font-weight: 400;\">= the business classification,\u00a0<\/span><\/p>\n<p style=\"padding-left: 40px;\"><span style=\"font-weight: 400;\">[src]<\/span> <span style=\"font-weight: 400;\">= an abbreviation for the source system and\u00a0<\/span><\/p>\n<p style=\"padding-left: 40px;\"><span style=\"font-weight: 400;\">[tech-split]<\/span> <span style=\"font-weight: 400;\">= a combination of technical satellite splitting criteria.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Please note that the split denoted by different security levels classifies data into security groups. Thus, end users are given access to only certain groups of tables corresponding to their clearance level. <\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">As part of our process, the security levels range from:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">the lowest confidentiality level &#8211; level 0, 1: no security measure required, for public data,<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">to limited access to certain internal parties &#8211; level A, R, C, F.<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">to the highest confidentiality level &#8211; level S: top secret.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">It is important to take note that the final technical satellite splitting criterion within Scalefree\u2019s SOP is defined by the split in privacy level. This split is a necessary component of the process as it separates personal and non-personal information from each other.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Moving onwards, the business-driven satellite split distributes raw data into different satellite tables utilizing certain business meanings of data content. <\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">We have defined several classifications for this purpose, to name a few: \u201ccontact\u201d for contact data and \u201cactivity\u201d for data that tracks the interactions users have made with the source record. <\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">Additionally, data modelers can define custom business classifications for specified unique business meanings in business objects. <\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">For example, all data attributes of an application installed on the CRM platform <a href=\"https:\/\/www.scalefree.com\/consulting\/salesforce-solutions\/\">Salesforce<\/a> are often stored within a single satellite structure. Thus, the business-driven satellite split aims to boost usability and accessibility of the EDW for end users. It does so by assisting users in finding the data they require within the DWH in a way that is both faster and easier by classifying data into groups that have actual meaning to business users.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Putting everything together, here\u2019s an example of a satellite name in our internal EDW solution:<\/span><\/p>\n<p><i><span style=\"font-weight: 400;\">customer_contact_sfdc_lcp_s<\/span><\/i><\/p>\n<p><span style=\"font-weight: 400;\">The above is a satellite of business object Customer and holds customers\u2019 contact information from the source system Salesforce. Thus, its content has a low rate of change, a security level of C and contains personal data.<\/span><\/p>\n\t<\/div>\n<\/div>\n\n\n\n<div class=\"divider-wrap\" data-alignment=\"default\"><div style=\"height: 25px;\" class=\"divider\"><\/div><\/div>\n<div class=\"wpb_text_column wpb_content_element \" >\n\t<div class=\"wpb_wrapper\">\n\t\t<h2>Conclusion<\/h2>\n\t<\/div>\n<\/div>\n\n\n\n<div class=\"divider-wrap\" data-alignment=\"default\"><div style=\"height: 25px;\" class=\"divider\"><\/div><\/div>\n<div class=\"wpb_text_column wpb_content_element \" >\n\t<div class=\"wpb_wrapper\">\n\t\t<p><span style=\"font-weight: 400;\">In this article, we\u2019ve presented our recommendations regarding naming conventions for different types of data warehouse objects and offered an in-depth look into our considerations for satellite naming.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Are you interested in other naming standard aspects? Let us know in the comments section!<\/span><\/p>\n<p style=\"text-align: right;\">&#8211; by Trung Ta<\/p>\n\t<\/div>\n<\/div>\n\n\n\n\n\t\t\t<\/div> \n\t\t<\/div>\n\t<\/div> \n<\/div><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Namenskonventionen im Data Warehousing<\/p>","protected":false},"author":2,"featured_media":29605,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[100],"tags":[],"class_list":{"0":"post-29030","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-architecture"},"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.scalefree.com\/de\/wp-json\/wp\/v2\/posts\/29030","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.scalefree.com\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.scalefree.com\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.scalefree.com\/de\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.scalefree.com\/de\/wp-json\/wp\/v2\/comments?post=29030"}],"version-history":[{"count":0,"href":"https:\/\/www.scalefree.com\/de\/wp-json\/wp\/v2\/posts\/29030\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.scalefree.com\/de\/wp-json\/wp\/v2\/media\/29605"}],"wp:attachment":[{"href":"https:\/\/www.scalefree.com\/de\/wp-json\/wp\/v2\/media?parent=29030"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.scalefree.com\/de\/wp-json\/wp\/v2\/categories?post=29030"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.scalefree.com\/de\/wp-json\/wp\/v2\/tags?post=29030"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}