Microsoft has posted a new article that details a SQL Server 2000 Service Pack 1 (SP1) bug. The article explains that executing a SELECT statement that has a nested query on a table that contains a computed column might generate the following Access Violation:
ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 61 generated fatal exception
c0000005 EXCEPTION_ACCESS_VIOLATION.
SQL Server is terminating this process.
Connection Broken
To avoid this problem, the article recommends that you place the computed column's value into a variable, then use that variable in the SELECT list. However, the article also notes that good database design typically avoids storing computed columns in a table; performing the computations through queries is a better practice. For more information about this problem, see the Microsoft article, "BUG: SP1 Regression: SELECT Query on a Table with a Computed Column Generates Access Violation."
