Documentos técnicos

Everything about data has changed, but that only means that data models are even more essential to understanding that data so that businesses can know what it means. As development methodologies change to incorporate Agile workflows, data architects must adapt to ensure models stay relevant and accurate. This whitepaper describes key requirements for Agile data modeling and shows how ER/Studio supports this methodology.

There are multiple considerations for collaborating on metadata within an organization, and you need a good metadata strategy to define and manage the right processes for a successful implementation. In this white paper, David Loshin describes how to enhance enterprise knowledge sharing by using collaborative metadata for structure, content, and semantics.

As an independent consultant, Ron Huizenga used both ERwin and ER/Studio with a wide range of customers. Based on his experience and evaluation, he concluded that ER/Studio had the right features and capabilities to address the complex enterprise data architecture needs of his clients. Read this paper to learn why he made the switch to ER/Studio.

In today’s enterprise data environment, businesses are dealing with a larger volume of data that has expanded in its variety and velocity, and must assess how to integrate the new ‘big data’ with their existing relational assets. In this analyst report, Carl Olofson shares his insights on the challenges, strategies, and benefits of working with complex data landscapes.

Metadata needs to be organized and managed if it is to be leveraged effectively. Published in the DBTA Best Practices Series, this article describes metadata and its value, outlines the importance of integrating metadata in an enterprise data environment, and reviews approaches to implementation.

As a modeling and collaboration platform, ER/Studio is a very capable environment to define, manage and organize metadata effectively. This allows business and data consumers understand how data is used across the organization. This Tech Note documents some of the features that make ER/Studio Data Architect and ER/Studio Team Server particularly well-suited for handling metadata.

In this white paper, Robin Bloor and Rebecca Jowiak from The Bloor Group discuss the value of metadata and the importance of organizing it well. Learn about the benefits of the ER/Studio Team Server, which lets you:

• Collaborate on metadata across your organization
• Manage disparate data sources and definitions
• Establish an enterprise glossary of business definitions and data elements
• Improve communication between teams

Your data models are brilliant... but only if the DBAs and developers are on the same page. Get more value through collaboration. How? In this white paper, Karen Lopez from InfoAdvisors, Inc. discusses strategies on how to build a little more teamwork and collaboration and get a lot more value from data modeling.

In this paper, you’ll learn:

• What ARRA, HITECH, Meaningful Use (MU), and Certification mean.
• How technical personnel such as data architects, DBAs and developers will be affected by MU.
• The best ways to determine the MU gaps that might be found in existing systems.
• Additional expertise technical personnel may need to meet MU.
• How quickly systems will need to be modified and deployed to meet MU rules.

To learn all you can about data modeling for your data warehouse and what to look out for, you need to know how to identify the primary issues that surface. This awareness can help when you run into a scenario where you find architecture that is not fully documented and different from the rest of your database designs.

In this whitepaper we’ll focus on seven common database design “sins” that can be easily avoided and suggest ways to correct them.