SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 General SQL Server Forums
 New to SQL Server Administration
 Replication DB - Dead lock issue - Sql server 2005
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

poratips
Posting Yak Master

104 Posts

Posted - 06/30/2013 :  00:26:39  Show Profile  Reply with Quote
Hi,
We have One Database which is a Replication Db, sometimes during beginning of the month, lot of user activities going and we having Dead lock issue.
Any one has idea how to prevent the dead lock in Replication DB?
We have to manually kill the user session one by one but if someone having same kind of issue and have any idea?


Thanks,

poratips
Posting Yak Master

104 Posts

Posted - 07/01/2013 :  10:13:22  Show Profile  Reply with Quote
Any help, please?
Go to Top of Page

Hommer
Aged Yak Warrior

784 Posts

Posted - 07/01/2013 :  15:20:15  Show Profile  Reply with Quote
I think you have performance issue instead of replication issue.

Replication may add to the server load and throughput, but trying to fix dead lock from replication's prospective is a long shot.

quote:
Originally posted by poratips

Any help, please?

Go to Top of Page

poratips
Posting Yak Master

104 Posts

Posted - 07/05/2013 :  10:11:04  Show Profile  Reply with Quote
Thanks Hommer.
Actually what happening as when during begining of the month replication DB runs and updaing/Inserting into lots of tables and that activities are heavy and during that time our other activities also running so user process hot hung or they have to wait for longer period of time and all the processes becomeing too slow..
We have Transaction Replication DB and we are subscriber and publisher is 3rd party.
Looking into more depth, it's not showing as a blocking or Deadlock but user processes are waiting for longer period and it's too much for other process.
Appreciate your inputs.

Thanks.
Go to Top of Page

russell
Pyro-ma-ni-yak

USA
5072 Posts

Posted - 07/09/2013 :  10:41:18  Show Profile  Visit russell's Homepage  Reply with Quote
You need to examine the queries/execution plans for the requests that are timing out.
Go to Top of Page

poratips
Posting Yak Master

104 Posts

Posted - 07/10/2013 :  08:11:40  Show Profile  Reply with Quote
Thanks Russell.
It's happening with many users and after that it's not that much waiting, any other needs to be observed?
Go to Top of Page

russell
Pyro-ma-ni-yak

USA
5072 Posts

Posted - 07/10/2013 :  11:58:45  Show Profile  Visit russell's Homepage  Reply with Quote
You're running transactional replication and only synching monthly?

Why? And how long is the synchronization taking? You need to schedule it for off-peak hours if this is what you're doing.

Or synch much more often. Or use a different method of synching.
Go to Top of Page

poratips
Posting Yak Master

104 Posts

Posted - 07/15/2013 :  08:18:27  Show Profile  Reply with Quote
It's a Transactional Replication and running every few minutes as we are only subscriber.
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.12 seconds. Powered By: Snitz Forums 2000