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
    sales and data analytics
    How Data Analytics Improves Lead Management and Sales Results
    9 Min Read
    data analytics and truck accident claims
    How Data Analytics Reduces Truck Accidents and Speeds Up Claims
    7 Min Read
    predictive analytics for interior designers
    Interior Designers Boost Profits with Predictive Analytics
    8 Min Read
    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
  • Big Data
  • BI
  • Exclusive
  • IT
  • Marketing
  • Software
Search
© 2008-25 SmartData Collective. All Rights Reserved.
Reading: Entry Point: Change is a Constant
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 > Entry Point: Change is a Constant
Data Warehousing

Entry Point: Change is a Constant

DataQualityEdge
DataQualityEdge
5 Min Read
SHARE

How many times have you received bad data from an upstream ‘stable’ database environment for no reason what so ever?

1…
2…
10…
13…
76…

Never…?

How’s this for a reply… no environment is stable! PERIOD.

More Read

The Horizon of Data Mining
Spotlight on Innovation
The World’s Most Unusual Data Centers [INFOGRAPHIC]
Estimating Extract, Transform, and Load (ETL) Projects
Changing Your Mind About Big Data Isn’t Dumb

Each and every data warehouse environment is subject to change, subject to growth, subject to budget constraints, and other external conditions (i.e., political changes). Their will always be change, THAT you cannot control.

Remember SOx. One recent example in Ontario is the Harmonized Sales Tax move. This means for those organizations tracking tax in their internal systems, they must make changes to their databases and systems to incorporate the HST and alter their PST and GST taxation collection and tracking in Ontario. This is a nice example of an externally forced-upon change. This particular impact will impact both Operational and Decision support systems.

Personal Experience:

The data files were coming in just fine from a source system that was considered stable (i.e., no data issues from them since project delivery).

Then one day, the volume dropped by more then 70% on file feeds received daily...


How many times have you received bad data from an upstream ‘stable’ database environment for no reason what so ever?

1…
2…
10…
13…
76…

Never…?

How’s this for a reply… no environment is stable! PERIOD.

Each and every data warehouse environment is subject to change, subject to growth, subject to budget constraints, and other external conditions (i.e., political changes). Their will always be change, THAT you cannot control.

Remember SOx. One recent example in Ontario is the Harmonized Sales Tax move. This means for those organizations tracking tax in their internal systems, they must make changes to their databases and systems to incorporate the HST and alter their PST and GST taxation collection and tracking in Ontario. This is a nice example of an externally forced-upon change. This particular impact will impact both Operational and Decision support systems.

Personal Experience:

The data files were coming in just fine from a source system that was considered stable (i.e., no data issues from them since project delivery).

Then one day, the volume dropped by more then 70% on file feeds received daily.

After some investigation the source system (System B) identified that their volumes had changed as well. They did not even know their data volume had decreased. The investigation was escalated to their source (system A), who identified that all the records where being sent to system B. There were no changes to System A, “more on that shortly.” Back to System B; they do not have the data. Open the source files and there the data was, the records that were missing were in the source files with blanks in the identifying fields.

A scheduled software (note scheduled) upgrade on System A, could not process French characters and inserted blanks in the initial fields and subsequent ID fields. So when System B arrived to pick up the record IDs it found nothing to insert.

A simple software upgrade that resulted in wasted time, money and missing data.

 

Ignore the potential for change and you will be left holding an empty bag. Never get comfortable.

Remember to inform all your upstreamers of how their changes may potentially become a critical impact to your environment.

Some of the most common forms of changes in systems are the result of the following items:

  • Data integration
  • Mergers and acquisitions
  • Politics, laws and regulations,
  • Software changes
  • Web interfaces (change of portals)
  • Hardware changes

I’m certain you may be able to add to this short list, and I welcome you to.

If you are someone making change, remember to practice proper Change Management techniques, a topic for future discussions.

TAGGED:changedata quality
Share This Article
Facebook Pinterest LinkedIn
Share

Follow us on Facebook

Latest News

sales and data analytics
How Data Analytics Improves Lead Management and Sales Results
Analytics Big Data Exclusive
ai in marketing
How AI and Smart Platforms Improve Email Marketing
Artificial Intelligence Exclusive Marketing
AI Document Verification for Legal Firms: Importance & Top Tools
AI Document Verification for Legal Firms: Importance & Top Tools
Artificial Intelligence Exclusive
AI supply chain
AI Tools Are Strengthening Global Supply Chains
Artificial Intelligence Exclusive

Stay Connected

1.2kFollowersLike
33.7kFollowersFollow
222FollowersPin

You Might also Like

Capacity for change

3 Min Read

Commendable Comments (Part 3)

8 Min Read

Building Competitive Advantage through New Data

4 Min Read

5 Lessons Social CRM can Learn from CRM

8 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 in ecommerce
Artificial Intelligence for eCommerce: A Closer Look
Artificial Intelligence
ai chatbot
The Art of Conversation: Enhancing Chatbots with Advanced AI Prompts
Chatbots

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?