Re: Do not SELECT
- From: Hugo Kornelis <hugo@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 08 May 2007 21:43:40 +0200
On Mon, 7 May 2007 09:38:00 -0700, Lubomir wrote:
Hi Hugo,
The reason is, that that this application serves more application (like
plugins) with their own tables.
Hi Lubomir,
As long as the data requirements for all these plugin applications are
relatively stable, they can each have their own set of tables that
you'll have to design and deploy once (and possibly more often, if and
when requirements change).
If the data requirements can change on a daily basis, you're probably
best advised to move away from relational databases, since they're
really designed to be used with a fixed datamodel.
--
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
.
- References:
- Re: Do not SELECT
- From: Hari Prasad
- Re: Do not SELECT
- From: Hugo Kornelis
- Re: Do not SELECT
- Prev by Date: Re: User, login role, schema
- Next by Date: Re: SQL Server 2000 & SQL Server 2005
- Previous by thread: Re: Do not SELECT
- Next by thread: Re: Do not SELECT
- Index(es):