NYCPHP Meetup

[Tim Gales]

 Mitch Pirtle writes:

> If the organization decides to commit to a particular 
> database platform (for whatever reason), not using all of the 
> features available to your advantage just makes no sense.

Well, it can turn out that major portions of your database 
contain information, which is primarily read-only.

Even the niftiest stored procedure capabilities and 
transactional rollback facilities cannot be implemented  
in such a was as to use  "all of the features available" 
on read-only tables.

Being able to use compressed tables as well as (in) memory 
tables in places and transaction-safe tables only where 
you need them can be a decided advantage.
(as usual, it depends on what it is you are trying to do) 

T. Gales & Associates
'Helping People Connect with Technology'

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 266.5.7 - Release Date: 3/1/2005