• The nearest I could find to it is the blog item that was cited in the article.

    But if you look at the dates on the blog it was probably in the code base for SQL 2008 at least.

    http://blogs.msdn.com/b/sqlserverfaq/archive/2009/06/01/size-of-the-transaction-log-increasing-and-cannot-be-truncated-or-shrinked-due-to-snapshot-replication.aspx

    I think this is one where M$ had problems locating it and fixing it, and thought not many users had run into it. So they quietly just patched it.



    ----------------
    Jim P.

    A little bit of this and a little byte of that can cause bloatware.