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.
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?
Lead level SQL DBA currently working for a well established Insurance organisation in London.