Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
wlho
Starting Member
3 Posts |
 Posted - 2003-05-06 : 21:57:40
|
| hi...i have a replication case which is always get deadlock...actually i replicating table A from SQL Server to table A at IBM DB2 at AIX Server.at the DB2 table A, i have a trigger insert the particular record key to another table which is table B to avoid having duplicate record,then at the table B, i have another trigger to broadcast the data out to client on screen....but i always get deadlock from DB2 when SQL replicate a lot datas...iz there anyway for me to set the deadlock time for SQL Server???or can the SQL server automatic rereplicate by ifself??? |
|
|
KnooKie
Aged Yak Warrior
623 Posts |
Posted - 2003-05-07 : 06:10:07
|
| Tricky to work out what you're trying to do here but it sounds rather odd.I'm not sure what you are trying to achieve with your INSERT trigger to table B, where would this duplicate record be coming from ? Why are you inserting the record key ? How does this help you ?SQL Server can automatically replicate at any intervals you wish.Maybe i'm missing something here !?====Paul |
 |
|
|
wlho
Starting Member
3 Posts |
Posted - 2003-05-07 : 06:45:21
|
| actually my system iz an alert system. whenever there iz update in the SLQ Server, the data need to replicate to AIX DB2. then i create trigger for the tablesin DB2 to insert the message key into another table to avoid duplication alert out...at the table there, i also have a trigger to send the message out to client screen. after i send the message out, i have to delete from the table so tat i can accept new message...i also not very sure there actually i get deadlock, but DB2 always pass error code 911 to SQL Server, error code 911 iz equal to Deadlock... |
|
|
|
KnooKie
Aged Yak Warrior
623 Posts |
Posted - 2003-05-07 : 07:38:07
|
| You can monitor locking activity on the SQL Server side of things by viewing the activity Monitor in Enterprise manager. When a deadlock occurs you should be able to see where/what/why by looking there.You may also be able to use the SQL Server profiler to monitor exactly what is being done to isolate your problem.If the problem is occurring on the DB2 side then this may not be the best place to post being a SQL Server site.====Paul |
|
|
|
wlho
Starting Member
3 Posts |
Posted - 2003-05-07 : 07:56:52
|
| actually i replication from SQL Server to DB2... DB2 always return error code 911 means deadlock...so, i wana know iz there any setting to set the SQL Server replication restart automatically after getting error... |
|
|
|
|
|
|
get Deadlock for replication...