We are getting strange corrupt index error messages mostly in a function called from the SELECT field list of a query. I know it is a "no no" performance wise to call user defined functions within a SELECT field list, but this is long running / existing code doing this. When a user receives this error, every single time so far, they are able to simply re-run that same code without the error. So these corrupt index errors seem to be happening only momentarily / seem to Not be actual true index corruption issues.
I have read a lot about how SMB2 running in a Windows 7 and Windows 2008 Server environment can cause index corruption. So my 1st question is, could SMB2 also be the cause of my above described 'momentary' index corruption?
My 2nd question, if we did turn off SMB2, would this adversely affect MS SQL Server 2008 (running on that same Windows 2008 Server)?
I have read a lot about how SMB2 running in a Windows 7 and Windows 2008 Server environment can cause index corruption. So my 1st question is, could SMB2 also be the cause of my above described 'momentary' index corruption?
My 2nd question, if we did turn off SMB2, would this adversely affect MS SQL Server 2008 (running on that same Windows 2008 Server)?