A different approach; because this site is rather large, and the concept of normalization as a programmer pisses me off, I think I may have come up with and interesting side solution....


If I ran one database set up as a completely denormalizsed temp database (to less strain on database A and create less robust calls from the AJAX layer) is this considered poor in any case, really? Keep the temp database local for quick retrieval, while the main database, used to essentially populate the Ajax calls (used to populate PHP objects) would be on a local, but separate server.

Half the reason I am scratching at this is because a lot of this information is legally sensitive, and I am taking the most secure approach I can really think of. That, and I love thinking out side the box.