When editing an SQL script saved as an external file (as opposed to a stored procedure), SSMS will go to sleep for up to 10 minutes, will finally save the file, but then comes back indicating the file has been changed by another user, and wants to reload it.
This happened sporadically over the last few weeks, but is starting to happen more often.
Attempts to delete the ve-....tmp file in Windows Explorer can an immediate crach of Windows Explorer. This happens as soon as you even click on the file!
What little I can find on the Googalator indicates it may be related to anti-virus software, but to date the issue is only related to SSMS.
Any ideas folks?