Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

How can I use a database event Expand / Collapse
Posted Sunday, December 6, 2009 11:45 AM


Group: General Forum Members
Last Login: Tuesday, January 20, 2015 4:08 AM
Points: 16, Visits: 123

Apologies if I'm posting in the wrong place - but this seemed the closest.

What I've done.....

When a loading process is finished, it updates the final stage status of a record to Completed.
I've put in a place a trigger which then inserts a row into another database on this status change
This then fires off 3 triggers to perform certain subsequent activity - in effect 3 procedures.

The issue I have it that this is all part of the original transaction. (In this case, if the two databases were out of sync, I'm not bothered, I have a recovery mechanism.) My concern, is that whilst the 3 triggered procedures are running on Database B, I could be holding locks on the original database.

Ideally, if using Ingres. I would write the three procedures to register for a Database event 'File Completed'. The trigger on the Database Insert table would raise the event 'File Completed' with the associated ID, and the original transaction would commit.

I think a similar thing could be done in Oracle wih Advanced Queueing.

I thought I might be able to use this solution with SQL Server - but it seems to be only DDL. Does anyone have any elegant solutions?


Post #829546
Posted Sunday, December 6, 2009 8:06 PM



Group: General Forum Members
Last Login: Today @ 8:45 AM
Points: 42,066, Visits: 39,447
If you consider the way you'd do it in Ingres "elegant", then why not just do it that way? Write the 3 stored procedures.

--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

Helpful Links:
How to post code problems
How to post performance problems
Post #829604
Posted Sunday, December 6, 2009 9:39 PM



Group: Administrators
Last Login: Today @ 12:17 PM
Points: 34,363, Visits: 18,583
I don't think there's a more elegant way. You could use the DTC (distributed transaction coordinator), but it would hold locks until things were committed, and if your link was down, you couldn't commit anything.

The slightly more elegant way in SQL is to use Service Broker to Q the event and have it picked up by the other database and take action there. that way if there were some comm issue, you could still commit the event in the first database/table and when things were working, it would occur in the second one. That leaves you some loose coupling, but the chance that things are out of sync for some time.

Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #829632
Posted Monday, December 7, 2009 7:02 AM



Group: General Forum Members
Last Login: Yesterday @ 7:36 AM
Points: 10,808, Visits: 14,832
I agree with Steve that Service Broker is probably a way to do what you are looking at doing.

Jack Corbett

Applications Developer

Don't let the good be the enemy of the best. -- Paul Fleming
At best you can say that one job may be more secure than another, but total job security is an illusion. -- Rod at work

Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
How to Post Performance Problems
Crosstabs and Pivots or How to turn rows into columns Part 1
Crosstabs and Pivots or How to turn rows into columns Part 2
Post #829826
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse