SQL2000 EE on W2003 AE

MS SQL SERVER

    Sponsored Links

    Next

  • 1. Set seperate Log/Data file locations during install
    I have a new SQL Box built with 3 drives, with the following intended usages: C: OS & Prog Files D: Log Files E: Data Files During the SQL install process you are allowed to specify the location for all data files but there is no way to specify one location for log files and a second for data files. Without specifying the 2 locations during the install, master/model/tempdb all ended up with their log and data files on the same drive and I have to go through the long process of detaching and reattaching them. Is there any way around this problem? -Dan
  • 2. server rebuild
    Hi I'm not sure exactly how this has happend but I've managed to lock myself out of SQL Server 2000. I think it maybe because I deleted the BUILT-IN/Administrators. What is the best approach to repairing or reinstalling the SQL Server? Is there any other way to get back in ie resetting the sa password? Many thanks Jez
  • 3. Downgrade from Enterprise Edition to Standard Edition of SQL 2000
    Hello, does anybody of you know about a step-by-step guide describing "downgrade" from Enterprise to Standard version of SQL 2000? Thanks in advance Karel
  • 4. Server options problem
    I am running SQL-Server developer Edition version 8.00.760 on a laptop running XP professional. I just reinstalled SQL-Server and SP3 and now I have an odd problem: when I set server connection options, specifically SET ARITH ON from the Properties dialog in the Enterprise Manager, I see the configuration value checked. When I click on run-value I don't see it set, so I stop the server and restart it from the EM. After it restarts, it still does not have the option set. Server options are not sticking for some reason. Any ideas or explanations as to why I cannot set the options from the EM? Any suggestions, hints, explanations welcome. -- Rich -
  • 5. default instance in SQL-
    Hi all, First time setup for SQL. My scenerio is: I had two SQL databases to setup. (third party packages). So, I wanted to prepare ahead of time and this is what I did: I installed C: sql server 2000 then I added two names instances and pointed data to d: drive. Then I found out that both the sql databases keep all their data in a seperate folder where their program files are.(don't use the sql \data folder) The first database has it's own sql engine so it doesn't install in the sql2000 tree.(It doesn't use the sql2000\named instance data folder for its data) I removed the named instance using windows add/remove but it left the sql named instance tree their with the subfolder called binn. My question is can I delete that named instance tree and all subfolders if I am not going to use it? My next question is : do you have to have a default instance setup? My second database is a named instance also but I have no default instance?

Re: SQL2000 EE on W2003 AE

Postby Dejan Sarka » Fri, 06 Feb 2004 20:44:04 GMT

On Win 2003 you need SQL 2000 SP3, otherwise it won't work.

-- 
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com








Re: SQL2000 EE on W2003 AE

Postby Tibor Karaszi » Fri, 06 Feb 2004 20:46:34 GMT

It depends on how you are going to migrate. In general, SLQ Server doesn't like to switch service
pack levels for the system databases around. And this is what is going to happen if you, for
instance, take a backup of master on the sp2 machine and restore it on the sp3 machine. You might
want to test, but I prefer to have the same level...

-- 
Tibor Karaszi, SQL Server MVP
Archive at:  http://www.**--****.com/ 







Similar Threads:

1.SQL 2000 EE & W2003 EE Cluster

Hi,
I'm new to SQL, but learning fast! I have 8 GB Ram on each node in my cluster and I'm running one instance of SQL in an Active / Passive cluster mode. In my Boot.ini file I'm using the /3gb switch and I would like to configure the SQL server to use a max of 6 GB Ram. I've been running like this for about eight months
Is the change I need to make only in the SQL enterprise Manager? And should I do it on the Active Node or the Virtual Server? Do I need to remove the /3gb switch and configure any other switches

sp_configure 'show advanced options', 
RECONFIGUR
G
sp_configure 'awe enabled', 
RECONFIGUR
G
sp_configure 'max server memory', 614
RECONFIGUR
G

Thanks
Rodne

