Hi all. We have a huge table tat we insert records from another huge table into and we have a START VIOLATIONS facility set up on the target table and I am wondering how this (if it does) affects our performance? Based on everyones experience, is this a major source of oevrhead? Just wondering if this insert would run faster sans the violations and diagnostics stuff.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
START VIOLATIONS performance
- Thread starter noober
- Start date
Hi,
In my viewpoint, violations facility should not be continued for a prolonged period, than what it is really meant for. Once your purpose is over or done with, you may promptly remove the violations tracings.
Violations tracing facility absorb or drain certain amount of resources from the engine to get the mechanism going. This extra service that you require from your database server, is always with a pinch, and it would have negative impact on the performance especially with the insert operation.
Regards,
Shriyan
In my viewpoint, violations facility should not be continued for a prolonged period, than what it is really meant for. Once your purpose is over or done with, you may promptly remove the violations tracings.
Violations tracing facility absorb or drain certain amount of resources from the engine to get the mechanism going. This extra service that you require from your database server, is always with a pinch, and it would have negative impact on the performance especially with the insert operation.
Regards,
Shriyan
- Status