Operational Defect Database
BugZero found this defect 1308 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 12947202
KB4494805 - FIX: Adding new Publication may fail if distribution database is in AG and collation is set to BIN in SQL Server 2016 and 2017 - Microsoft Support
Last update date:
6/2/2022
Affected products:
SQL Server 2016 Developer - duplicate (do not use)
SQL Server 2016 Enterprise - duplicate (do not use)
SQL Server 2016 Enterprise Core - duplicate (do not use)
SQL Server 2016 Standard - duplicate (do not use)
Affected releases:
build lower than 14.0.3223.3
Fixed releases:
14.0.3223.3
Description:
Symptoms
Consider the following scenario: You use Microsoft SQL Server 2016 or 2017 for publisher, distributor and subscriber. The Distribution database is part of an Availability Group (AG). You add new Publication to the Distribution database in the AG. The collation is set to BIN or case-sensitive. In this situation, the publication may fail with an error message that resembles the following: Error 4104, Level 16, State 1, Procedure ProcedureName, Line LineNumber The multi-part identifier "s.job_id" could not be bound.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Resolution
This issue is fixed in the following cumulative updates for SQL Server: Cumulative Update 16 for SQL Server 2017 Cumulative Update 7 for SQL Server 2016 SP2 About cumulative updates for SQL Server: Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server: Latest cumulative update for SQL Server 2017 Latest cumulative update for SQL Server 2016
References
Learn about the terminology that Microsoft uses to describe software updates.
