Rich Weissler (12/14/2012)
But, okay... I give up, how does having an indexed view cause a loss of precision?
(I.e. Yep, I see the error. I don't understand WHY. :-( )
It doesn't. But there are specific settings required for making and maintaining indexed views, and this happens to be one of them.
If you change the setting before trying to create the view, that in itself would already fail. (Or, to be more precise, creating the view would succeed, but creating the index to convert it from a normal into an indexed view would fail).
The reason for this limitation? (Puts on speculative hat) Many settings are discouraged anyway, and I guess that MS decided not to put in extra engineering effort to support and test indexed views (and several other features with similar limitations) under all those settings. So they simply forbid them.
Hugo Kornelis, SQL Server MVP
Visit my SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis