> You don't know much about databases, eh?
A well written program with a well designed database can deliver your
miages quite quickly. Depending on the database, it can be twice as
fast or only somewhat faster. It's seldom slower than having
thousands of files in a directory for a program to search through.
It also has nothing to do with Microsoft.
Now if you could just learn how to attribute correctly, you'd have the
medium of USENet to list among things you know how to do.
Well I may not know much about them, but at least have 10 years of
experience and currently working on one similiar project and have one
program running for 3 years without a hickup with a few 100K pictures (0.5
TByte on Raid 5 controller). Well, I may not be doing things the way MS and
other "Authoritie s" suggest, but I usually end up with rock solid
solutions...
....my programs don't utilise the Registry, but they can be easily installed,
don't screw up, and have never done one machine, and one can run multiple
copies of it at the same time, if for same strange reason one needs to. One
may also run older versions of the same thing simultaneously. ..etc
This is not because of my higher IQ or because I am a smarter programmer. I
think it is simply because I don't overcomplicate things when it is not
needed...
I beleive in simple and elegant solutions, simple straight logic.
I still think, horses for courses! I like to see how will you deliver a
number of pictures from a database significantly quicker through an SQL
server than straight from a well organised Hierachical File Structure, which
gets pretty close to optimal binary search....
considering that you have to read the data from a hard-drive into say an SQL
server, than feed it to IIS
opposed to sending a link to the browser and IIS sends the files
down....also I am curious which will be more processor hungry?
And I agree with you on that a lot depend on the iumplementation :-)
Regards,
Tom