Actually I am Developing a Database Auditing Infrastructure. I am working in SQL Server 2005.
So my main focus of area is "SQL Triggers" and "stored Procedures". I ask for help on CLR routine i thought it would help me.
Anything dealing with data is probably better written in T-SQL than CLR, unless you have a good reason to need the CLR
If you can me some other suggestion. I would be thankful to you.
Secondly can you suggest me a way that is there any possibility of writing Generalized DML triggers on all tables of database or not ???
It is possible, but I would strongly recommend against it. Generic triggers tend to perform poorly, leading to slow data changes, deadlocks and all other such unpleasant things.
What I've done in the past is to have a stored procedure that can, using dynamic SQL, create triggers on all tables. That way you only have to write the code once, but the triggers are specific to their tables and hence reasonably fast.
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass