February 12, 2008 at 2:48 pm
This was a well done and much appreciated column.
You are quite correct in pointing out that indexed views can add complexity in requiring things such as ANSI_Nulls, ANSI_WARNINGS, etc, but where they are already implemented they are a cleaner solution than adding computed indexed columns in that they separate the calculations from the table which stores the raw data. Both can be good options though.
---
Timothy A Wiseman
SQL Blog: http://timothyawiseman.wordpress.com/
February 14, 2008 at 3:40 am
The database SET options for indexing a computed column and creating an indexed view are exactly the same.
Easy fix - just set your default server SET options and then all your connections, no matter what makes them (OLEDB, ODBC, DB-LIB, ADO.NET, etc) will be able to work with your indexed computed columns and views.
The post earlier about computed columns working in 2000 and then not in 2005 is easily solved this way. I think the stored proc call is to
sp_configure 'server options', 376
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply