Reminds me of when I had just joined a new group, they gave me access to some DBs and asked me to "see what I could see". (I had worked with the group while working for another group and they had liked the answers I came up with there.) I printed the schemas for one of the DBs, was going through it, and I suddenly was laughing. I'm reading SQL schema, and I'm laughing. That was a new experience for me. Why was I laughing? I had seen normalization rules mashed, kicked around, and tromped on before. They could all be explained away by either ignorance or studied/justified exception to the rule applications. I had never encountered a table that violated every normalization rule I could think of and throw in some best practice violations to boot. The only explanation that made sense was that the developer knew the rules so he could violate so many all in one place. That was what tickled my funny bone. That couldn't have been an accident, somebody went out of their way to violate every rule they could think of. Well, the joke was on me. I took the schema to my manager so he could share in the joke. He asked me to forward this schema to his manager. I picked the last of 31 tables, put "Interesting Schema" in the E-mail title, sent it to his manager and CC'd mine. Forgot about it. A couple of weeks later, I got a call from a livid manager. To be honest, he had a right to be livid and since he couldn't do a thing about the person he should be mad at, I let him holler at me since I started the ball rolling. I was really thankful that I didn't report to him, because if I had, I think he would have fired me. Seems my manager's manager had a meeting of managers and sprang this table in the meeting as an example of really poor SQL design. Personally, that still should have happened, but after the manager was told ahead of time what was going to happen to him. He's telling me how valuable these tables are and are currently being used. I'm thinking maybe on your databases, but how valuable are 31 tables dated from December 1 through the 31'st of last year to what is going on now in July? (One of the normalization rules is to not put data in a table name. When I read that, I thought, who would be dumb enough to do that? I hadn't yet run into several thousand log tables dated to the millisecond for 6 months of data.)