SQL Server Q&A

Symptoms
SummaryMore informationPrerequisitesHow to identify your SQL Server service pack and version SQL Server 2000 baseline buildsHotfix update information
Resolution
This article contains a list of the Microsoft SQL Server 2000 hotfixes. You can use this list to determine which hotfixes are included in a specific hotfix build. Unless otherwise specified, all the hotfixes in prior builds will be included in later builds. The list includes all the public hotfixes that have been released since the release of Microsoft SQL Server 2000 Service Pack 3 and Microsoft SQL Server 2000 Service Pack 3a.
Here are some important notes regarding the Microsoft SQL Server 2000 hotfixes. For all the hotfixes, you must have SQL Server 2000 Service Pack 3 or SQL Server 2000 Service Pack 3a installed.For hotfixes earlier than build 8.00.0818, we recommend that you apply build 8.00.0818 instead. Build 8.00.0818 contains security fixes that are documented in Microsoft Security Bulletin MS03-031. For download locations and additional information about the security vulnerability addressed in MS03-031, visit the following Microsoft Web site:
http://www.microsoft.com/technet/security/bulletin/MS03-031.mspx(http://www.microsoft.com/technet/security/bulletin/MS03-031.mspx)Hotfixes that are not part of a security release can only be obtained by contacting Microsoft Product Support Services. For a complete list of Microsoft Product Support Services telephone phone numbers and for information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS (http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)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. To install any hotfix later than build 8.00.0977, you must first install the 8.00.0977 “baseline” build. For more information about “baseline” builds, see the “SQL Server 2000 baseline builds” section. This list does not contain the fixes for Microsoft Data Access Components (MDAC) or forMicrosoft SQL Server 2000 Analysis Services.

Symptoms
Inserting certain Unicode strings into a SQL Server 2000 Windows CE (SSCE) table might cause an SQL INSERT command to fail with an application error, or the application might stop responding (hang) while other programs remain responsive. The symptoms of the problem can vary, but may include messages similar to:

Application <Executable file name> has performed an illegal operation and will be shut down. Fatal Exception 0xC0000005
Resolution
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS(http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)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.
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.
Microsoft SQL Server 2000 Windows CE Edition 2.0

DateTimeVersionSizeFile name—————————————————————–15-Apr-200314:152.0.5214.01,403,972 bytesSsce20.dllARM
Microsoft SQL Server 2000 Windows CE Edition 1.1

DateTimeVersionSizeFile name—————————————————————–26-Feb-200320:441.1.5026.01,258,496 bytesSsce10.dllARMNote Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.

Symptoms
Note: This article discusses a scenariothat may beaddressed by Microsoft Advisory Services.
Microsoft Advisory Services is an hourly fee-based, consultative support option that provides proactive support beyond your break-fix product maintenance needs. This is a remote, phone-based support option that includes working with the same technician for assistance with issues like product migration, code review, or new program development. This service is typically used for shorter engagements, and is designed for developers and IT professionals who do not require the traditional onsite consulting or sustained account management services that are available from other Microsoft support options. This article also provides some self-help resources for this scenario.
For additional information on Microsoft Advisory Services, including on how to engage, refer to this Microsoft web page:
http://support.microsoft.com/default.aspx?pr=AdvisoryService(http://support.microsoft.com/default.aspx?pr=advisoryservice)
Resolution
Microsoft Advisory Services does not guarantee identification of root cause.For example, if adding an index, updating statistics,or applying a Cumulative Update (CU) resolves the issue, Microsoft Advisory Services is not obligated to continue troubleshooting to determine customer specific root cause.If at the request of Advisory Services personnel, you are willing to continue troubleshooting to identify root case, you will not be charged for the additional hours. You may be asked to upgrade to the latest build (CU) of SQL Server for their Service Pack and activate certain fixes.Ifyou are unable to upgrade to the latest CU or activate fixes, working on your issue may be postponed.If upgrading to the latest CU fixes the problem, the case will be marked as “bug related” and you will not be charged.

Symptoms
Microsoft supports setup and installation for the Crystal Reports products shipped with the Professional and Enterprise Editions of Microsoft Visual Basic for Windows versions 3.0, 4.0, 5.0 and 6.0. For other Crystal Reports support, please do not contact Microsoft. Please contact Crystal Decisions(formerly Seagate Software), which now owns and supports Crystal Report Writer. For support on Crystal Reports in Visual Studio .NET, please see the article in the References section below.
NOTE: The third-party contact information included in this article is provided to help you find the technical support you need. This contactinformation is subject to change without notice. Microsoft in no wayguarantees the accuracy of this third-party contact information.
Resolution
Support for Crystal Reports is provided to registered users. To register for Crystal Reports, visit the following Business Objects Web site:
http://www.businessobjects.com/register/content.asp(http://www.businessobjects.com/register/content.asp) Registered users of Crystal Reports may obtain technical support for their Crystal Reports product. To learn more about obtaining technical support, visit the following Business Objects Web site:
http://support.businessobjects.com/(http://support.businessobjects.com/) For information about developer-related support for Crystal Reports, visit the following Business Objects Web site:
http://www.businessobjects.com/services/support/crystal_dev.asp(http://www.businessobjects.com/services/support/crystal_dev.asp)