In the day-to-day throws of a data warehousing initiative, it’s sometime difficult to identify the larger, farther-reaching issues that may not sink your project immediately, but may have costly consequences down the road. 

Many times, the goal it to simply *get it finished,* but like many things, finishing strong pays dividends for a long, long time.  Here then, are a quick list of issue that we regularly see that need to be addressed sooner than later.

  1. Convoluted ETL Process If you find that your ETL process is “somewhat complexed,” I have a simple question:  Where is it going from here?  I’ve sat in too many meeting in which a technical resource walks a room-full of team members and business-types through the finer points of the ETL process that seems remarkably complicated, perhaps unnecessarily.  Understandably, ETL is inherently involved, but an inability to succinctly explain and clearly show (read: demonstrate) the process is only going to create a situation in the near future once the resource has left, or been re-assigned, that is going to make revisions or updates problematic.
     
  2. Limited Responsiveness – Building on item #1, the amount of time required to find, make, test and implement changes to a data initiative may be significant, and as a result, the responsiveness that you discover from the group supporting your project is less than ideal.  What we see most frequently is that teams that aren’t able to quickly respond to the needs of the business are trying to support, in many cases, the unsupportable.  A "brittle" data warehouse, for example, works just as designed, but making changes to it requires a significant time investment to either figure-out… or more commonly… re-write the process.  And, the result is that you’re going to have to live with a high-maintenance, high-touch data solution that is effectively inflexible.  And, that’s a real problem.
     
  3. Resource Dependence – If your data initiative has a specific resource primarily because he/she is the only resources that know how it works… you’re going to have a problem, and you’re going to be held hostage at the most inconvenient time possible.  This is a problem for a lot of reasons, not least of which, because any changes (updates, enhancements, additions, etc.) are only going to serve to demonstrate continued dependence on a single point failure.  At some point, you’re going to have to pay that resource an ever-increasing amount, or they’re simply going to leave at a time not of your choosing.
     
  4. Project Delays – Delays in the course of a project are far too common, and provide glimpse of what you can expect going forward.  Occasionally, project delays come from the classic “eyes bigger than their stomachs” syndrome as it relates to defining dates and deliverables. However, I would submit, it’s frequently because that time is being invested in the wrong things.  Rather than focusing 100% of the effort on specific business deliverables, it’s regularly invested in solving problems and building-out infrastructure that could be acquired at a fraction of the cost.
     
  5. Poor Performance – Subpar performance comes in a lot of forms, but it regularly stems from the same source: a general lack of acknowledgement of the scope/scale of the required data, and the necessary architecture to fully support it.  Poor performance has probably undermined more data solutions than anything else, as it’s not a binary scale… and regularly gets explained away.

Take the RISK out of your next SQL Server data initiative, or RESCUE the one you're worried about.  Give our team a call at 317.313.5200, and see how the Datawa.re table-driven, data warehousing framework can accelerate your project by:

  • Using Better Technology – A better technology architecture means a better data solution. The Datawa.re architecture is unmatched for building the best foundation for your data strategy built on Microsoft® technology.
     
  • Being More Responsive and Agile – Moving at the speed of business isn't easy without the right tools.  Datawa.re makes responding to changing business needs easy when new opportunities arise.
     
  • Making it Easy to Live With – No new tools to install, no new tools to learn. Based on Microsoft SQL Server®, the Datawa.re approach and platforms fit nicely into your organization's existing IT strategy.

Visit www.datawa.re

Comment