The key to your answer, really lies in the future of the project. You are
currently working on version 1? How will the programmers accommodate changes
once you and your customers require structural / logical changes for version
2.
Version 2 will required more complex relationships using existing tables.
The database may grow to an astronomical size. The number of users may
increase 1000 fold (is this app going to be run on the Internet
eventually.... in the long run?)
Will putting code in the database provide for version 2, or is code better
off being placed into DLLs and run under Microsoft's Transaction Server?
Will the database be used to support both version 1 of an application and
also version 2 of the same application, or will everyone have to upgrade
immediately to version 2 to start using the new database? Once you upgrade
to version 2 and it's not suitable, and you're faced with a re-write, then
what?
I personally never put rules into the database.
That's my 2 cents worth...
--
Pete
Barnel Saintilma <bt974_at_ncf.ca> wrote in message
news:38937789.3704C58E_at_ncf.ca...
