 |
SoftTree Technologies
Technical Support Forums
|
|
Author |
Message |
vicki
Joined: 11 Jul 2012 Posts: 2 Country: Hong Kong |
|
DB Audit Degrade Performance? |
|
My DB Audit database got about 40G data after implemeting for a year.
And it is found that database has slow response.
In my concept, DB Audit uses trigger to record INSERT/UPDATE/DELETE, which performance should not be affected by the size of DB Audit database, right?
Or DB Audit trigger actually do some "select" action before / after inserting audit record?
|
|
Wed Jul 11, 2012 4:40 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
The size of the database is not important for the performance if it is not very fragmented and the database server does not spend a lot of time searching for where to save the new data.
|
|
Wed Jul 11, 2012 8:00 am |
|
 |
vicki
Joined: 11 Jul 2012 Posts: 2 Country: Hong Kong |
|
|
|
So, does the trigger seatch before save?
|
|
Wed Jul 11, 2012 7:19 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
It may read filter definitions, if any filters have been defined. That's all. If filters have been defined reasonable, that read is nothing in terms of performance impact, it should be all cached in memory
|
|
Wed Jul 11, 2012 8:42 pm |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|