BUG: SP_DBOPTION May Not Set the Database ANSI_NULL_DEFAULT Option When You Use Turkish Collation (298564)

SYMPTOMS

An attempt to set the ANSI NULL DEFAULT database option by using SQL Enterprise Manager (SEM) or the sp_dboption stored procedure on a computer that is running SQL Server with a SQL Server Turkish collation or Microsoft Windows Turkish Collation may not succeed.

An example of such a collation for SQL Server is:

SQL_Latin1_General_CP1254_CI_AS

An example of such a collation for Windows collation:

Turkish_BIN for SQL collation

From the SQL Server Query Analyzer, you see the following message, but the option does not change:

The command(s) completed successfully.

WORKAROUND

To work around this problem, use the ALTER DATABASE Transact-SQL command to set the ANSI_NULL_DEFAULT option.

For example, in the Northwind database, execute the following statement from Query Analyzer:

ALTER DATABASE Northwind SET ANSI_NULL_DEFAULT ON

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

SQL Server 2000 Books Online includes the following text in the sp_dboption topic:

"sp_dboption is supported for backward compatibility. Use ALTER DATABASE to set database options."