Microsoft distributes Microsoft SQL Server 2008 and Microsoft SQL Server 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 or SQL Server 2008 R2 fix release.
Symptoms
Consider the following scenario:
-
You create a transactional publication in Microsoft SQL Server 2008 or in Microsoft SQL Server 2008 R2.
-
You have an indexed view. You set the ANSI_NULLS property of the index view to TRUE.
-
You add the indexed view to the publication as an article. You set the article type to "indexed view logbased."
Note You can use the following code to specify the indexed view type. Do this when you run the sp_addarticle stored procedure to add the indexed view article to the publication.@type = N'indexed view logbased'
-
You create a subscription for the transactional publication.
-
The indexed view is replicated to the subscription database.
In this scenario, the ANSI_NULLS property of the indexed view is changed to FALSE in the subscription database.
Notes
-
This issue typically occurs when the ANSI_NULLS property of the tables that are involved in the SQL expression structure of the index view is set to FALSE.
-
This issue also exists in Microsoft SQL Server 2005.
Cause
This issue occurs because tables, views, functions, and stored procedures in SQL Server 2008 share the same storage bit for the ANSI_NULL property. Therefore, if the ANSI_NULLS property of one of tables that are involved in the SQL expression structure of the indexed view is set to FALSE, the default ANSI_NULLS property for the indexed view would be FALSE.
Resolution
Cumulative update information
SQL Server 2008 Service Pack 1
The fix for this issue was first released in Cumulative Update 10 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2279604 Cumulative update package 10 for SQL Server 2008 Service Pack 1Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
SQL Server 2008 Service Pack 2
The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2289254 Cumulative update 1 for SQL Server 2008 Service Pack 2Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released
SQL Server 2008 R2
The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2345451 Cumulative Update package 4 for SQL Server 2008 R2 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
Workaround
To work around this issue, update the metadata cache after the indexed view is created, and before sp_addarticle is run to add the indexed view article.
Notes To update the metadata cache, use one of the following methods:
-
Stop the SQL Server service, and then start the service.
-
Set the subscription database to offline, and then set the database to online.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
For more information about the sp_addarticle stored procedure, visit the following Microsoft website:
Introduction to the sp_addarticle (Transact-SQL) stored procedureFor more information about publishing data and database objects, visit the following Microsoft website:
Publishing data and database objectsFor more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499New naming schema for Microsoft SQL Server software update packagesFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
