Issue
Operating System Selection when using SQL Server
Product Line
TAC INET
Environment
I/NET Seven Site
Cause
Making decisions on operating system selection while using SQL Server 2000
Resolution
If your site has grown beyond the capabilities of the Microsoft SQL Desktop Engine (MSDE) as discussed in Customer Advisory CA-2004-04 then you need to decide upon an operating system to use when you upgrade to SQL Server 2000.
SQL Server 2000 Enterprise Edition and Standard Edition can run on the following operating systems:
- Windows Server 2003, Standard Edition
- Windows Server 2003, Enterprise Edition
- Windows Server 2003, Datacenter Edition
- Windows® 2000 Server
- Windows 2000 Advanced Server
- Windows 2000 Datacenter Server
Source: http://www.microsoft.com/sql/evaluation/sysreqs/2000/default.mspx
An option to consider based on the needs of the customer is whether Windows Small Business Server 2003 Premium Edition can meet their needs. This version sells at almost the same cost as SQL Server 2000 (5 CALs), however it includes much more.
Windows Small Business Server 2003, Premium Edition includes the following components:
- Microsoft Windows Server 2003
- Microsoft Exchange Server 2003, Standard Edition
- Microsoft Shared Fax Services
- Microsoft Office Outlook 2003
- Microsoft Windows SharePoint Services 2.0
- Health Monitor 2.1
- Remote Web Workplace
- Microsoft Internet Security and Acceleration Server 2000, Standard Edition with Service Pack 1 (SP1)
- Microsoft SQL Server 2000, Standard Edition with Service Pack 3a (SP3a)
- Microsoft Office FrontPage 2003
It is important to note that there are some restrictions built into this version of Windows Server 2003. These restrictions limit it to only a single domain solution and can only expand up to 75 users or device connections.
Windows Small Business Server restrictions
Windows Small Business Server provides a cost-effective suite of programs for small businesses that have 75 or fewer users or devices. To help you prevent unapproved network installations and to help you protect your networks against viruses and other attacks, Microsoft has placed the following restrictions on the use of Windows Small Business Server:
- You must install all the component server programs in Windows Small Business Server on a single computer. No component may be installed on a separate computer. If you want to run one or more of the component services on a computer other than the Windows Small Business Server-based computer, the other computer requires separate licenses.
- You can connect a maximum of 75 users or devices to a Windows Small Business Server-based network. This requirement limits the number of users or workstations that can access one or more of the component server programs.
- Windows Small Business Server is a single-domain solution that is not intended to be integrated with other Windows-based domains. You are not permitted to establish explicit trusts to other Microsoft Windows NT-based domains or to Active Directory directory service domains. Also, Windows Small Business Server does not let you create child domains. The computer that is running Windows Small Business Server must have all operations master roles and must be at the root of the Active Directory forest.
- The following features that are available in earlier versions of Small Business Server are not available in Windows Small Business Server:
- Microsoft Shared Modem Service
- Microsoft Terminal Server
- Windows Small Business Server supports up to two physical CPUs and up to four virtual CPUs with hyperthreading.
Note: Earlier versions of Windows Small Business Server support up to four physical CPUs. - You can have other domain controllers and member servers in your Windows Small Business Server-based network. However, the computer that is running Windows Small Business Server must be set up as the root domain controller of an Active Directory forest. This requirement may prevent the computer that is running Windows Small Business Server from serving as a corporate branch office server or as a department server of a large organization that is based on Active Directory or on Microsoft Windows NT 4.0. You cannot add Windows Small Business Server to an existing domain. You must install a Windows Small Business Server-based domain and then add additional domain controllers or member servers to the domain.
- When you run Exchange 2003 on a Windows Small Business Server-based network, Exchange 2003 cannot be part of a larger Exchange 2003 organization. Because Windows Small Business Server is installed at the root of the Active Directory forest, you cannot install Exchange 2003 components that belong to an existing Exchange 2003 organization.
Source: http://support.microsoft.com/default.aspx?scid=kb;en-us;842690
Windows Small Business Server 2003 Premium Edition is a good solution for jobs where the controls contractor will be managing the server operating system that is the core of the BMS. Many customers today will allow controls contractors to utilize their IP infrastructure but want the system managed and maintained by that same controls contractor. This software allows that contractor to provide a turn key installation and include all PC hardware and software.
Windows Small Business Server 2003 Premium Edition is also a very cost effective solution for jobs where the specification requires a server operating system or a full version of SQL server that the contractor must provide.
It is recommended that if Windows Small Business Server 2003 Premium Edition is used, any software that is not needed on the server is disabled (i.e. Exchange Server, Fax Services, SharePoint Services).
In conclusion, Windows Small Business Server 2003 Premium Edition is a cost effective way to provide SQL Server at a site if all criteria are met.
Update: If using I/NET 2.40 and above, please check this compatibility matrix for Operating Systems when using SQL Server
For other compatibility issues, see Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Sa....
