January 31, 2018 at 2:30 am
All,
We have an issue that has surfaced since moving from ESX to AHV as our hypervisor, where in we are seeing an IO mismatch between the new 4096 (secondary) and old 512 (primary) log shipping servers. We get several 9004 errors daily and end up removing the log shipping and re-implementing. The secondary site has the log shipped database in Standby, read only mode.
Now, I understand that this would cause the issue and depending upon your version of SQL Server there have been hotfixes / Cu's that address this, along with either trace flag 1800 or 3057.
https://support.microsoft.com/en-us/help/2987585/restore-log-with-standby-mode-on-an-advanced-format-disk-may-cause-a-9
The question I have is, that MS only released the hotfix for SQL 2008 R2 SP2... and we are running with SQL 2008 R2 SP3... which obviously has all the Cu's from between the 2 versions, but does this include the hotfix? I cannot seem to find information on this anywhere... and only details relating to the CU's.
If this is not part of SP3, is it possible, with no detrimental affects, to install this hotfix onto SP3, even though it was released for SP2 and would it actually have an affect in this case?
Thanks all...
Lead level SQL DBA currently working for a well established Insurance organisation in London.
www.linkedin.com/in/hadenkingslandleaddba
February 2, 2018 at 2:32 am
So, finally solved (well worked around this issue)
After a lot of back and forth to MS, we agreed to apply the on demand hotfix 3033860 for SQL 2008 R2 SP3 and then turn on trace flag 3057.
The moral of this story being... be very aware of what is taking place in your environment, not just for SQL Server. This is something I try to do on a daily basis, but in this instance I had no sight or awareness of the hypervisor move. Hopefully you will be a little better placed now if this ever happens to you. Although, come mid 2019, non of us will be running SQL 2008 R2 right? 😉
Lead level SQL DBA currently working for a well established Insurance organisation in London.
www.linkedin.com/in/hadenkingslandleaddba
February 2, 2018 at 7:14 am
I spoke too soon... the issue has re-occurred even after the hotfix and trace flag.... open to ideas?
Lead level SQL DBA currently working for a well established Insurance organisation in London.
www.linkedin.com/in/hadenkingslandleaddba
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply