Re: Proposed Solution :: DB Design Dilemma!! One DB or Many DBs??

robhindman_at_hotmail.com (Rob Hindman) wrote in message news:<d4199cf5.0202140817.55a579ae_at_posting.google.com>...
> Guys, thanks for your input, but I think you're being a bit too
> harsh...

When I read what your solution was going to be, I had that sinking, awful, pit of the stomach feeling, but not my business.

Then when I read what the other gentleman wrote about not hiring on there, I went "yeah, no s@#&, I wouldnt' want to work on that."

And I had realized, and gave credit to those who told you their truth, and felt kinda weiny for not doing it myself.

Then when you didn't catch the clue, I thought I'd throw in my two bits.

The multiple table/database/scattered all over hell approach sucks. You really need to sit down and figure out the solution for one site. It is NOT 3 tables. I bet it is 30 tables to effectively solve the needs for a simple solution. Now syncronize that and multiply it out across all your sites, then make an update to a record somewhere and see what happens. If that works, then try to get a grand total of agings and see what happens.

You guys need a GOOD data analyst/designer on your team.

-Doug Miller Received on Fri Feb 15 2002 - 10:34:28 CST