• Jim P. (8/31/2012)


    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.

    Thank you very much Jim!

    We are now at least looking at patching. 😀


    Over 12yrs in IT and 10yrs happily stuck with SQL.
    - SQL 2008/R2/2012/2014/2016/2017
    - Oracle 8/9/10/11
    - MySQL 4/5 and MariaDB