Re: Database design question - Isolated, unrelated tables

On Mon, 25 Jun 2007 18:08:15 -0700, nyathancha_at_hotmail.com wrote:

(snip)
> I think
>there is a system table somewhere in sql server that logs all the
>transactions and changes that happen in the table right?

Hi nyathancha,

Wrong. SQL Server has a log file that it uses internally for rolling transactions back, or rolling forward after an unexpected shutdown. The format is not documented, though there are some third-party tool vendors that claim their tools can read it. Even more important, the log file can be cleaned for various reasons. This file isn't intended to be used for auditing at all.

(snip)
> The resolution of the reporting and
>entries hasn't been decided yet

But you (or rahter, "they") do want SOME form of reporting on the data, right? In that case, you need to model it appropriately - find out what attributes need to be stored, normalize down to a proper table design, then implement.

Any idea of generating reports on a generic "catch-all" table design such as what you're proposing will turn into a nightmare.

-- 
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis