We had a user yesterday that ran a report and their system froze.
i connected and looked and the replication processes is what was blocking. i stopped the synchrnozing, everyone could continue working, then i started the synch and everything was fine.
This is SQL 2005, merge replication.
The report is driven by a SELECT that has a user defined function that also only does SELECTs, and the report query takes about 30 minutes to run.
Does a SELECT lock a record in a table while it is reading it? If so, i don't want a SELECT to lock anything, but i also don't want the SELECT to read dirty records (NOLOCK/REUNCOMMITED).
This might not be enough information to start with, but i am trying to figure out if the report query is what caused the replication to cause blocking - somehow - and if so what can i do to stop a SELECT statement from locking records.
View Complete Post