Yes. SQL Server occasionally loses it's mind on such things. Over the last 16 years of using SQL Server, I've given up on trying to find the reasons. It appears to be because of spurious pips on the network when you have a waxing moon with the correct angular displacement to certain sunspots and the Red Wings are playing a home game on a rainy day but only during high tide and the coffee machine across the room is cycled. :-D
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs