Well, the instance didn't failover, but it dumped like hell.
SQLErrorlog file stating ".... a lock it does not own .... " which IMO is a symptom for the lock manager to be fairly messed up.
Serializable transactions keep locks from their beginning untill commit or rollback, causing more overhead to the lock manager.
Maybe this points to a bug, but more important, it points to use another way of handling this kind of logging.
I didn't file the bug at MS, because the workaround is actualy the way to do it.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me