Anyone have a workaround for this bug in LocalDb 2012
This has been closed as fixed so I guess this might be fixed in SQL Server 2012 Sp2. What is SP level of SQL Server 2012 in your case
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP