Audit Data

Hi all,
I would just like to ask whats the best way to make some audit on some of the tables in a MS SQL server, what i'm planning to have is to have a table which can contain all changes/inserts/deletion of some given tables, my first idea was to have this:

AuditTable that have the following fields:
AuditID, TableName, FieldName, OldValue, NewValue, UpdateBy, UpdateDate

then in all the given tables, i'll have insert, update and delete trigger, the issue comes down to the trigger, what will be the best way to have that trigger written in a way that it can be use for other tables as well? say if a table have more then 20 fields, I don't want to declare 20 var and compare them 1 by1, and if there is a diff, then i insert to the audittable, I want something that it can loop and (if possible) be able to use by other table as well, so the field name etc can get from sysobjects, but then how can you code it in a way that it can do that?

Or is there any better way to get the same result? currently i have an audit table for each table i want to audit on and its just wasting space, any help will be great.
Thanks,What do you need this for?|||One method is to use the Binary_Checksum() function across both the original record and the updated record. If the values returned are different, then the record has changed and you should copy the original into your archive table.|||Does that mean i need to check every single field? that will take a while isn't it? is there any better way? how do you guys do your audit?

The reason I need this for is to keep a log on who did what on when on selected tables in a given DB, where sometimes ppl will ask things like who delete this record, or who update that record etc, and i can't just keep the last update as they need to chase back who did updates, for example PersonA update 2 times and PersonB comes in and update 3 times then PersonD delete that record...i need to keep track of all these info.|||There are many off-the-shelf packages that will give you this functionality. Download the eval and see how it is done. Most likely it all bottles down to C2-based auditing trace.|||I ran across this the other day. The VB package builds a shadow audit table (per auditied table) and builds the triggers for insert, update and delete. Also has paramaters which build SP's to trim the audit records or restore from the audit table.

http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=e94eb930-1f8d-4e9a-be65-38313ce31166|||I think you are going to have problems with audit table design:

"AuditTable that have the following fields:
AuditID, TableName, FieldName, OldValue, NewValue, UpdateBy, UpdateDate"

I suspect you will find it very difficult to manage or retrieve usefull information from a single audit table that covers all the tables in your database, though at first glance that may appear to be the simplest solution. You will find that writing queries against this to track changes or restore lost data will be quite cumbersome.

A more common approach is to create a copy of each of the tables you want to archive, perhaps with "_HIST" appended to the name and with your Update time columns included as well. Then just have an update trigger on your production tables that copies the entire record to its history table.

Even though you are increasing the number of tables, you will find this method much easier to use.

Attaching SQL Server 2000 database on SQL Serve 2005

Hello!
We are planning to migrate our multi terabyte SQL Server 2000 database
by detaching data/log files on 2000 box and reattaching them on 2005. Has
anyone experienced any issues with this process in general and databases of
such size in particular? As far as I know, SQL Server will perform database
conversion when attaching database on SQL 2005.
Any thoughts are greatly appreciated,
IgorThis is a simple test,with a database names 'test' which on sqlserver 2000.
first:
Stop the database's servers(2000) on machine.
second:
Execute the command on 2005 server:
exec sp_attach_db @.dbname = N'test',
@.filename1 = N'd:\sqlserver database\MSSQL\data\test_Data.MDF',
@.filename2 = N'd:\sqlserver database\MSSQL\data\test_Log.LDF'
ok.So easy.And the server will return a message:'Converting database 'test'
from version 539 to the current version 607.'
"imarchenko" wrote:

> Hello!
> We are planning to migrate our multi terabyte SQL Server 2000 database
> by detaching data/log files on 2000 box and reattaching them on 2005. Has
> anyone experienced any issues with this process in general and databases o
f
> such size in particular? As far as I know, SQL Server will perform databas
e
> conversion when attaching database on SQL 2005.
>
> Any thoughts are greatly appreciated,
> Igor
>
>|||you should copy the datafile to a specifically catalog 。And use new files
to
attach.Otherwise 2000 server's 'test' database will disappear
"luyan" wrote:
[vbcol=seagreen]
> This is a simple test,with a database names 'test' which on sqlserver 2000
.
> first:
> Stop the database's servers(2000) on machine.
> second:
> Execute the command on 2005 server:
> exec sp_attach_db @.dbname = N'test',
> @.filename1 = N'd:\sqlserver database\MSSQL\data\test_Data.MDF',
> @.filename2 = N'd:\sqlserver database\MSSQL\data\test_Log.LDF'
> ok.So easy.And the server will return a message:'Converting database 'test
'
> from version 539 to the current version 607.'
> "imarchenko" wrote:
>|||luyan,
Thanks for you reply. I do know how to detach/attach database. My
question is whether anyone has experienced any problems while attaching
terabyte databases.
Thanks,
Igor
"luyan" <luyan@.discussions.microsoft.com> wrote in message
news:051EBA51-A12E-4E42-A07B-94B5D588DA72@.microsoft.com...[vbcol=seagreen]
> you should copy the datafile to a specifically catalog ?And use new files
> to
> attach.Otherwise 2000 server's 'test' database will disappear
> "luyan" wrote:
>|||It may take a long time. I did restore a 500 MB SQL 2000 DB to SQL 2005 and
it took about 10 minutes on SAN system. In your situation you have to
consider this issue.
Bill
"imarchenko" wrote:

