You should also update the server replication components on Microsoft Internet Information Services (IIS) servers if you have, or plan to build, replication topologies that include both:Microsoft SQL Server 2000 Windows CE Edition (SQL Server CE) andDatabases and publishers running MSDE 2000 Release A.An updated SQL Server CE Server Tools installer is available at this Microsoft Web site.
For distributed queries, MSDE 2000 Release A returns provider error information in addition to the server error information returned by earlier versions of MSDE 2000. When a query between linked servers results in an error, MSDE 2000 checks to see if the provider supports the IErrorRecords OLE DB interface. If this interface is supported, MSDE 2000 calls the GetErrorInfo function to get additional error information from the provider and returns this information to the user as part of the error message. If the IErrorRecords interface is not supported, there is no change in MSDE 2000 behavior: MSDE 2000 returns a generic error.
Change the owner of a published database to the sa built-in administrator login before attaching or restoring the database if:The instance is running MDSE 2000 Release A.The user attaching the database is not a member of the sysadmin fixed server role.Cross-database ownership chaining has not been allowed.If all of these conditions are true, you should execute the sp_changedbowner stored procedure on the attached or restored database. Assign ownership to the sa login to ensure that replication functions correctly.
This is a technique we often used on Windows 2000 servers. The original MDAC that shipped with Windows 2000 didn't support looking up the port for Named Instances. However, if you knew the port, you could create an alias and everything would work just fine.
I have to support several older apps developed in VB4 (16 bit) and VB5 and we are migrating from SQL Server 2000 to SQL Server 2005. The alias works great with apps developed in VB5 using ODBCDirect and ADO but does not seem to work for apps developed using VB4 (16 bit) using DAO for data access. The new database server is setup as a named instance. Is it the alias or the named instance that is causing the problem Any ideas on how to get around this
Windows Server 2003 is the follow-up to Windows 2000 Server, incorporating compatibility and other features from Windows XP. Unlike Windows 2000, Windows Server 2003's default installation has none of the server components enabled, to reduce the attack surface of new machines. Windows Server 2003 includes compatibility modes to allow older applications to run with greater stability. It was made more compatible with Windows NT 4.0 domain-based networking. Windows Server 2003 brought in enhanced Active Directory compatibility and better deployment support to ease the transition from Windows NT 4.0 to Windows Server 2003 and Windows XP Professional.
Internet Information Services (IIS) has been upgraded to v6.0.There have also been significant improvements to Message Queuing and to Active Directory, such as the ability to deactivate classes from the schema, or to run multiple instances of the directory server (ADAM). There was also a notable change in the ability to create a rescue disk, which was removed in favor of Automated System Recovery (ASR).Other Improvements to Group Policy handling and administration have also been made. For the first time in the history of Windows Server, a backup system to restore lost files has been created together with improved disk management, including the ability to back up from shadows of files, allowing the backup of open files.Another important area where improvements have been made are the scripting and command line tools, with the improvements being part of Microsoft's initiative to bring a complete command shell to the next version of Windows. Other notable new features include support for a hardware-based \"watchdog timer\", which can restart the server if the operating system does not respond within a certain amount of time. On this version of Windows Server the Themes service is disabled by default, defaulting to the appearance of previous Windows versions (such as Windows 2000).
The Standard edition of SBS includes Microsoft Remote Web Workplace, Windows SharePoint Services, Microsoft Exchange Server, Fax Server, Active Directory, a basic firewall, DHCP server and network address translation capabilities. The Premium edition of SBS adds Microsoft SQL Server 2000 and Microsoft ISA Server 2004.
Windows Server 2003 for Embedded Systems replaced \"Windows 2000 Server for Embedded Systems\". Intended use was for building firewall, VPN caching servers and similar appliances. Variants were available with \"Server Appliance Software\" and with \"Microsoft Internet Security and Acceleration Server\"  1e1e36bf2d