Cookies help us display personalized product recommendations and ensure you have great shopping experience.

By using this site, you agree to the Privacy Policy and Terms of Use.
Accept
SmartData CollectiveSmartData Collective
  • Analytics
    AnalyticsShow More
    image fx (67)
    Improving LinkedIn Ad Strategies with Data Analytics
    9 Min Read
    big data and remote work
    Data Helps Speech-Language Pathologists Deliver Better Results
    6 Min Read
    data driven insights
    How Data-Driven Insights Are Addressing Gaps in Patient Communication and Equity
    8 Min Read
    pexels pavel danilyuk 8112119
    Data Analytics Is Revolutionizing Medical Credentialing
    8 Min Read
    data and seo
    Maximize SEO Success with Powerful Data Analytics Insights
    8 Min Read
  • Big Data
  • BI
  • Exclusive
  • IT
  • Marketing
  • Software
Search
© 2008-25 SmartData Collective. All Rights Reserved.
Reading: 5 Simple Tidbits to Include in Your Data Error Report
Share
Notification
Font ResizerAa
SmartData CollectiveSmartData Collective
Font ResizerAa
Search
  • About
  • Help
  • Privacy
Follow US
© 2008-23 SmartData Collective. All Rights Reserved.
SmartData Collective > Big Data > Data Warehousing > 5 Simple Tidbits to Include in Your Data Error Report
Data Warehousing

5 Simple Tidbits to Include in Your Data Error Report

DataQualityEdge
DataQualityEdge
5 Min Read
SHARE

ETL code and processes are key in the operations of updating and maintaining a data warehouse. A good operational set-up will have data error reports available for the data quality analyst to verify and action.

Traditionally an error report will tell you the data is wrong, provide an error code which relates to a very lame description of the error. In many cases it was written by a business analyst who has worked a long-time on the project and just wants to wrap up the work and move on to the next project. Therefore, in those cases the support analyst or data analyst will be left holding the bag, or scratching their head when they do get a data error. Don’t let it get to that, push back and ask for more.

These are a few items to include in the error reports to make life easier for the support team, other than an error code.

Include:

More Read

Alberto’s Business Analytics Predictions for 2012
Why In-Memory Analytics is Like Digital Photography: An Industry Transformation
Do Customers REALLY Want to Know What’s Inside the Black Box?
“We’re developing a bag of algorithms to be plugged together,” said William Pulleyblank, chief of…”
On-Demand Software Index: A selective bounce

1. Job number/name: this is an easy find to report on, this is the job that was handling the data when the error occurred.

2. Impacted Table: not everyone will know what job impacts what table, so include it, this will provide immediate recognition of the type of data your dealing with.

3. Primary Index: having the primary index will allow you to search f…

ETL code and processes are key in the operations of updating and maintaining a data warehouse. A good operational set-up will have data error reports available for the data quality analyst to verify and action.

Traditionally an error report will tell you the data is wrong, provide an error code which relates to a very lame description of the error. In many cases it was written by a business analyst who has worked a long-time on the project and just wants to wrap up the work and move on to the next project. Therefore, in those cases the support analyst or data analyst will be left holding the bag, or scratching their head when they do get a data error. Don’t let it get to that, push back and ask for more.

These are a few items to include in the error reports to make life easier for the support team, other than an error code.

Include:

1. Job number/name: this is an easy find to report on, this is the job that was handling the data when the error occurred.

2. Impacted Table: not everyone will know what job impacts what table, so include it, this will provide immediate recognition of the type of data your dealing with.

3. Primary Index: having the primary index will allow you to search for the record that is at fault either in the temporary table, or in a temporary holding file.

4. A brief meaningful description of the error, a two-word error message just does not cut it in many situations.

5. The most important piece of information to include in an error report would be to identify the action required to fix it. This is often excluded by many business analysts as they gather requirements. Data quality is often omitted from requirements and the business does not know the data the way they should (but are getting better), and have no idea how to correct it. It is a significant piece of information that will save significant amounts of time on the part of your support team. In the event you are not able to put the action required in an error report (due to possible text length or most often funding), reference the error back to the appropriate document that contains the actions required.

Just remember no one likes to get an error report, alert or notification identifying what has broken next. So make it easier for all those support analysts out there, give them what they need.

 
TAGGED:data qualityetl
Share This Article
Facebook Pinterest LinkedIn
Share

Follow us on Facebook

Latest News

power supplies for ATX for data scientists
Why Data Scientists Should Care About SFX Power Supplies
Big Data Exclusive
AI for website optimization
Free Tools to Test Website Accessibility
Artificial Intelligence Exclusive
Generative AI models
Thinking Machines At Work: How Generative AI Models Are Redefining Business Intelligence
Artificial Intelligence Business Intelligence Exclusive Infographic Machine Learning
image fx (2)
Monitoring Data Without Turning into Big Brother
Big Data Exclusive

Stay Connected

1.2kFollowersLike
33.7kFollowersFollow
222FollowersPin

You Might also Like

Data Quality – Everyone is a Stakeholder

7 Min Read

#7: Here’s a thought…

7 Min Read

Shut Your Mouth

5 Min Read

DQ Problems? Start a Data Quality Recognition Program!

5 Min Read

SmartData Collective is one of the largest & trusted community covering technical content about Big Data, BI, Cloud, Analytics, Artificial Intelligence, IoT & more.

ai chatbot
The Art of Conversation: Enhancing Chatbots with Advanced AI Prompts
Chatbots
AI and chatbots
Chatbots and SEO: How Can Chatbots Improve Your SEO Ranking?
Artificial Intelligence Chatbots Exclusive

Quick Link

  • About
  • Contact
  • Privacy
Follow US
© 2008-25 SmartData Collective. All Rights Reserved.
Go to mobile version
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?