> Hello!
> We are planning to migrate our multi terabyte SQL Server 2000 database
> by detaching data/log files on 2000 box and reattaching them on 2005. Has
> anyone experienced any issues with this process in general and databases o
f
> such size in particular? As far as I know, SQL Server will perform databas
e
> conversion when attaching database on SQL 2005.
>
> Any thoughts are greatly appreciated,
> Igor
>
>|||Bill,
Thanks for you feedback.
Igor
"Bill Wang" <BillWang@.discussions.microsoft.com> wrote in message
news:D23E2D1B-DAA2-4FA2-A5CA-E253DC148BED@.microsoft.com...[vbcol=seagreen]
> It may take a long time. I did restore a 500 MB SQL 2000 DB to SQL 2005
> and
> it took about 10 minutes on SAN system. In your situation you have to
> consider this issue.
> Bill
> "imarchenko" wrote:
>

Attaching SQL Server 2000 database on SQL Serve 2005

Hello!
We are planning to migrate our multi terabyte SQL Server 2000 database
by detaching data/log files on 2000 box and reattaching them on 2005. Has
anyone experienced any issues with this process in general and databases of
such size in particular? As far as I know, SQL Server will perform database
conversion when attaching database on SQL 2005.
Any thoughts are greatly appreciated,
IgorThis is a simple test,with a database names 'test' which on sqlserver 2000.
first:
Stop the database's servers(2000) on machine.
second:
Execute the command on 2005 server:
exec sp_attach_db @.dbname = N'test',
@.filename1 = N'd:\sqlserver database\MSSQL\data\test_Data.MDF',
@.filename2 = N'd:\sqlserver database\MSSQL\data\test_Log.LDF'
ok.So easy.And the server will return a message:'Converting database 'test'
from version 539 to the current version 607.'
"imarchenko" wrote:
> Hello!
> We are planning to migrate our multi terabyte SQL Server 2000 database
> by detaching data/log files on 2000 box and reattaching them on 2005. Has
> anyone experienced any issues with this process in general and databases of
> such size in particular? As far as I know, SQL Server will perform database
> conversion when attaching database on SQL 2005.
>
> Any thoughts are greatly appreciated,
> Igor
>
>|||you should copy the datafile to a specifically catalog ã'And use new files to
attach.Otherwise 2000 server's 'test' database will disappear
"luyan" wrote:
> This is a simple test,with a database names 'test' which on sqlserver 2000.
> first:
> Stop the database's servers(2000) on machine.
> second:
> Execute the command on 2005 server:
> exec sp_attach_db @.dbname = N'test',
> @.filename1 = N'd:\sqlserver database\MSSQL\data\test_Data.MDF',
> @.filename2 = N'd:\sqlserver database\MSSQL\data\test_Log.LDF'
> ok.So easy.And the server will return a message:'Converting database 'test'
> from version 539 to the current version 607.'
> "imarchenko" wrote:
> > Hello!
> >
> > We are planning to migrate our multi terabyte SQL Server 2000 database
> > by detaching data/log files on 2000 box and reattaching them on 2005. Has
> > anyone experienced any issues with this process in general and databases of
> > such size in particular? As far as I know, SQL Server will perform database
> > conversion when attaching database on SQL 2005.
> >
> >
> > Any thoughts are greatly appreciated,
> > Igor
> >
> >
> >|||luyan,
Thanks for you reply. I do know how to detach/attach database. My
question is whether anyone has experienced any problems while attaching
terabyte databases.
Thanks,
Igor
"luyan" <luyan@.discussions.microsoft.com> wrote in message
news:051EBA51-A12E-4E42-A07B-94B5D588DA72@.microsoft.com...
> you should copy the datafile to a specifically catalog ?And use new files
> to
> attach.Otherwise 2000 server's 'test' database will disappear
> "luyan" wrote:
>> This is a simple test,with a database names 'test' which on sqlserver
>> 2000.
>> first:
>> Stop the database's servers(2000) on machine.
>> second:
>> Execute the command on 2005 server:
>> exec sp_attach_db @.dbname = N'test',
>> @.filename1 = N'd:\sqlserver database\MSSQL\data\test_Data.MDF',
>> @.filename2 = N'd:\sqlserver database\MSSQL\data\test_Log.LDF'
>> ok.So easy.And the server will return a message:'Converting database
>> 'test'
>> from version 539 to the current version 607.'
>> "imarchenko" wrote:
>> > Hello!
>> >
>> > We are planning to migrate our multi terabyte SQL Server 2000
>> > database
>> > by detaching data/log files on 2000 box and reattaching them on 2005.
>> > Has
>> > anyone experienced any issues with this process in general and
>> > databases of
>> > such size in particular? As far as I know, SQL Server will perform
>> > database
>> > conversion when attaching database on SQL 2005.
>> >
>> >
>> > Any thoughts are greatly appreciated,
>> > Igor
>> >
>> >
>> >|||It may take a long time. I did restore a 500 MB SQL 2000 DB to SQL 2005 and
it took about 10 minutes on SAN system. In your situation you have to
consider this issue.
Bill
"imarchenko" wrote:
> Hello!
> We are planning to migrate our multi terabyte SQL Server 2000 database
> by detaching data/log files on 2000 box and reattaching them on 2005. Has
> anyone experienced any issues with this process in general and databases of
> such size in particular? As far as I know, SQL Server will perform database
> conversion when attaching database on SQL 2005.
>
> Any thoughts are greatly appreciated,
> Igor
>
>|||Bill,
Thanks for you feedback.
Igor
"Bill Wang" <BillWang@.discussions.microsoft.com> wrote in message
news:D23E2D1B-DAA2-4FA2-A5CA-E253DC148BED@.microsoft.com...
> It may take a long time. I did restore a 500 MB SQL 2000 DB to SQL 2005
> and
> it took about 10 minutes on SAN system. In your situation you have to
> consider this issue.
> Bill
> "imarchenko" wrote:
>> Hello!
>> We are planning to migrate our multi terabyte SQL Server 2000
>> database
>> by detaching data/log files on 2000 box and reattaching them on 2005. Has
>> anyone experienced any issues with this process in general and databases
>> of
>> such size in particular? As far as I know, SQL Server will perform
>> database
>> conversion when attaching database on SQL 2005.
>>
>> Any thoughts are greatly appreciated,
>> Igor
>>