2.Win 2k AE, SQL 2k EE, Clustering after 1 node failed after a hardware death

Hi,

I got a problem with a cluster with SQL 2000 EE.

Had two servers, Win 2k Adv Ed., one of them died. 
Failover to node 2 worked fine.

Bought some new hardware, installed Win 2k Adv. Ed., SP4, 
MSCS.

I EVICTED the old server form the MSCS console from node 2.

I did install the new server with the same computername 
and IP adresses then the old, now dead, server.

When I try and run SQL 2k EE, I can't seem to install my 
node. All seems well in Cluster Admin console. I see my 
two nodes, the resources are all active on node 2 since 
the failover.

When I start SQL 2k EE setup, it asks for my Virtual 
Server, to which I answer with the name of the virtual 
server on node 2 (should that be what I need to do?)

My questions:

1- I should see the Quorum and my Data partiton from my 
Fiber Array on my new server, right? Problem is, I don't 
see the partitions. That's a problem, right?

2- Can someone please tell me what are the choices I got 
to make during the SQL 2000 EE installation? 

First - Virtual Server as the choice, and the name of my 
clustered virtual server for the answer. NEXT

Second - Upgrade, Remove or Add? Or ADVANCED?

Third - Going for ADVANCED at #2, only choice here is 
MAINTAINS A VS FOR FAILOVER CLUSTERING

Fourth - Ask for an IP, I got 1 choice in the bottom box, 
whihc is the IP of my virtual server. DO I need to enter 
anything, or just click NEXT?

Fifth - In thie Cluster Management window, I see my node 2 
as a configured node, and I need to add some more. The new 
node, the server I am installing, is "UNAVAILABLE"... 
What's wrong? Never got further than this.


Thanks for the help.

P. Carignan
 XXXX@XXXXX.COM 

3.Rolling Upgrade of SQL2000/W2000 cluster to SQL2000/W2003

Hi All,

Could someone out there please point me to a good guide to complete a
rolling upgrade of a Windows 2000 SQL Server 2000 2 node cluster to Windows
2003 SQL Server 2000 cluster?

I have seen the live meeting by MS on the topic, but it covers only 2 slides
on a rolling upgrade and this is what I am looking to do.

Any help would be greatly appreciated as I have been testing for the past
few days and have always received the same error detailing an ODBC
SQLDRIVERCONNECT failed errors. The actual SQL Server is starting but it
seems the MSCS service runs this connect for the Is Alive function and can't
connect so stops the service.

The only way I have managed to get the upgrade to work is to uninstall the
SQL Server cluster, Upgrade the MSCS cluster then reinstall SQL Server again
on the cluster, of course this means all my DB's are gone and my settings
also.... Hence the request for points on how to perform the rolling upgrade.

Cheers,
Des

4.SQL2K with w2003 EE cluster active/passive step by step guide

Hi.

Someone has a step by step guide to install and configure the w2003 EE 
cluster and to use SQL2k failover cluster active /passive solution? 

Thank you

5.sql2000 setup fails on w2003

Hi,

My end goal is an active-passive sql2000 cluster running 
on 2 windows 2003 ee nodes.

I have installed the os, got the san drives recognised 
and setup the cluster.

then i run sql2000 setup:
specify virtual,name,ip
specify default instance name
specify drives install options
setup then warns about unsigned infs, i choose yes to 
continue

setup then states "performing operations on the cluster 
nodes, this may take a few minutes"
setup eventually fails after approx 30mins

i have since removed node2 from the cluster to make it a 
single node install
specified the servername in client network config util
copied the cd locally to run setup
created an msdtc resource

all with same result

any help would be appreciated

Rob

6. SQL2000 backed by Veritas BackupExec9 on newly migrated W2003 Serv

7. sql2000 sp2 on w2003

8. SQL2000 backed by Veritas BackupExec9 on newly migrated W2003



Return to MS SQL SERVER

 

Who is online

Users browsing this forum: No registered users and 37 guest