Pros/Cons of using Win 2003 over Win 2000 for SQL Server Enterprise ?

We've recently got a new Server in.
The server has 16Gb of RAM, 8 cpus etc
We now have a choice of sticking with Windows 2000 Advanced Server or
going with Windows 2003 Enterprise edition.
Besides being able to use more RAM and having to use Service pack 3a
in Win 2003
Any pros/cons of both ?
Any recommendations ?
We use Full text, replication, analysis services etc
What issues / Enhancements has MS introduced for sp3A ?
I know that once Service pack 3A is installed all full text indexes
are automatically rebuilt..
In a replication scenario Is it necessary or just a recommendation
that all participants in the replication scenario are using the same
service pack ?
Anything else to look out for ?Win2003 has several enhancements that canmake it very worth while. The cpu
scheduling and parallism is improved along with many improvements in the
file and I/O areas. Win2003 is just a better choice overall for an
enterprise server in my opinion.
--
Andrew J. Kelly
SQL Server MVP
"Steve" <stevekeilygroups@.yahoo.com.au> wrote in message
news:70809952.0311191644.338d1eb3@.posting.google.com...
> We've recently got a new Server in.
> The server has 16Gb of RAM, 8 cpus etc
> We now have a choice of sticking with Windows 2000 Advanced Server or
> going with Windows 2003 Enterprise edition.
> Besides being able to use more RAM and having to use Service pack 3a
> in Win 2003
> Any pros/cons of both ?
> Any recommendations ?
> We use Full text, replication, analysis services etc
> What issues / Enhancements has MS introduced for sp3A ?
> I know that once Service pack 3A is installed all full text indexes
> are automatically rebuilt..
> In a replication scenario Is it necessary or just a recommendation
> that all participants in the replication scenario are using the same
> service pack ?
>
> Anything else to look out for ?

Promoting a SQL Server 2000 to a DC

I manage a small Win 2k domain with 3 servers and about 20 users (IIS for ou
r
website on one server, DC & Exchange on one, SQL 2000/file/print on one). W
e
currently have a single DC in our domain and I want to promote one of the
other servers to a DC for backup purposes. The IIS box is out because it
hosts our public web page, which leaves me with the SQL box. I read that
DCPromo removes any local user accounts and am not sure of how this will
affect our SQL Server. It is currently using mixed authentication and start
s
as a system account. Any constructive feedback is appreciated.>
> I manage a small Win 2k domain with 3 servers and about 20 users (IIS for
our
> website on one server, DC & Exchange on one, SQL 2000/file/print on one).
We
> currently have a single DC in our domain and I want to promote one of the
> other servers to a DC for backup purposes. The IIS box is out because it
> hosts our public web page, which leaves me with the SQL box. I read that
> DCPromo removes any local user accounts and am not sure of how this will
> affect our SQL Server. It is currently using mixed authentication and
starts
> as a system account. Any constructive feedback is appreciated.
--
For performance reasons, we generally do not recommend running SQL Server
on a domain controller.
Regards,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.sql

Promoting a SQL Server 2000 to a DC

I manage a small Win 2k domain with 3 servers and about 20 users (IIS for our
website on one server, DC & Exchange on one, SQL 2000/file/print on one). We
currently have a single DC in our domain and I want to promote one of the
other servers to a DC for backup purposes. The IIS box is out because it
hosts our public web page, which leaves me with the SQL box. I read that
DCPromo removes any local user accounts and am not sure of how this will
affect our SQL Server. It is currently using mixed authentication and starts
as a system account. Any constructive feedback is appreciated.>
> I manage a small Win 2k domain with 3 servers and about 20 users (IIS for
our
> website on one server, DC & Exchange on one, SQL 2000/file/print on one).
We
> currently have a single DC in our domain and I want to promote one of the
> other servers to a DC for backup purposes. The IIS box is out because it
> hosts our public web page, which leaves me with the SQL box. I read that
> DCPromo removes any local user accounts and am not sure of how this will
> affect our SQL Server. It is currently using mixed authentication and
starts
> as a system account. Any constructive feedback is appreciated.
--
For performance reasons, we generally do not recommend running SQL Server
on a domain controller.
Regards,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Promoting a SQL Server 2000 to a DC

I manage a small Win 2k domain with 3 servers and about 20 users (IIS for our
website on one server, DC & Exchange on one, SQL 2000/file/print on one). We
currently have a single DC in our domain and I want to promote one of the
other servers to a DC for backup purposes. The IIS box is out because it
hosts our public web page, which leaves me with the SQL box. I read that
DCPromo removes any local user accounts and am not sure of how this will
affect our SQL Server. It is currently using mixed authentication and starts
as a system account. Any constructive feedback is appreciated.
>
> I manage a small Win 2k domain with 3 servers and about 20 users (IIS for
our
> website on one server, DC & Exchange on one, SQL 2000/file/print on one).
We
> currently have a single DC in our domain and I want to promote one of the
> other servers to a DC for backup purposes. The IIS box is out because it
> hosts our public web page, which leaves me with the SQL box. I read that
> DCPromo removes any local user accounts and am not sure of how this will
> affect our SQL Server. It is currently using mixed authentication and
starts
> as a system account. Any constructive feedback is appreciated.
For performance reasons, we generally do not recommend running SQL Server
on a domain controller.
Regards,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.