Re: Getting lots of DB Errors: Transaction was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Index on sessionid will help immensely with that many rows. Ultimately, I would suggest never using a Guid as a primary key, performance is going to be less than ideal, even with an index. Byron Mann Lead Engineer Architect HostMySite.com On Jul 16, 2013 1:02 PM, Brook Davies

re: Getting lots of DB Errors: Transaction was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Absolutely you should have an index on sessionID. Without that index you are forcing a table scan for that id so the engine can do the update. When your table was smaller, SQL could deal with that a lot easier. Once you start getting to 3-4 million rows, the performance starts to slow down

RE: Getting lots of DB Errors: Transaction was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Thanks Jeff and Byron! -Original Message- From: Jeff Garza [mailto:j...@garzasixpack.com] Sent: July-16-13 10:38 AM To: cf-talk Subject: re: Getting lots of DB Errors: Transaction was deadlocked on lock | communication buffer resources with another process and has been chosen as the