I'm in the process of applying SP3/CU6 to my systems, I will watch for this. I followed it so please update it with any updates

Hi Dennis,

Would you have the opportunity to upgrade to SQL Server 2014?

It can be the case that a bug was fixed (most of the times, reported also only) on SQL Server 2014/2016/vNext and not on 2012.

If this is not possible, I strongly recommend to send a support incident to SAP so we can forward it to Microsoft.

Kind regards,
Luis

• Hi all,

  Microsoft FPE provide a extended event to catch error 701, FYI.

  to catch the statement that causes the 701 error, please
  use this X-Event Session. Once the error occurred again, send us the generated
  file (you should change the path to the file for your system):<o:p></o:p>

  DROP
  EVENT SESSION [Catch 701 Errors] ON SERVER
  
  GO
  
  CREATE EVENT SESSION [Catch 701 Errors] ON SERVER
  
  ADD EVENT sqlserver.error_reported(
  
  ACTION(package0.callstack,package0.process_id,sqlos.numa_node_id,sqlserver.client_app_name,sqlserver.client_hostname,sqlserver.client_pid,sqlserver.database_name,sqlserver.plan_handle,sqlserver.session_id,sqlserver.session_nt_username,sqlserver.sql_text)
  
  WHERE ([error_number]=(701)))
  
  ADD TARGET package0.event_file(SET
  filename=N'C:\Temp\Catch701Errros.xel',max_rollover_files=(0))
  
  WITH (MAX_MEMORY=4096 KB,EVENT_RETENTION_MODE=ALLOW_SINGLE_EVENT_LOSS,MAX_DISPATCH_LATENCY=30
  SECONDS,MAX_EVENT_SIZE=0
  KB,MEMORY_PARTITION_MODE=NONE,TRACK_CAUSALITY=OFF,STARTUP_STATE=OFF)
  
  GO<o:p></o:p>

  You have to manually start the session once you created it.<o:p></o:p>