dbTalk Databases Forums  

Why is database integrity so impopular ?

comp.databases.theory comp.databases.theory


Discuss Why is database integrity so impopular ? in the comp.databases.theory forum.

Reply
 
Thread Tools Display Modes
  #321  
Old   
whileone
 
Posts: n/a

Default Re: Why is database integrity so impopular ? - 11-10-2008 , 10:06 AM






On Oct 5, 11:30*am, eric.bouchardlefeb... (AT) gmail (DOT) com wrote:
Quote:
Hello,

When time comes to build transactional databases (as opposed to data
wharehouses), I belong to the school that STRONGLY believe in
normalizing data with high integrity mechanisms. *I know all the
performance cons but IMHO, pros largely overwhelme.

Just to be difficult.....

This is now a long thread, with numerous well-crafted arguments
exhaustively
defending good database design. But (largely for the sake of
argument)
there are times when bad design is called for.

For large, well-funded projects, performance can always
be purchased, usually for far less than the maintenance costs
associated with
bad design.

But smaller, not-so-well funded systems are part of the bell curve
too.
I wrote a web-based administration system for an "outfitters"
organization once.
There were about 1000 licensed outfitters that needed to be tracked
by a single-person administrator. So there was a private interface
plus a
public one. The public interface was supposed to
include a keyword search that combined outfitter location with
arbitrary
combinations of attribute keywords like "elk hunting, fly fishing,
walleye, pheasant" etc.

This organization had a limited budget and insisted on
a cheap shared host server. Mysql queries with mulitiple named
cursors
ran like lightning on my desktop linux box, but they ran like half-
frozen molasses
on the overloaded shared host server.

But application code that did "string-like" over a long string of
comma-separated
keywords worked, and it ran an order of magnitude faster (on the
chintzy shared
host).




Reply With Quote
  #322  
Old   
whileone
 
Posts: n/a

Default Re: Why is database integrity so impopular ? - 11-10-2008 , 10:06 AM






On Oct 5, 11:30*am, eric.bouchardlefeb... (AT) gmail (DOT) com wrote:
Quote:
Hello,

When time comes to build transactional databases (as opposed to data
wharehouses), I belong to the school that STRONGLY believe in
normalizing data with high integrity mechanisms. *I know all the
performance cons but IMHO, pros largely overwhelme.

Just to be difficult.....

This is now a long thread, with numerous well-crafted arguments
exhaustively
defending good database design. But (largely for the sake of
argument)
there are times when bad design is called for.

For large, well-funded projects, performance can always
be purchased, usually for far less than the maintenance costs
associated with
bad design.

But smaller, not-so-well funded systems are part of the bell curve
too.
I wrote a web-based administration system for an "outfitters"
organization once.
There were about 1000 licensed outfitters that needed to be tracked
by a single-person administrator. So there was a private interface
plus a
public one. The public interface was supposed to
include a keyword search that combined outfitter location with
arbitrary
combinations of attribute keywords like "elk hunting, fly fishing,
walleye, pheasant" etc.

This organization had a limited budget and insisted on
a cheap shared host server. Mysql queries with mulitiple named
cursors
ran like lightning on my desktop linux box, but they ran like half-
frozen molasses
on the overloaded shared host server.

But application code that did "string-like" over a long string of
comma-separated
keywords worked, and it ran an order of magnitude faster (on the
chintzy shared
host).


Reply With Quote
  #323  
Old   
whileone
 
Posts: n/a

Default Re: Why is database integrity so impopular ? - 11-10-2008 , 10:06 AM



On Oct 5, 11:30*am, eric.bouchardlefeb... (AT) gmail (DOT) com wrote:
Quote:
Hello,

When time comes to build transactional databases (as opposed to data
wharehouses), I belong to the school that STRONGLY believe in
normalizing data with high integrity mechanisms. *I know all the
performance cons but IMHO, pros largely overwhelme.

Just to be difficult.....

This is now a long thread, with numerous well-crafted arguments
exhaustively
defending good database design. But (largely for the sake of
argument)
there are times when bad design is called for.

