Do you know if this issue persists across all SQL server versions or has it been fixed in any of the newer versions?