upgrade SQL Server OS to Win2k03

MS SQL SERVER

    Sponsored Links

    Next

  • 1. SQL Server Management Studio install?
    Hi, I just setup a new server, Windows 2003 64-bit with SQL Server 2005 64-bit. How can I install the management studio on either my Windows XP workstation or another Windows 2003 server that's 32-bit? Can I install the management studio from the 64-bit media or do I need to get the 32-bit version? Thanks in advance, Linn
  • 2. Log On
    Is it possible to log on to two different servers from my CPU? If so how do I configure it? two different domains?
  • 3. Sql Server 2008 express deployment
    Hello, I have a application that I have made that requires Sql Server 2008 Express. How do I deploy express with my application. I also need to set the Sql Server service to Local System account with Interact with desktop selected.

upgrade SQL Server OS to Win2k03

Postby Elvyn Gutierrez » Thu, 09 Feb 2006 23:11:42 GMT

Hi. We have a SQL 2000 SP3 server that I need to upgrade the underlying OS 
from Win2k to Win2k03. This server has 3 partitions;  C: OS/Sql executables, 
D: Data (mdf) files  and E: Logs (.ldf) files. I don't plan to do a in place 
upgrade, I rather perform a fresh installation on the C: partition. If I 
perform a fresh installation of the OS and SQL, will SQL recognize the DB's 
on the D: and E: partitions. Any ideas on how to do this trouble free. I've 
heard that Win2k03 SP1 causes some problems. Is that true?

-- 
Elvyn Gutierrez
Pellerano & Herrera
MIS/Lan Manager 



Similar Threads:

1.Renaming SQL Servers and Upgrading OS

Two unrelated topics.

(One)
Any issues in upgrading the OS on a SQL Server from Windows 2000/sp4 to
Windows Server 2003?

(Two)
We are migrating to a new server, which will have to have the same name
since numerous applications point to it. I was originally planning to
install SQL Server after the "new" server had been given the "old" name; but
a quick look through BOL indicates that SQL Server will recognize the new
name on reboot. The only apparent tricks are to run sp_dropserver <old name>
and sp_addserver <new name> to clean up the sysservers table, and dropping
any remote logons, of which there are none in this case.

I am planning on creating users on the "new" SQL Server with the same SIDs
as on the "old" server; then physically copying .mdf, .ndf, and .ldf files
to the new server and attaching them. Of course, there will be full backups
made prior to this. Does this seem a rational approach.

Thanks,
     John


2.Upgrading OS from W2K to 2003 Server

When I run the 2003 server compatibility report on my W2K server running SQL 
2000 the report is showing SQL server 6.5. Yet when I ran select @@version 
in Query Analyzer it is showing SQL 2000. I don't feel comfortable upgrading 
the server OS to 2003 until I find out why my SQL is showing as SQL server 
6.5 instead of 2000. I am afraid it will disable my SQL server. Any ideas 
why and how to resolve the issue. 

Looking forward any ideas or solution on how to fix the issue. 

Ismael

3.Performance decrease after OS upgrade

We were running a 4 processor server with 8 GB RAM and 800GB hard disk
space on Windows 2000 server and SQL Server 2000.
Recently we have upgraded the server to 8 processor and added another
800GB. The OS was upgradded to Windows 2003 enterprise edition.
All the processor are 2.5GHz Xeon preocessors.

After upgradation the performance of the server has gone down from what
it was giving before the upgrade.

It seems that multiprocessing is not ocurring.

The model of the server is HP DL740

The OS is installed in a built in array(5i controller) of the server
and the SQL server is installed in a external array(6400 controller).

I will really aprecite if anyone can give any clue to improve the
performance.


Thanks in advance.

Taw.

4.Upgrading W2K3 OS on a cluster

We have a two node active-active cluster, DB11 and DB12 using GeoCluster and
SQL Server 2K.

I need to update the OS on DB11 from W2K3 MSDN to a W2K3 licensed setup.
When I tried to do this update for DB12, I moved all the groups over to DB11
and then did the update.  It was a disaster, the update died halfway (for
some reason a licensing update deletes and recreates all the Windows DLLs)
and I was forced to reinstall everything on DB12 and jump through some major
hoops to get clustering correctly configured again, 2 days later.

I am about to do this same upgrade for DB11 and I don't want the upgrade to
die like before.  I've done the upgrade on many machines and DB12 was the
only one to die like this.  As such I suspect it had something to do with
clustering.  Is there anything else I need to do differently this time?  I
would like not to evict DB11 and readd back later but I'll do it if I have
to.



5.Upgrade OS and hardware

Hi,  Our 2 node(active/active) cluster is running on an old machine and 
running SQL2000 and W2k.  We wanted to upgrade the hardware and the OS to 
W2003.  I am planning to setup the new hardwares with W2003 and SQL2000 and 
then moved the resources over to the new servers and then get rid of the old 
ones.

My question is, can different OS belong to the same cluster?  Will my plan 
work?

Thanks.

--Elmer

6. Access denied after OS Disk upgrade!?

7. OS upgrade to Windows2003 ?

8. Performance Hits within EM After Upgrading OS to Windows 2003



Return to MS SQL SERVER

 

Who is online

Users browsing this forum: No registered users and 93 guest