Microsoft Knowledge Base Email Alertz

KBAlertz.com: FIX: The SPACE function always returns one space in SQL Server 2000 if the SPACE function uses a collation that differs from the collation of the current database

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]






Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

FIX: The SPACE function always returns one space in SQL Server 2000 if the SPACE function uses a collation that differs from the collation of the current database

Article ID:946584
Last Review:March 12, 2008
Revision:1.3
Bug #: 50002208 (SQL Hotfix)
Microsoft distributes Microsoft SQL Server 2000 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 2000 fix release.
On This Page

SYMPTOMS

Consider the following scenario. You have a query that contains the SPACE function. The SPACE function uses a collation that differs from the collation of the current database. You specify a value that is larger than 1 for the parameter of the SPACE function. Then, you run the query in Microsoft SQL Server 2000. In this scenario, the SPACE function always returns one space.

This problem does not occur in Microsoft SQL Server 2005.

Back to the top

RESOLUTION

Hotfix information

A 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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 (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.

Prerequisites

You must have SQL Server 2000 Service Pack 4 installed to apply this hotfix. For more information about how to obtain SQL Server 2000 Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:
290211 (http://kbalertz.com/Feedback.aspx?kbNumber=290211/) How to obtain the latest SQL Server 2000 service pack

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

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 2000, 32-bit version
File nameFile versionFile sizeDateTimePlatform
Dtsui.dll2000.80.2271.01,593,34411-Feb-200804:36x86
Impprov.dll2000.80.2271.0102,40011-Feb-200804:36x86
Msgprox.dll2000.80.2271.094,20811-Feb-200804:36x86
Msrpjt40.dll4.10.9424.0188,47311-Feb-200804:36x86
Mssdi98.dll8.11.50523.0239,10411-Feb-200804:36x86
Ntwdblib.dll2000.80.2271.0290,81611-Feb-200804:36x86
Odsole70.dll2000.80.2271.069,63211-Feb-200804:36x86
Osql.exe2000.80.2271.057,34411-Feb-200804:36x86
Pfclnt80.dll2000.80.2271.0430,08011-Feb-200804:36x86
Qrdrsvc.exe2000.80.2271.0192,51211-Feb-200804:36x86
Replmerg.exe2000.80.2271.0163,84011-Feb-200804:36x86
Replprov.dll2000.80.2271.0237,56811-Feb-200804:36x86
Replrec.dll2000.80.2271.0315,39211-Feb-200804:36x86
Replsub.dll2000.80.2271.0270,33611-Feb-200804:36x86
Rinitcom.dll2000.80.2271.0278,52811-Feb-200804:36x86
Semexec.dll2000.80.2271.0856,06411-Feb-200804:36x86
Semmap.dll2000.80.2271.053,24811-Feb-200804:36x86
Snapshot.exe2000.80.2271.061,44011-Feb-200804:36x86
Sqlagent.exe2000.80.2271.0323,58411-Feb-200804:36x86
Sqldiag.exe2000.80.2271.0118,78411-Feb-200804:36x86
Sqldmo.dll2000.80.2271.04,362,24011-Feb-200804:36x86
Sqldumper.exeNot Applicable22,52811-Feb-200804:36x86
Sqlevn70.rll2000.80.2271.045,05611-Feb-200802:12Not Applicable
Sqlfth75.dll2000.80.2271.0102,40011-Feb-200804:36x86
Sqlservr.exe2000.80.2271.09,183,23211-Feb-200804:36x86
Sqlsort.dll2000.80.2271.0589,82411-Feb-200804:36x86
Sqlvdi.dll2000.85.2101.0122,36811-Feb-200804:36x86
Stardds.dll2000.80.2271.0176,12811-Feb-200804:36x86
Svrnetcn.dll2000.80.2271.0110,59211-Feb-200804:36x86
Ums.dll2000.80.2271.035,84011-Feb-200804:36x86
Xpstar.dll2000.80.2271.0311,29611-Feb-200804:36x86

Back to the top

WORKAROUND

To work around this problem, use the COLLATE clause to explicitly cast the collation that the SPACE function uses to be the same as the collation of the current database. For example, run the following statement that uses the COLLATE clause.
SELECT Corrected='*' COLLATE database_default + SPACE(12)  + '*'

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

MORE INFORMATION

For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 (http://kbalertz.com/Feedback.aspx?kbNumber=822499/) New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 (http://kbalertz.com/Feedback.aspx?kbNumber=824684/) Description of the standard terminology that is used to describe Microsoft software updates
For more information about the COLLATE clause, see the "COLLATE" topic in SQL Server 2000 Books Online.

Back to the top


APPLIES TO
•Microsoft SQL Server 2000 Developer Edition
•Microsoft SQL Server 2000 Enterprise Edition
•Microsoft SQL Server 2000 Personal Edition
•Microsoft SQL Server 2000 Standard Edition
•Microsoft SQL Server 2000, Workgroup Edition

Back to the top

Keywords: 
kbautohotfix kbhotfixserver kbfix kbexpertiseadvanced kbqfe KB946584

Back to the top

   

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please