sritchie
Member
I was wondering if anyone has any real-world experience of the performance difference in running unicode & non-unicode business data on SQL Server 2005. I understand there's a performance hit from JDE converting non-unicode data to unicode & vice versa, however everything I know about SQL Server performance (not that much, admittedly) is telling me that the increasing the page count on all of those string indexes is going to drastically increase logical IO and hammer performance.
I'm aware there's a whitepaper around showing 2.6% performance increase with unicode on iSeries, however I'd expect the iSeries probably has better disk IO than our SAN. Has anyone done any research on unicode performance on a non-iSeries platform?
I'm aware there's a whitepaper around showing 2.6% performance increase with unicode on iSeries, however I'd expect the iSeries probably has better disk IO than our SAN. Has anyone done any research on unicode performance on a non-iSeries platform?