Posted by Erland Sommarskog on 07/11/05 00:40

David Portas (REMOVE_BEFORE_REPLYING_dportas@acm.org) writes:
> Could you give us an example of when "having a good data model" is NOT
> appropriate?

The standard example would be when you have a third-party application,
and you are supposed to write some home-brewed queries for reports. In
this situation you don't start redesigning the data model, how flawed it
may be.

Although, my guess is that Wolfgang tried to say even if you have a good
data model, that alone does evade the needs for modularizing your code.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

[Back to original message]