When profiling our Microsoft Dynamics NAV application with SQL Server Profiler, I get INSERTs with the REPEATABLEREAD hint.
What effect does the REPEATABLEREAD hint has on an INSERT statement?
In SQL Server 2012 - How does "Repeatable Read" isolation level work? the REPEATABLEREAD hint is described, but this seems to apply to SELECTs only.
Extra info:
- Not all INSERTs have the
REPEATABLEREADhint, so maybe Microsoft Dynamics NAV application issues the hint under specific circumstances. - The INSERTs are simple INSERT statement (no SELECT INTO or JOINs). The execution plan also shows a simple INSERT
REPEATABLEREADhint "Specifies that a scan is performed with the same locking semantics as a transaction running at REPEATABLE READ isolation level. For more information about isolation levels, see SET TRANSACTION ISOLATION LEVEL (Transact-SQL)." So, if theINSERTmust scan indexes to check for dupes etc. - maybe that's what it means