Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Model Design   (RSS)
Monday, April 27, 2009 4:15 PM

Localizing a report model

Reports and report models can be localized at many levels. Following are some ideas around the current support in SQL Server 2008 for each type of localization. - Localized metadata at report design time o Example : Spanish report author sees “Cliente”
Posted by bobmeyers | 0 Comments
Monday, April 27, 2009 1:58 PM

Considerations for a large report model

Customer report models that vary in size from a few to a few hundred entities. Little Northwind with its 10 or so entities comes in around 200K, but we've seen models a hundred times that size (over 20 MB). One of the key drivers of model size is the
Posted by bobmeyers | 4 Comments
Thursday, March 05, 2009 7:00 AM

A better way to model inheritance

I've been playing around with a report model we use internally here in the SQL Server product group. At a conceptual level, the data being modeled makes heavy use of inheritance (EntityA "is a" EntityB), but in working with the model and with Report Builder,
Posted by bobmeyers | 1 Comments
Filed under: ,
Wednesday, December 20, 2006 4:43 PM

Creating a role to one of several related items

I call this the Primary Address problem, because a classic example is when you have a Customer table and an Address table, and each customer can have many addresses (Primary, Billing, Shipping, etc.), but no more than one of any given type. If you have
Posted by bobmeyers | 9 Comments
Filed under: ,
Thursday, September 28, 2006 11:30 AM

Evolving your report model over time

Many factors combine to make report models highly likely to change and evolve over time. Sometimes the underlying schema changes. Sometimes new stuff is added. Sometimes you just want to improve how the schema is presented to users. Report models are
Posted by bobmeyers | 2 Comments
Filed under: ,
Thursday, September 28, 2006 11:20 AM

Creating a report model that can be used against multiple databases

Sometimes it is useful to create a report model that can be used against multiple databases that have the same structure, but reside on different servers and/or have different schema qualifiers. Uploading a second copy of a report model and pointing it
Posted by bobmeyers | 5 Comments
Filed under: ,
Friday, March 24, 2006 6:02 PM

How to create a 'company' security filter for a hosted application

Several customers have asked how to restrict data visibility in a report model for a hosted application, where every table has a "CompanyID" column, and every user that accesses the system is associated (via some other table) with exactly one company.
Posted by bobmeyers | 3 Comments
Friday, March 24, 2006 7:51 PM

Collapsing a many-to-many relationship in a report model

Often a many-to-many relationship exists between two entities where the intermediate entity has nothing on it except the connecting roles. For example, it might be that an Employee can be assigned to many Regions, and each Region can have many Employees
Posted by bobmeyers | 8 Comments
Filed under: , ,
Thursday, January 19, 2006 11:50 PM

Report model denormalization: Why, How, and When

Relational databases are often heavily normalized to improve performance, reduce storage requirements, and ensure data consistency. While performance may be relevant to report execution, neither of these reasons is relevant when presenting the schema
Posted by bobmeyers | 6 Comments
Filed under: ,
Tuesday, October 25, 2005 10:19 PM

What to do with IdentifyingAttributes and DefaultDetailAttributes?

SQL 2005 report models will ship with a curious and admittedly incomplete solution for handling "the information users typically want to see about an instance of entity X". The problem is that there are many scenarios for which the answer to that question
Posted by bobmeyers | 1 Comments
 
Page view tracker