FIX: A SELECT query that uses the LIKE clause may return incorrect results in SQL Server 2005 Mobile Edition (920116)
The information in this article applies to:
- Microsoft SQL Server 2005 Mobile Edition
Bug: #11419 (SQL Server CE)
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. SUMMARYThis article describes the following about this hotfix
release:
- The issues that are fixed by this hotfix package
- The prerequisites for applying the hotfix
package
- Information about whether you must restart the computer after you apply the
hotfix package
- Information about whether the hotfix package is replaced by any other hotfix
package
- Information about whether you must make any registry changes after you apply
the hotfix package
- The files that are contained in the hotfix
package
SYMPTOMSWhen you use a SELECT query that uses the LIKE clause in Microsoft SQL Server 2005 Mobile Edition, the query may
return an incorrect result.CAUSEThis problem may occur when you query a table that has a
composite primary key.RESOLUTIONA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft SQL Server 2005 Mobile Edition service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. PrerequisitesThere are no prerequisites for this hotfix. Restart informationYou do not have to restart your computer
after you apply this hotfix. Registry informationYou
do not have to create any registry keys or modify any registry keys to use any
hotfixes that this package contains. Hotfix file informationThis hotfix may not contain all the files that you must have to
fully update a product to the latest build. This hotfix contains only the files
that you must have to correct the issues that this article
lists.
The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.SQL Server 2005 Mobile Edition, ARMV4 processor
|
| sqlcecompact30.dll | 3.0.5207.1 | 71,168
| 09-May-2006 | 23:56 | | sqlcese30.dll | 3.0.5207.3 | 400,896 | 24-May-2006 | 18:36 |
SQL Server 2005 Mobile Edition, ARMV4I processor |
| sqlcecompact30.dll | 3.0.5207.1 | 80,608 | 10-May-2006 | 17:00 | | sqlcese30.dll | 3.0.5207.3 | 419,040 | 24-May-2006 | 19:51 |
WORKAROUNDTo work around this problem, use the upper function or the lower function in the WHERE clause of the SELECT query. For example,
use the following query: SELECT * FROM TABLE1 WHERE upper(A) LIKE 'ABC%' STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.
| Modification Type: | Minor | Last Reviewed: | 7/26/2006 |
|---|
| Keywords: | kbQFE kbhotfixserver kbpubtypekc KB920116 kbAudITPRO kbAudDeveloper |
|---|
|