Servicing model : release documentation about fixes before the files themselves - by AaronBertrand

Status : 

  External<br /><br />
		This item may be valid but belongs to an external system out of the direct control of this product team.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 509152 Comments
Status Resolved Workarounds
Type Suggestion Repros 0
Opened 11/8/2009 4:34:31 PM
Access Restriction Public


This week, CU4 for SQL Server 2008 SP1 was quietly slipped some updated files, referencing a KB article that does not yet exist.  I wrote plenty about it here:

The biggest danger, I feel, is that users who have tested CU4 (2734) in their labs may tell their deployment team to go download CU4 from, and deploy it to their production environment.  But when they get there, they could very easily choose to download the "updated" version (2740).  I don't think I have to explain how many ways this could end badly.
Sign in to post a comment.
Posted by Microsoft on 11/18/2009 at 8:42 PM
Thank you for filing Suggestion #509152 through Microsoft Connect. During our release cycles it is in our best intention to synchronize the release of the hotfix and documentation to ensure the customers are getting the correct information they need in order to make a sound decision about their SQL Server deployment.

To learn more about build 2740 please visit or the SQL Release Services Blog site at

We will endeavor to better synchronize the release of the hotfix with the documentation in the future.

Abhishek Sinha
Program Manager
SQL Server Sustained Engineering
Posted by ManServ on 11/13/2009 at 1:02 PM
Full ACK. ATM they don't even tell us the published date, just "last review".

Microsoft has published KB976953 and KB976761 that describes a bug in SQL Server Agent. However, KB973602 was not updated yet to warn against these known issues.
Posted by ChrisAVWood on 11/9/2009 at 2:10 PM
And as the KB article gets changed give it a change history log