Oracle Development
 
Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
User Name:
Password:
Remember me

The Shed is going Social! Join us on FaceBook and Twitter and chime in on the conversation.

Go Back   Dev Shed ForumsDatabasesOracle Development

Reply
Add This Thread To:
  Del.icio.us   Digg   Google   Spurl   Blink   Furl   Simpy   Y! MyWeb 
Thread Tools Search this Thread Rate Thread Display Modes
 
Unread Dev Shed Forums Sponsor:
  #1  
Old September 14th, 2012, 10:48 AM
Billabang's Avatar
Billabang Billabang is offline
Contributing User
Dev Shed Newbie (0 - 499 posts)
 
Join Date: Nov 2005
Location: Manchester
Posts: 395 Billabang User rank is Sergeant (500 - 2000 Reputation Level)Billabang User rank is Sergeant (500 - 2000 Reputation Level)Billabang User rank is Sergeant (500 - 2000 Reputation Level)Billabang User rank is Sergeant (500 - 2000 Reputation Level)Billabang User rank is Sergeant (500 - 2000 Reputation Level) 
Time spent in forums: 4 Days 8 h 51 m 55 sec
Reputation Power: 22
Red face Trigger Advice

Hi

I am soon engaging in a project where we will deploy three triggers to each table in a customers live database. One each for Inserts,Updates and deletes.

These triggers write or update a row in a separate table on a different schema.

We have experienced locking issues on these tables previously with SQL Server.

I am simply looking for advice on what to look for if issues occur around performance or locking and anybody else's experience with trigger performance/locking issues on Oracle?

Are there settings we can look at to improve performance?
Any general guidance and advice is much appreciated from anyone who has worked in this kind of area.

Thanks in Advance
__________________
Will Code for Rep!

Reply With Quote
  #2  
Old September 18th, 2012, 09:48 AM
debasisdas's Avatar
debasisdas debasisdas is offline
Humble Learner
Dev Shed Newbie (0 - 499 posts)
 
Join Date: Jul 2007
Location: Bangalore, India
Posts: 279 debasisdas User rank is First Lieutenant (10000 - 20000 Reputation Level)debasisdas User rank is First Lieutenant (10000 - 20000 Reputation Level)debasisdas User rank is First Lieutenant (10000 - 20000 Reputation Level)debasisdas User rank is First Lieutenant (10000 - 20000 Reputation Level)debasisdas User rank is First Lieutenant (10000 - 20000 Reputation Level)debasisdas User rank is First Lieutenant (10000 - 20000 Reputation Level)debasisdas User rank is First Lieutenant (10000 - 20000 Reputation Level)debasisdas User rank is First Lieutenant (10000 - 20000 Reputation Level)  Folding Points: 1142847 Folding Title: Super Ultimate Folder - Level 3Folding Points: 1142847 Folding Title: Super Ultimate Folder - Level 3Folding Points: 1142847 Folding Title: Super Ultimate Folder - Level 3Folding Points: 1142847 Folding Title: Super Ultimate Folder - Level 3Folding Points: 1142847 Folding Title: Super Ultimate Folder - Level 3Folding Points: 1142847 Folding Title: Super Ultimate Folder - Level 3Folding Points: 1142847 Folding Title: Super Ultimate Folder - Level 3Folding Points: 1142847 Folding Title: Super Ultimate Folder - Level 3
Time spent in forums: 2 Months 3 Days 4 h 56 m 45 sec
Reputation Power: 118
Send a message via ICQ to debasisdas Send a message via AIM to debasisdas Send a message via Skype to debasisdas
First of all if you are working on a single source table, you do not need 3 separate triggers. It can be achieved with a single trigger by handling different DB events. and since the triggers write or update a row in a separate table on a different schema, you need to check for the commit mechanism that is implemented, may be through your application. Also you need to verify the dependency of data across multiple tables / schemas or any other existing triggers.

Reply With Quote
  #3  
Old September 18th, 2012, 10:48 AM
Billabang's Avatar
Billabang Billabang is offline
Contributing User
Dev Shed Newbie (0 - 499 posts)
 
Join Date: Nov 2005
Location: Manchester
Posts: 395 Billabang User rank is Sergeant (500 - 2000 Reputation Level)Billabang User rank is Sergeant (500 - 2000 Reputation Level)Billabang User rank is Sergeant (500 - 2000 Reputation Level)Billabang User rank is Sergeant (500 - 2000 Reputation Level)Billabang User rank is Sergeant (500 - 2000 Reputation Level) 
Time spent in forums: 4 Days 8 h 51 m 55 sec
Reputation Power: 22
Thanks for your reply, our application automatically creates the separate triggers so there is no choice there unfortunately. There are hundreds of tables to each have these triggers.

What do you mean regarding checking the commit mechanism?

My main concern is for any performance issues we could hit and not knowing which settings to change if any performance issues did occur. Or locking of the tables for that matter.

Reply With Quote
Reply

Viewing: Dev Shed ForumsDatabasesOracle Development > Trigger Advice

Developer Shed Advertisers and Affiliates



Thread Tools  Search this Thread 
Search this Thread:

Advanced Search
Display Modes  Rate This Thread 
Rate This Thread:


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
View Your Warnings | New Posts | Latest News | Latest Threads | Shoutbox
Forum Jump

Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
  
 


Powered by: vBulletin Version 3.0.5
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.

© 2003-2013 by Developer Shed. All rights reserved. DS Cluster - Follow our Sitemap