Attaching SQL Server 2000 database on SQL Serve 2005

Hello!
We are planning to migrate our multi terabyte SQL Server 2000 database
by detaching data/log files on 2000 box and reattaching them on 2005. Has
anyone experienced any issues with this process in general and databases of
such size in particular? As far as I know, SQL Server will perform database
conversion when attaching database on SQL 2005.
Any thoughts are greatly appreciated,
Igor
This is a simple test,with a database names 'test' which on sqlserver 2000.
first:
Stop the database's servers(2000) on machine.
second:
Execute the command on 2005 server:
exec sp_attach_db @.dbname = N'test',
@.filename1 = N'd:\sqlserver database\MSSQL\data\test_Data.MDF',
@.filename2 = N'd:\sqlserver database\MSSQL\data\test_Log.LDF'
ok.So easy.And the server will return a message:'Converting database 'test'
from version 539 to the current version 607.'
"imarchenko" wrote:

> Hello!
> We are planning to migrate our multi terabyte SQL Server 2000 database
> by detaching data/log files on 2000 box and reattaching them on 2005. Has
> anyone experienced any issues with this process in general and databases of
> such size in particular? As far as I know, SQL Server will perform database
> conversion when attaching database on SQL 2005.
>
> Any thoughts are greatly appreciated,
> Igor
>
>
|||you should copy the datafile to a specifically catalog 。And use new files to
attach.Otherwise 2000 server's 'test' database will disappear
"luyan" wrote:
[vbcol=seagreen]
> This is a simple test,with a database names 'test' which on sqlserver 2000.
> first:
> Stop the database's servers(2000) on machine.
> second:
> Execute the command on 2005 server:
> exec sp_attach_db @.dbname = N'test',
> @.filename1 = N'd:\sqlserver database\MSSQL\data\test_Data.MDF',
> @.filename2 = N'd:\sqlserver database\MSSQL\data\test_Log.LDF'
> ok.So easy.And the server will return a message:'Converting database 'test'
> from version 539 to the current version 607.'
> "imarchenko" wrote:
|||luyan,
Thanks for you reply. I do know how to detach/attach database. My
question is whether anyone has experienced any problems while attaching
terabyte databases.
Thanks,
Igor
"luyan" <luyan@.discussions.microsoft.com> wrote in message
news:051EBA51-A12E-4E42-A07B-94B5D588DA72@.microsoft.com...[vbcol=seagreen]
> you should copy the datafile to a specifically catalog ?And use new files
> to
> attach.Otherwise 2000 server's 'test' database will disappear
> "luyan" wrote:
|||It may take a long time. I did restore a 500 MB SQL 2000 DB to SQL 2005 and
it took about 10 minutes on SAN system. In your situation you have to
consider this issue.
Bill
"imarchenko" wrote:

> Hello!
> We are planning to migrate our multi terabyte SQL Server 2000 database
> by detaching data/log files on 2000 box and reattaching them on 2005. Has
> anyone experienced any issues with this process in general and databases of
> such size in particular? As far as I know, SQL Server will perform database
> conversion when attaching database on SQL 2005.
>
> Any thoughts are greatly appreciated,
> Igor
>
>
|||Bill,
Thanks for you feedback.
Igor
"Bill Wang" <BillWang@.discussions.microsoft.com> wrote in message
news:D23E2D1B-DAA2-4FA2-A5CA-E253DC148BED@.microsoft.com...[vbcol=seagreen]
> It may take a long time. I did restore a 500 MB SQL 2000 DB to SQL 2005
> and
> it took about 10 minutes on SAN system. In your situation you have to
> consider this issue.
> Bill
> "imarchenko" wrote: