What You Don’t Know About Database Sharing Could Hurt You

What You Don’t Know About Database Sharing Could Hurt You

If you’re not part of the corporate IT staff, should you care about the nitty-gritty of how your organization shares complex relational databases? The answer is yes, if you are: A Fortune 2000 organization that could better fill rush orders if it could bring new suppliers on board more quickly. A small, specialty supplier that could sell to more, and bigger, customers if it could easily access their production forecasts. A growing business in an emerging market that needs to avoid the complexity and expense of electronic data interchange just to share business data. A CFO who could understand his business better if his financial analysts could more easily access and drill into raw financial data. A Big Data service provider that could make more sales if it could more easily share its insights and data results with its customers, or Any organization that could cut costs or increase sales by doing a better job analyzing data. Why “Relational” Matters If you’re storing any substantial amount of information about customers, distributors, suppliers, raw materials, products, sales, costs or profits, it’s probably in a relational database.  This “relational” capability is critical because it allows you to explore the relationships among different subsets of the data in unpredictable ways to meet new challenges. Let’s say, for example, you’re a sales manager for a retail chain trying to understand why sales fell so far in January. You suspect it’s due to a flu outbreak, and knowing the answer could help you better track future flu outbreaks and adjust stock and promotions accordingly. You have your business analysts compare county-by-county sales of specific products with state data on county-by-county instances of the flu. This is the type of ad-hoc query that’s so important to the business, and is the core function of a relational database.  Even just sharing production forecasts between a customer and supplier require a relational format so the customer can compare suppliers on metrics such as price, on-time delivery and quality. Yet it is exactly these business-critical relational capabilities that most current database sharing approaches strip away – or preserve only at a cost that is too high for most customers. Key Requirements Retaining table structures is important because database queries require them. Comparing specific product sales per store against county-level flu levels might require one table listing sales per store, another listing flu cases per county, and yet another table...

Read More