Thanks for response. It is now working fine. But, I have a question.

Now in msdn sites for sp_trace_setevent / sp_trace_setfilter / sp_trace_setstatus , I see the following WARNING message.

/*

This feature...

Yeah i think there some confusion went..Anyways as you said server tracing gives what are all things happeining on the client...we actually not required old values of data of what...

Simple method is to have server side tracing using TSQL..Let me know how this code is...

--Server Side tracing

declare @rc int

declare @TraceID int

declare @maxfilesize bigint

set @maxfilesize = 2

-- Please...

CDC captures only insert,update,delete on tables..but I don't think it captures drop,truncate,select ...Also in order to create that we need sql agent which on back ground runs the jobs..It requires...

ya that's correct..How about working on Server side scripting...instead of setting sql profile setup on another server?/

I am following the same way as in script..but receiving the folowing error on Step 2:

Must declare the scalar variable "@TraceID".

Any suggestions..do we need to declare any traceid value

Ya, I am not implementing any spcific logic..here is the way i am doing..

CREATE TABLE LOG_TABLE (Add_dttm datetime DEFAULT (GetDate()), TABLE_NAME sysname, Activity char(6),login_sname sysname DEFAULT SUSER_SNAME())

GO

DECLARE @sql...

If you do not have enterprise edition, to enable TDE then Secure the folder on the local drive with password.

Any updates by anyone would be helpful...

Ok, this is the way I am implementing auditing : SCHEMA LEVEL AUDITING

CREATE DATABASE AUDIT SPECIFICATION Example2

FOR SERVER AUDIT ADEVNTUREWORKSAudit

ADD (INSERT,UPDATE,DELETE,SELECT

ON SCHEMA::dbo

...

All the table level changes(insert,update,delete,select).

Well I have a Scenario: We have users who requires db_datareader and db_datawriter permissions to run there front end applications. We are using windows authentication as access permissions. Now...

Thanks mike..

performance testing(load)

To just make sure of log space is not running.out of space...and database is functioning as is....