Our application interfaces with a partner's application by calling one of their stored procedures. They insist on sprinkling NOLOCK hints throughout their code and this is a long stored procedure. We are intermittently getting bad data and suspect a race condition.
Is there any way, short of manually changing their stored procedure, that we can override their NOLOCK hints when executing it?
Note -- our code making the stored procedure call is a .NET application, in case that gives us any other options.