Apologies if I'm posting to the wrong place - I'm a newbie to this! I have an asp classic application which allows users to update records in a database. The database is constantly being replicated to using transactional replication from another database - generally this works fine however at busy times of the day users occasionally find that the asp pages gives them a timeout error - this persists for a few minutes and is then ok again. I am almost certain that this is due to locks by replication. I am uncertain how replication locks records and whether we can specify that it only locks to record level as opposed to page/table etc. It is unlikely that the record being updated is one thats currently being updated by replication so I'm guessing that replication locks pages? I could extend the timeout period on the asp application however as the record appears to be locked for a several minutes I dont want the application hanging around that long. Any advice would be gratefully received.