Select the product you need help with
FIX: A Query with a LIKE Comparison Results in a Non-Optimal Query Plan When You Use a Hungarian SQL Server CollationArticle ID: 826364 - View products that this article applies to. On This PageSYMPTOMSWhen you generate a query execution plan for a query that contains a LIKE comparison on a column, the query execution plan may not be optimal. You may see that the query execution plan uses a table scan even when there is a clustered index available on the column that is used with the LIKE operator. This problem may occur if the string that is used in the LIKE comparison ends with the last character or the largest character in the sort order of the column's SQL Server collation. For example, this problem may occur if the string pattern that is used in the LIKE comparison ends with the string z% and the column that is involved in the LIKE comparison uses a SQL Server collation such as a Latin1_General_CI_AS collation, a Hungarian_CI_AS collation, or a Hungarian_CI_AI collation. RESOLUTIONService pack informationTo resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:290211
(http://support.microsoft.com/kb/290211/
)
How to obtain the latest SQL Server 2000 service packHotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
(http://support.microsoft.com/contactus/?ws=support)
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Date Time Version Size File name ------------------------------------------------------------------------------- 31-May-2003 18:45 2000.80.818.0 78,400 Console.exe 25-Jun-2003 01:01 2000.80.818.0 33,340 Dbmslpcn.dll 25-Apr-2003 02:12 786,432 Distmdl.ldf 25-Apr-2003 02:12 2,359,296 Distmdl.mdf 30-Jan-2003 01:55 180 Drop_repl_hotfix.sql 23-Jun-2003 22:40 2000.80.837.0 1,557,052 Dtsui.dll 23-Jun-2003 22:40 2000.80.837.0 639,552 Dtswiz.dll 24-Apr-2003 02:51 747,927 Instdist.sql 03-May-2003 01:56 1,581 Inst_repl_hotfix.sql 08-Feb-2003 06:40 2000.80.765.0 90,692 Msgprox.dll 01-Apr-2003 02:07 1,873 Odsole.sql 05-Apr-2003 01:46 2000.80.800.0 62,024 Odsole70.dll 07-May-2003 20:41 2000.80.819.0 25,144 Opends60.dll 02-Apr-2003 21:48 2000.80.796.0 57,904 Osql.exe 02-Apr-2003 23:15 2000.80.797.0 279,104 Pfutil80.dll 22-May-2003 22:57 19,195 Qfe469571.sql 11-Jul-2003 17:04 1,084,147 Replmerg.sql 04-Apr-2003 21:53 2000.80.798.0 221,768 Replprov.dll 08-Feb-2003 06:40 2000.80.765.0 307,784 Replrec.dll 11-Jul-2003 16:56 1,085,925 Replsys.sql 01-Jun-2003 01:01 2000.80.818.0 492,096 Semobj.dll 31-May-2003 18:27 2000.80.818.0 172,032 Semobj.rll 29-May-2003 00:29 115,944 Sp3_serv_uni.sql 01-Jun-2003 01:01 2000.80.818.0 4,215,360 Sqldmo.dll 07-Apr-2003 17:44 25,172 Sqldumper.exe 19-Mar-2003 18:20 2000.80.789.0 28,672 Sqlevn70.rll 02-Jul-2003 00:18 2000.80.834.0 180,736 Sqlmap70.dll 08-Feb-2003 06:40 2000.80.765.0 57,920 Sqlrepss.dll 25-Jul-2003 21:45 2000.80.845.0 7,553,105 Sqlservr.exe 25-Jul-2003 21:44 2000.80.845.0 590,396 Sqlsort.dll 08-Feb-2003 06:40 2000.80.765.0 45,644 Sqlvdi.dll 25-Jun-2003 01:01 2000.80.818.0 33,340 Ssmslpcn.dll 01-Jun-2003 01:01 2000.80.818.0 82,492 Ssnetlib.dll 01-Jun-2003 01:01 2000.80.818.0 25,148 Ssnmpn70.dll 01-Jun-2003 01:01 2000.80.818.0 158,240 Svrnetcn.dll 31-May-2003 18:59 2000.80.818.0 76,416 Svrnetcn.exe 30-Apr-2003 23:52 2000.80.816.0 45,132 Ums.dll 02-Jul-2003 00:19 2000.80.834.0 98,816 Xpweb70.dll Note Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4. PropertiesArticle ID: 826364 - Last Review: November 2, 2007 - Revision: 7.5 APPLIES TO
|



Back to the top








