Exam 70-767: Implementing a Data Warehouse using SQL

-
Exam Topics

Design, implement, and maintain a data warehouse (35–40%)

  • Design and implement dimension tables
·        Design shared and conformed dimensions, determine supportrequirements for slowly changing dimensions, determine attributes, design hierarchies, determine star or snowflake schema requirements, determine the granularity of relationship by using fact tables, determine auditing or lineagerequirements, determine keys and key relationships for a data warehouse, implement dimensions, implement data lineage of a dimension table
  • Design and implement fact tables
·        Identify measures, identify dimension table relationships, create composite keys, design a data warehouse that supports many-to-manyrelationships, implement semi-additive measures, implement non-additivemeasures
  • Design and implement indexes for a data warehouse workload
·       Design an indexing solution; select appropriate indexes; implement clustered, non-clustered, filtered, and columnstore indexes
  • Design storage for a data warehouse
·        Design an appropriate storage solution, including hardware,disk, and file layout
  • Design and implement partitioned tables and views
·        Design a partition structure to support a data warehouse, implement sliding windows, implement partition elimination, design a partitionstructure that supports the quick loading and scale-out of data
  • Manage and maintain a SQL Data Warehouse
·        Manage queries by using labels; manage statistics; manage partition distribution; scale out the data warehouse; grow, shrink, and pause the data warehouse

Extract, transform, and load data (40–45%)

  • Design and implement an extract, transform, and load (ETL) control flow by using a SQL Server Integration Services (SSIS) package
·        Design and implement ETL control flow elements, includingcontainers, tasks, and precedence constraints; create variables and parameters; create checkpoints, sequence and loop containers, and variables in SSIS; implement data profiling, parallelism, transactions, logging, and security
  • Design and implement an ETL data flow by using an SSIS package
·        Implement slowly changing dimension, fuzzy grouping, fuzzylookup, audit, blocking, non-blocking, and term lookup transformations; map columns; determine the appropriate transform object for a given task; determineappropriate scenarios for Transact-SQL joins versus SSIS lookup; design table loading by using bulk loading or standard loading; remove extra rows or bad rows by using deduplication
  • Implement an ETL solution that supports incremental data extraction
·        Design fact table patterns, enable Change Data Capture, create aSQL MERGE statement
  • Implement an ETL solution that supports incremental data loading
·        Design a control flow to load change data, load data by usingTransact-SQL Change Data Capture functions, load data by using Change Data Capture in SSIS
  • Debug SSIS packages
·        Fix performance, connectivity, execution, and failed logicissues by using the debugger; enable logging for package execution; implement error handling for data types; implement breakpoints; add data viewers; profile data with different tools; perform batch clean-up
  • Deploy and configure SSIS packages and projects
·        Create an SSIS catalog; deploy packages by using the deploymentutility, SQL Server, and file systems; run and customize packages by using DTUTIL

Build data quality solutions (15–20%)

  • Create a knowledge base
·        Create a Data Quality Services (DQS) knowledge base, determineappropriate use cases for a DQS knowledge base, perform knowledge discovery, perform domain management
  • Maintain data quality by using DQS
·        Add matching knowledge to a knowledge base, prepare a DQS for data deduplication, create a matching policy, clean data by using DQS knowledge clean data by using the SSIS DQS task, install DQS
  • Implement a Master Data Services (MDS) model
·        Install MDS; implement MDS; create models, entities, hierarchies, collections, and attributes; define security roles; import and export data; create and edit a subscription; implement entities, attributes, hierarchies, and business rules
  • Manage data by using MDS
·        Use MDS tools, use the Master Data Services ConfigurationManager, create a Master Data Manager database and web application, deploy a sample model using MDSModelDeploy.exe, use the Master Data Services web application, use the Master Data Services Add-in for Excel, create a Master Data Management hub, stage and load data, create subscription views

Comments

  1. UnknownJuly 6, 2018 at 2:57 AM

    Thank you so much for sharing that valuable blog.You put Good stuff. All the subjects were cleared up briefly.Keep in blogging. Vendor Reconciliation
    Warehouse Audit
    Stock Audit

    ReplyDelete
  2. isabellaSeptember 5, 2018 at 5:30 AM

    This comment has been removed by the author.

    ReplyDelete
  3. isabellaNovember 19, 2018 at 2:06 AM

    Thanks for sharing; I got more information from this blog. I would like to see your updates regularly so keep blogging. Duplicate Payment Review
    Duplicate Payment Recovery | Continuous Transaction Monitoring

    ReplyDelete

Post a Comment

Popular Posts

Non-blocking, semi-blocking, and blocking transforms in SSIS

-
Not all Data Flow transforms are created equal. In fact, some are much faster and require a  lot less memory (non-blocking transforms). Others are slower while consuming much more  memory (blocking transforms), and some are in between (semi-blocking transforms). We don’t  always have a choice if we need to use a certain transform to do a certain specified task, but  it is good to know the differences between these types of transforms so that we can better  understand performance and resource utilization issues. Synchronous and asynchronous There is another related aspect about Data Flow transforms, which is their ability to quickly  process a row as they are coming into the transform, independently of any other rows that  came before or after (synchronous transforms). The other type of transform needs to be  dependent on some or all of the rows that come before and after (asynchronous transforms). On the whole, non-blocking transforms a...
Read more

Implement additive, semi-additive, and non-additive measures

-
Additive Additive measures are numeric values that can be summed up by all the dimensions in the  fact table, for example the Sales Amount. These are the most common measures and they are  the easiest to understand and implement. Semi-additive Semi-additive measures are numeric values that can be summed up by some dimensions  in the fact table, but not all. In most cases, they can be aggregated by any other dimension  except time.  An example of a semi-additive measure is Account Balance. You can determine  the ending balance of an account at the end of a month, but adding up these monthly account  balances do not make sense. Semi-additive measures are usually found in fact tables that store  periodic snapshots of data. Non-additive Non-additive measures, as the name implies, are measures that cannot be summed up.  These measures include percentages such as Discount Percent, ratios such as Profit Margin, and  averages ...
Read more

Implement an ETL solution that supports incremental data extraction

-
Image
Design fact table patterns Fact tables used in data warehouses can become the very large, very fast by order of magnitude.  It’s important to implement best practices for fact table design at the onset, even if your  fact table does not contain billions of rows. Here are some things to be aware and include in  your fact table design: Consider partitioning your fact tables when they are larger than 100 GB. The partitions can be by any column, which provides a fairly equal distribution of your data. Usually the Date columns (not DateTime columns) are good candidates. This provides more granularity when creating indexes, loading, updating, and deleting data (by partitions) Faster data access for queries by limiting the IO to specific partitions Utilize partition switching to move data in and out almost instantaneously Implement sliding window using partition splitting and partition merging Build clustered indexes on the Date Key of the fact tables (not...
Read more