February 7, 2014 at 9:28 am
So, I have a new SQL Server 2012 installation. I have a few test\dev databases that will be ported over from 2005 to 2012 within the next month.
I just noticed that the transaction logs on these databases are blowing out despite being in Simple recovery model. What's even more weird is that these DBs are DEV databases so they are not even that highly utilized by production users and thus their size should be relatively contained.
I found the following article on MS: http://support.microsoft.com/kb/2830400
These DBs were initialized from backups from the source server and initially set at Simple recovery model. However, they behave like they are in Full Recovery Model.
Wondering if anyone else has seen this behavior before?
The work around was to reset the Recovery Model to Full then back to simple via:
ALTER DATABASE myDB SET RECOVERY FULL;
go
ALTER DATABASE myDB SET RECOVERY SIMPLE;
go
I will let you know if this works for me or not so this post may be more of a head's up for those that face this problem.
Thanks
Jim
February 7, 2014 at 9:49 am
Yeah, I have seen this before.
If you're doing a new migration to SQL 2012, I'd strongly recommend going straight up to the latest Cumulative Update if your policies allow it and doing your testing against that, rather than just SP1. There's quite a few big bugs that have been fixed post-SP1.
February 7, 2014 at 11:31 am
The latest CU is Update 8 ( http://support.microsoft.com/kb/2917531 ). You think I should update to that CU? I'm sometimes hesitant to update CU preferring to wait for an SP but if I see enough issues I guess I will.
I control this environment so it is my call. I guess since we're in a QA\DEV mode now I can apply the CU to that environment and see how it goes. If all is well, I can apply to the PROD environment (which is not live yet b\c we're in the upgrade process anyway).
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply