Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | SQL Server 2000 Service Pack 4 |
|---|---|
| Date: | Sat, 7 May 2005 12:35:19 -0500 |
http://www.microsoft.com/sql/downloads/2000/sp4.asp SQL Server 2000 Service Pack 4 Posted: May 06, 2005 SQL Server 2000 Service Pack 4 (SP4) adds platform support for Microsoft Windows Server 2003 x64 Edition, allowing 32-bit SQL Server 2000 applications to run on 64-bit platforms using the Windows on Windows emulator (WOW64). SP4 addresses specific issues discovered in SQL Server 2000 since its ship date. SP4 is also the first service pack to service the 64-bit edition of SQL Server. Because SQL Server service packs are cumulative, SP4 includes all fixes from previously released Service Pack 1 (SP1), Service Pack 2 (SP2), Service Pack 3 (SP3), and Service Pack 3a (SP3a). SP4 can be applied to an original SQL Server 2000 installation or to one where SP1, SP2, SP3, or SP3a was previously applied. This service pack includes the MS03-031 security bulletin released in July, 2003. SQL Server 2000 SP4: Includes a new version of MSXML version 3.0 SP6. With SP4, the OPENXML statement is updated to use a custom-built XML parsing technology designed to be backward compatible with MSXML 2.6. Includes MDAC 2.8 SP1 except for Windows XP and Windows Server 2003 platforms, where it is included with the operating system service packs for those platforms. Adds the following platform support: With Microsoft Windows Server 2003 x64 Edition, SP4 provides support for 32-bit SQL Server applications on 64-bit architectures using the Windows on Windows emulator (WOW64). For more information on specific 64-bit platforms supported, see the Windows Server 2003 x64 Editions Product Overview. With SP4, you can leverage 64-bit processor architectures using 32-bit SQL Server applications when running in WOW64. Note: SQL Server 32-bit applications, including SQL server client tools, are still not supported on WOW64 for IA64. Also, currently 32-bit Reporting Services is not supported to run on WOW64 on IA64 and x64 platforms running Windows Server 2003 x64 Edition. Improves documentation; the Readme documents are reorganized into four distinct readme files for the different SP4 components: ReadmeSql2k32sp4: Readme for Service Pack 4 for Microsoft SQL Server 2000 (32-bit) ReadmeSql2k32asp4: Readme for Service Pack 4 for Microsoft SQL Server 2000 Analysis Services ReadmeSql2k32desksp4: Readme for Service Pack 4 for Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) ReadmeSql2k64sp4: Readme for Service Pack 4 for Microsoft SQL Server 2000 (64-bit) Benefits In addition to providing the latest updates and fixes, SQL Server 2000 SP4 provides enhanced performance, security, and serviceability. Performance SQL Server 2000 SP4 improves performance on 64-bit systems with 32 or more processors. Security SQL Server 2000 SP4 provides: Refreshed, more secure Visual Database Tools (Table Designer, Database Diagrams, and Query Designer). New registry entries to provide additional control over security, metadata, and memory management. Serviceability SQL Server 2000 SP4 introduces new serviceability functionality that enables you to remove hotfixes applied to SP4 and later versions of SQL Server 2000 running on Microsoft Windows XP and Windows Server 2003. SP4 itself cannot be rolled back. Error reporting can be enabled for selected instances during the SP4 installation. For descriptions of additional changes, please refer to the readme files for SP4. Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) and SP4 Users who have an existing instance of MSDE 2000 must know how their instance of MSDE 2000 was installed to know how to update it. In particular, you must know the original package name for your instance of MSDE 2000. To determine the original package name, see the article How To Identify Which MSI File Was Used for an Existing MSDE Installation in the Microsoft Knowledge Base. If the original package name for your instance was SqlRun01.msi through SqlRun16.msi, use the SQL2000.MSDE-KB884525-SP4-x86-ENU.exe file to apply SP4. If the original package name for your instance was Sample.msi or SampleUpg.msi, see the article How To Create Patch Files for the MSDE 2000 Sample.msi File. If your original package name indicates the instance of MSDE 2000 was installed by the Microsoft .NET SDK or Microsoft Application Center, see Microsoft Products that include MSDE 2000 for instructions. If the product code associated with your instance of MSDE 2000 is not listed, then the instance was installed by the setup utility of an application. You cannot use the SQL2000.MSDE-KB884525-SP4-x86-ENU.exe file to apply SP4 to such MSDE instances. Instead, you must get a patch file from the company who wrote the application. If the application came from a company other than Microsoft, you must contact that company for a patch file. If the application came from Microsoft, refer to Microsoft Products that include MSDE 2000 which lists the MSDE applications from Microsoft (this page will be updated with information about how to upgrade these instances of MSDE 2000). -- NTBugtraq Editor's Note: Most viruses these days use spoofed email addresses. As such, using an Anti-Virus product which automatically notifies the perceived sender of a message it believes is infected may well cause more harm than good. Someone who did not actually send you a virus may receive the notification and scramble their support staff to find an infection which never existed in the first place. Suggest such notifications be disabled by whomever is responsible for your AV, or at least that the idea is considered. --
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Announcement: The Web Security Mailing List, contact |
|---|---|
| Next by Date: | Re: MS05-019 Breaks VPN, Arley Barros Leal |
| Previous by Thread: | Announcement: The Web Security Mailing List, contact |
| Next by Thread: | High risk flaw in HP OpenView Radia Management Agent, NGSSoftware Insight Security Research |
| Indexes: | [Date] [Thread] [Top] [All Lists] |