SQL Server 2000 compatible with Windows Server 2003?

[trichie]

Hi! Is MS SQL Server 2000 compatible with Windows Server 2003 Standard/Enterprise Edition? Is there a service pack available to make them compatible? Thanks for your help!

 

[NortonES2]

SQLServer 2000 SP3 is compatible.

-------------------------------

If it doesn't leak oil it must be empty!!

 

[trichie]

Thanks NortonES2! I have an additional question though. We are currently planning to migrate our system to Windows Server 2003. Problem is, when we try to upgrade to 2003, it first scans the system for incompatibilities and throws a warning saying that it cannot accept SP2 or lower. But we are apparently using SP3 already for SQL Server (so we're really unsure what SP2 Windows is talking about). So after installing Windows 2003, SQL Server is running okay. But, when we deployed our application, our application couldn't access the database. Looking at the error message, it seems that there is some error with the JDBC Driver. Which leads us to believe that there is some incompatibility with Windows 2003 and the driver. We are currently using JDBC Driver for Service Pack 2, Type 4. Is there a JDBC Driver for Service Pack 3? Or is there any other version we should download? Any thoughts? Thanks!

 

[mrdenny]

When running SQL 2000 on Windows 2003 you must install service pack 3 or 3a. Windows 2003 will not allow SQL 2000 to listen for incomming connections unless SQL SP3 or SP3a is installed.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[SQLBill]

we are apparently using SP3 already for SQL Server

But are you SURE? Check the version to make sure.
Run SELECT @@VERSION in Query Analyzer. It should return:
8.00.760 for SQL Serever 2000 with SP3. A higher 3 digit number at the end is also good. But anything lower than 760 isn't SP3.

-SQLBill

 

[mrdenny]

You can also use this on SQL 2000. It will give you more specific info.

SELECT 'SQL Server '
+ CAST(SERVERPROPERTY('productversion') AS VARCHAR) + ' - '
+ CAST(SERVERPROPERTY('productlevel') AS VARCHAR) + ' ('
+ CAST(SERVERPROPERTY('edition') AS VARCHAR) + ')'

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[trichie]

Hi! I ran the query and it returned 8.00.194, so I guess we were mistaken when we thought we were using SP3 already.

Thanks for all your help guys!

 

[SQLBill]

OUCH!! Version 194 is SQL Server 2000 with NO service pack.

-SQLBill

 

[SQLBill]

One other thing to be aware of ... SP3 or SP3a require a password for the SA account.

-SQLBill

 

[kk5]

We are planning to upgrade our Windows 2000 Advanced server which has SQL 2000 SP3, to Windows 2003 enterprise edition.
Just insert the CD for 2003 and do the upgrade, is that the way..Please let me know the steps to proceed, appreciate everyones help

 

[mrdenny]

kk,
I would never recommend upgrading a box. If at all possible purchase new hardware, then install the new OS on the new server, setup SQL, test it, then move the databases over to the new server, and turn off the old server.

If you can't do that, then I would recommend backing up the databases from the windows 2000 server, and formatting the machine, and installing Windows 2003 on it.

Any perticuler reason that you are planning on upgrading the database from Windows 2000 to Windows 2003?


Denny

--Anything is possible. All it takes is a little research. (Me)

 

[kk5]

Denny,
Thanks for the reply, the only reason we are upgrading, as we dont have funds to purchase new hardware, the only option left for me is upgrading.
Your suggestion was excellent regarding taking backup of all databases, formatting the machine and doing a fresh install, but will all the SQL logins would come back when we do a fresh install of SQL server and restore databases? Please let me know,

 

[mrdenny]

If you also restore the master database then yes. If you have jobs and alerts, then you will want to script them, or restore the msdb database as well.

Denny

--Anything is possible. All it takes is a little research. (Me)