Hi,
after testing and checking our source, i woundered why the SQLServer 2000 and 2005 do not the same. The source was fine and i found the problem on SQL Server side.
The Problem is, that the 2005 use bad exec. plans because he use the comparison operater (>,<) instead of the Like operator (SQL 2000 behavior)
So the SQL2005 returns more rows an the 2000. U can see this when using Query Analyzer and Profiler.
So, i search the i-net and found an Update on ms support site.
Now the question, before i will test this update, has somebody some experience with following Update 4 for SP2 for SQL Server 2005 :?:
http://support.microsoft.com/kb/942659/
Regards
Answers
http://blogs.msdn.com/microsoft_dynamics_nav_sustained_engineering/archive/2007/11/19/new-trace-flag-in-update-4-for-sql-2005-sp2.aspx
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog
Thanks waldo
I always see what happens. Until now, I only set this flag only a few times... .
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog
I have several customers running SQL Server 2005 build 9.0.3200 without any problems; even though there was no need for the new traceflag 4119, yet.
Have in mind that meanwhile 3215 (U5) is available - but I've got no experiences with this one, so far ...
NAV/SQL Performance Optimization & Troubleshooting
STRYK System Improvement
The Blog - The Book - The Tool