For large, well-funded projects, performance can always
be purchased, usually for far less than the maintenance costs
associated with
bad design.

But smaller, not-so-well funded systems are part of the bell curve
too.
I wrote a web-based administration system for an "outfitters"
organization once.
There were about 1000 licensed outfitters that needed to be tracked
by a single-person administrator. So there was a private interface
plus a
public one. The public interface was supposed to
include a keyword search that combined outfitter location with
arbitrary
combinations of attribute keywords like "elk hunting, fly fishing,
walleye, pheasant" etc.

This organization had a limited budget and insisted on
a cheap shared host server. Mysql queries with mulitiple named
cursors
ran like lightning on my desktop linux box, but they ran like half-
frozen molasses
on the overloaded shared host server.

But application code that did "string-like" over a long string of
comma-separated
keywords worked, and it ran an order of magnitude faster (on the
chintzy shared
host).


Reply With Quote
  #324  
Old   
whileone
 
Posts: n/a

Default Re: Why is database integrity so impopular ? - 11-10-2008 , 10:06 AM



On Oct 5, 11:30*am, eric.bouchardlefeb... (AT) gmail (DOT) com wrote:
Quote:
Hello,

When time comes to build transactional databases (as opposed to data
wharehouses), I belong to the school that STRONGLY believe in
normalizing data with high integrity mechanisms. *I know all the
performance cons but IMHO, pros largely overwhelme.

Just to be difficult.....

This is now a long thread, with numerous well-crafted arguments
exhaustively
defending good database design. But (largely for the sake of
argument)
there are times when bad design is called for.

For large, well-funded projects, performance can always
be purchased, usually for far less than the maintenance costs
associated with
bad design.

But smaller, not-so-well funded systems are part of the bell curve
too.
I wrote a web-based administration system for an "outfitters"
organization once.
There were about 1000 licensed outfitters that needed to be tracked
by a single-person administrator. So there was a private interface
plus a
public one. The public interface was supposed to
include a keyword search that combined outfitter location with
arbitrary
combinations of attribute keywords like "elk hunting, fly fishing,
walleye, pheasant" etc.

This organization had a limited budget and insisted on
a cheap shared host server. Mysql queries with mulitiple named
cursors
ran like lightning on my desktop linux box, but they ran like half-
frozen molasses
on the overloaded shared host server.

But application code that did "string-like" over a long string of
comma-separated
keywords worked, and it ran an order of magnitude faster (on the
chintzy shared
host).


Reply With Quote
  #325  
Old   
whileone
 
Posts: n/a

Default Re: Why is database integrity so impopular ? - 11-10-2008 , 10:06 AM



On Oct 5, 11:30*am, eric.bouchardlefeb... (AT) gmail (DOT) com wrote:
Quote:
Hello,

When time comes to build transactional databases (as opposed to data
wharehouses), I belong to the school that STRONGLY believe in
normalizing data with high integrity mechanisms. *I know all the
performance cons but IMHO, pros largely overwhelme.

Just to be difficult.....

This is now a long thread, with numerous well-crafted arguments
exhaustively
defending good database design. But (largely for the sake of
argument)
there are times when bad design is called for.

For large, well-funded projects, performance can always
be purchased, usually for far less than the maintenance costs
associated with
bad design.

But smaller, not-so-well funded systems are part of the bell curve
too.
I wrote a web-based administration system for an "outfitters"
organization once.
There were about 1000 licensed outfitters that needed to be tracked
by a single-person administrator. So there was a private interface
plus a
public one. The public interface was supposed to
include a keyword search that combined outfitter location with
arbitrary
combinations of attribute keywords like "elk hunting, fly fishing,
walleye, pheasant" etc.

This organization had a limited budget and insisted on
a cheap shared host server. Mysql queries with mulitiple named
cursors
ran like lightning on my desktop linux box, but they ran like half-
frozen molasses
on the overloaded shared host server.

But application code that did "string-like" over a long string of
comma-separated
keywords worked, and it ran an order of magnitude faster (on the
chintzy shared
host).


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.