Good Morning!
I am beginning the process of moving SQL 2000 databases to SQL 2005 cluster.
Has anyone already did this and is there anything I should know?
We plan on leaving the SQL 2000 database up during this process and granting read only at the time.
I am nervous about this as this is a high profile database in our dept.
I don't even know if I know where to begin!
Any suggestions are truely welcome!
Thanks,
/P
Hi
We are planning to upgrade the SQL Server in our production environment from SQL Server 2000 to SQL Server 2005. This is a 4 Node cluster environment with 3 Databases on 3 Virtual instances. The main requirement is to achieve this with no/minimal downtime.
Could you please suggest or direct me to any documentation for the best practices used to upgrade such an environment?
Thanks
Priyanka
I have upgraded our test server and on non cluster production machine. My next server is a cluster and I don't have a test cluster server. Do I upgrade the active node and that is all or am I going to need to fail it over and upgrade the other node.
Also the prerequesite for the upgrade advisor is .net 2.0 I am going to up that on each server one at a time but I am only going to add the upgrade advisor to one node is that ok.
I read the SP1 documentation and it clearly states only patch the active node and do not patch the inactive nodes.
We're upgrading a SQL Server 2000 cluster (Active/Passive) running on Windows 2003 Server 32 - bit Standard to a SQL Server 2005 Cluster running on Windows Server 2003 64-bit Enterprise. Our existent cluster's databases are residing on SAN. We can't purchase new hardware and we have no spare hardware. We also need to move from Windows 2003 32-bit Server to Windows 2003 64-bit Enterprise Server at the same time. We want to keep downtime to a bare minimum.
What we were thinking was the following steps... Anyone try this?
1. Break the link between the servers. Or should we just evict the passive node?
2. Install a fresh copy of windows 2003 64-bit server on one side along with SQL Server 2005. While this step is running, the active node would still be live on Windows 2003 32-bit Server and SQL Server 2000 serving our customers.
3. Bring the active server down.
4. Create new cluster on the newly upgraded server and assign the same cluster name and IP as the original one.
5 Bring the luns from SAN to the newly upgraded server and initialize SQL Upgrade
6. As a final step, the old active node will be rebuilt, we would install a fresh copy of windows 2003 64 - bit server on it and sql server 2005. At this point we would bring it back into the cluster and the cluster would be complete again.
Thoughts?
I have a production failover cluster running SQL Server 2000 at SP3that I want to upgrade to SP4. I do not have a test failover clusterto test with so I need the install on the primary server to work thefirst time. Per the information I have I just install the patch on theprimary server and it will install both on the primary and on thesecondary.However, I remember when I did the initial install and it failed. Thefirst problem traced to the fact that the install uses temporary filesunder the profile of the installing administrator and the id had neverlogged into the second server so the install failed on creating thetemporary file. The was a second problem that related to an OS featurethat had to be off for the install to work.If anyone out there has done this upgrade and remembers encountering aproblem and its fix/workaround I would appreciate a head up warning.Thank you-- Mark D Powell --
View 1 Replies View RelatedHave recently performed an in-place upgrade of a 2 instance sql cluster from 2000 to 2005. The upgrade process went relatively smoothly. However, I am running into problems installed sp2. The first problem that I run into is that I have resrcmon.exe locked. I can click next, which is fine, but once I get past that point I get stuck during the installation process. I am updating DatabaseServices and Integration Services. It gets stuck on 'Awaiting first complete passive cluster node SQL-Test'. Does anyone have any ideas?
Thanks,
Tim
Hello there,
We have about a dozen SQL server 2000 Enterprise Edition servers in house. Our goal is to set up a cluster SQL server 2005 and consodiate the existing dozen servers to a few servers for easy manage and maintainence. So there are 3 things that we want to accomplish:
1. upgrade to SQL server 2005,
2. Consolidate existing servers
3. Make a cluster server to get high availability
But I'm sure what's the right order to acheive them. To upgrade each server to 2005 and then move them to cluster server? or set up the cluster server in 2005 and restore existing dbs to the cluster server. upgrade first or cluster first? upgrade first or consolidate first? pros and cons? upgrade or backup/restore? What do you recommend? We have lots of stored procedures, views and triggers, DTS packages and some replications. Any insight will be greatly appreciated.
-Jessie
Current set-up: three node cluster running Windows Server 2003 Enterprise Edition SP2 with two instances of SQL Server 2005 Standard Edition SP2.
Virtual node 1: Standard Edition, default instance, Database Engine only
Virtual node 2: Standard Edition, named instance, Database Engine, Analysis Services and Integration Services
Physical node A: Prefered node for virtual node 1
Physical node B: Failover node for both virtual node 1 and 2 (thus having two installations of Standard Edition)
Physical node C: Prefered node for virtual node 2
We started off with this set-up because there was no need for Enterprise features, and SQL 2005 supports failover clustering with two nodes in Standard Edition. Saved a bundle of cash, so everybody's happy. Now we need to run a solution on virtual node 2 that requires Enterprise features in Analysis and Integration Services, so an edition upgrade is required on virtual node 2. I have done some research and found several edition upgrade examples, but none that match the above scenario. We are running production on these machines, so I can't risk experimenting with command line options, I have to be right the first time.
Is it possible to mix two editions of SQL Server 2005 in one cluster? Can I upgrade virtual node 2 to Enterprise but leave virtual node 1 at Standard? What procedure do I have to follow to upgrade all three components of virtual node 2 to Enterprise Edition on both physical node B and C?
Any ideas will be greatly appreciated.
During the installation of Adding node to a SQL Server failover cluster(On passive node) getting error like.. The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.We  run the below commands but didn’t get any resolution & got the same above error .
Â
1<sup>st</sup> Method…
1. Open console command (Run->CMD with administrator privileges).Â
2. net stop winmgmtÂ
3. Rename folder %windir%System32WbemRepository to other one, for backup purposes (for example _Repository).Â
4. net start winmgmt
2<sup>nd</sup>Â Method..
1. Disable and stop the WMI service.
a) Command : - sc config winmgmt start= disabled
b. Command : - Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â net stop winmgmt
2. Run the following commands.
a). Command: Winmgmt /salvagerepository %windir%System32wbem
b). Command: Â Winmgmt /resetrepository %windir%System32wbem
3. Re-enable the WMI service
Command:Â Â Â Â Â Â Â Â Â sc config winmgmt start= autoÂ
Last command to run after above steps
4. Command:Â Â Â Â mofcomp "%programfiles(x86)%Microsoft SQL Server100Sharedsqlmgmproviderxpsp2up.mof"
File not found Error for above command.
Can I build a cluster by adding the cluster service, then the SQL instances, then add the other nodes and their passive SQL instances?I would lean to building the cluster first, the add the SQL instances.
View 4 Replies View Related
We're upgrading a SQL Server 2000 cluster (Active/Passive) running on Windows 2000 Server to a SQL Server 2005 Cluster running on Windows Server 2003. We can't purchase new hardware and we have no spare hardware. We also need to move from Windows 2000 Server to Windows 2003 Server at the same time. We want to keep downtime to a bare minimum.
What we were thinking was the following steps... Anyone try this?
1. Break the link between the servers.
2. Install a fresh copy of windows 2003 server on one side along with SQL Server 2005. While this step is running, the active node would still be live on Windows 2000 Server and SQL Server 2000 serving our customers.
3. Restore a copy of a backup from the active production side to the node we're upgrading and at that point we would bring the active node down, switching the active node to be the newly upgraded server.
4. As a final step, the old active node would now have the link to it broken, we would install a fresh copy of windows 2003 server on it and sql server 2005. At this point we would bring it back into the cluster and the cluster would be complete again.
Thoughts?
Friends -
Need your help and guidence for doing upgrading SQL Server 2000 Cluster to SQL Server 2005 Cluster.
Let me explain my current environment.
1. Currently SQL Server 2000 Cluster environment is running on Windows 2000 Server we need to upgrade this to SQL Server 2005 on Windows 2003 Server. >>> Production environment.
My Plans:
1. On Testing Environment Install SQL Server 2000 cluster on Windows 2003 Server and do a restore of databases from the produciton environment.
2. Upgrade In-Place from SQL Server 2000 Cluster to SQL Server 2005 Cluster.
My doubts
1. Can i install SQL Server 2000 Cluster on Windows 2003 Server. Is it possible or not.
Please advise me and correct my steps.
Cheers
VSH
We wish to upgrade our hardware of two sql boxes onto a single cluster. One of our databases will not run on sql 2005 and so I wanted to know if it is possible to run an instance of sql2000 and an instance of sql 2005 on the same cluster.
This is possible or would it cause as a lot of problems?
Hi
I have a cluster with 4 sql server 2000 instances and would like to upgrade 2 of these to sql server 2005 - is there any document or list of things to ensure I do
Thanks
Hello,
I have a project where I have to upgrade SQL 2000 to 2005. When we are upgrading we are going to move to new server so server name will change. Most of our applications have a hard coded connection string. Applications are developed with Classic ASP, .NET 1.1 and 2.0 as well.
Now the question is what is the best way to do this? Changing all the connection string will be a very painful task as we have many applications.
Can anyone suggest a way where we can achieve this without changing all the connection strings?
Thanks in advance.
Tareq
what are some of the issues that we might face while upgrading from SQl 2000 to SQl 2005? Actually I have to create upgrade plan for path from MS 2000 to MS 2005.
Any suggestions will be appreciated.
Thanks
Hi,
I was wondering if anyone could point me in the right direction for upgrading from SQL 2000 to SQL 2005?
I was under the impression that it was as easy as following an upgrade path after popping in the CD, but I realized it's not.
I'm a Systems Administrator who has installed both version in stand alone systems, but never tried an upgrade.
Thanks for your help.
Hello,
I would like to upgrade sql server 2000 to sql 2005. So Can I install the sql server 2005 on the same server where sql 2000 is already running and then use the database upgrade wizard. Or should I install the sql server 2005 on a different server.
Thanks
I have a sql 2000/2005 side-by-side install on a single server. I right-click a sql 2000 database, select All Tasks, and the Copy Database to upgrade a sql 2000 database. In the "Copy Database Wizard" I see the message:
"To use the detach and attach method SQL Server Agent must run under an Integration Servicers Proxy account that can access the file system of both the source and destination servers."
1. What does that mean?
2. I decided to click "Finish" in the wizard, and the database copy seemed to work fine. Whaterver 1) means does, by default, the SQL Server Agent already run under this "Integration Services Proxy" account. (Rememberr the upgrade process did work).
TIA,
barkingdong
Hey Guys,
Looking for some type of solution on this issue. I'm going from SQL2000 to SQL2005 and I run the upgrade advisory tool and all and I'm going through the procedures of getting our SQL server updated to SQL2005, when I attempt to run that analyzer to take a look at how well the migration will go. I get a timed out error message on the fallowing.
ORDERBYORDINALS
FTCATPROPITEMCOUNT
OLDSYSTEMTABLES
DROPSYSOBJ
HOSTIDRETURN
FTPROPS
QRYGOVCOSTLIMIT
FTCATALOGNAMERESTRICTION
SPCONFIGURE
INVALIDCHAR
OPENXMLWITH
XPAGENTPROXY
UPDATETEXT
SPHELPTRIGGERNEWCOL
DISKINIT
SYSPERFINFO
DEPRECATEDSP
OLDDBCC
ORDERBYALIAS
Exact error message and its always the same for each entry.
"Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding"
Any help in this are would be greatly appreciated, all other issues have been resolved I'm just stuck on this and I don't want to upgrade until the advisory tool gives me the ok to.....
Thanks in advance.
All,
I am looking for upgrading SQL 2000 databases to SQL 2005.Has anybody got a detailed plan /Documents for doing so?.
Thanks and Regards
Avijit Macker
I am in the beginning of upgrading a SQL 2000 DB on a Small business server to a 64 bit 2005 DB on a new box. Is my best method of upgrading to use the "copy" DB function in 2005? If so, what do I need to do to install the management tools on the 2000 box - since this is a 32 bit edition, and I have the 64 bit media?
View 1 Replies View Related
I got a requirement to upgrade only One SQL 2000 to SQL 2005 server. i did check that there are only databases in this server along with Linked server. I am looking for a best practice document for SQL upgrade and any thoughts or experience any one has faced during upgrade.
Other question is what about if there is a DTS on the server. right now on this particular server there is no DTS but in coming weeks i may need to upgrade other server which is having DTS as well. I have worked alot on SSIS packages but want to see if DTS will be converted to SSIS packages or i will have to manually do it.
Thanks
Hi,
We have 2 .net 1.1 applications using Microsoft SQL Server 2000 Enterprise Edition. To connect to database we are using nHibernate 0.6 for one application and Microsoft Enterprise Library Data Blocks Ver 1.0 in another.
We are planning to upgrade SQL servers of both applications to SQL 2005 Enterprise edition and retain .net 1.1 framework. Are nHibernate 0.6 and Microsoft Enterprise Library 1.0 data blocks compatible with the SQL 2005? Are any upgrades required for these as well?
We ran SQL upgrade advisor report on these applications, there weren't any changes to table/ stored procs suggested. Could that mean that the existing table design and stored procs are compatible with SQL 2005?
Thanks in Advance,
Abhijith Bharadwaj
Hi all,
I just ran sql upgrade advisor and got the following message:
"You can use SQL Server 2005 tools to edit your existing DTS packages. However, upgrading or
uninstalling the last instance of SQL Server 2000 on a computer removes the components required
to support this feature. You can retain or restore these components by installing the special
Web download, €œSQL Server 2000 DTS Designer Components,€? from the Microsoft Download Center
before or after you upgrade or uninstall SQL Server 2000."
I do have several DTS packages in my sql server 2000 database. does that mean if I upgrade my current 2000 database to 2005, those dts will be gone. But I can download sql server 2000 dts deginer components on our new sql 2005 database server before I upgrade. Then when I restore my sql 2000 database on our new 2005 server, eveything would be OK? I am not sure if my understanding is correct.
My advisor is on my local computer and I am running analysis against a remote database(on our intranet),€œSQL Server 2000 DTS Designer Components,€? should be intalled on my local computer or remote database server? what steps I should take in order to retain my dts package or transform it into something else?
can you shed light on me?
Thanks.
Betty
I am going through upgrading our current installation of SQL 2000 to 2005. When I install 2005 it doesn't seem to upgrade the server, but only installs the server tools. Do I need to completely remove 2000 in order to upgrade? Thanks!
View 4 Replies View RelatedI am trying to upgrade a SQL Server 6.5(Cluster) to SQL Serevr 7.0 (Cluster)..I already have an intsllation of 7.0(On a Cluster),so this means that 6.5 and sql 7 are on seperate cluster's ,if i try to upgrade from 6.5 Cluster to 7.0 Cluster is asks me to uncluster 6.5 and 7.0 is this correct ,assume i cannot break the cluster then what???.. what is the best way i can achieve this functinality.....
thanks in advance
Jack
I have a Cluster environment that has SQL 2000 Enterprise installed. I would like to install SQL 2005 Enterprise as well. What should I watch out for. Do I need to specify a named instance for the 05 install, setup is giving me the option and does see the 2000 instance? Is there a document that walks through this installation?
Regards
Where can i find some reference material on how to upgrade to 2005 in a replicated environment please?
does anyone know what order i need to tackle the servers, is it likely to be the same as the Service Pack process?
cheers
Hi all,
Recently, I upgraded one of our database servers from SQL 2000 to SQL 2005. At the moment, all the databases are in 80 compatibility mode. I upgraded them based on the false pretenses that I could perform online reindexing right off the bat. Apparently, that isn't the case, and it requires switching to 90 compatibility. My question is if I switch to 90, will all indexes be invalidated/unusable? Or will I be able to switch to 90 and perform the online reindexing right away with no downtime?
We have a few 24/7 production VLDB's in the mix (one of which is on this newly upgraded server), and only reasonable downtime is possible. The largest window of downtime I have is about 10 PM - 5 AM with prior notice.
The upgrade was performed using SAN-based LUN's with a detach/reattach.
Thanks,
Matt
Hello
Server Details:
OS => Windows Server 2003
SQL => SQL Server 2005
Client Machines:
OS => WinXP sp2
SQL => 2000, 2005 express
The developers at work connect remotely to the server. Some of them have the "client SQL 2005 express" and others are using "SQL 2000"
Over the next week I plan to upgrade all the developers to 2005 Standard.
I have performed an upgrade of '2005 express' to '2005 standard' and encountered no problems. However I have no experience upgrading the 2000 client.
Can anyone suggest a strategy (fresh install/upgrade)or highlight any pitfalls that I should avoid.
Thanks in advance for any help/suggestions offered.
Regards
Toby
Initially, the articles I read suggested that doing an "in place" upgrade is the simplest path, with the drawback that if something goes wrong, I'll have to re-install 2000. And that migrating is more difficult since I'll have to recreate all the logins , security, replication ....
Then I saw a series of posts saying migration is the best ... backup & restore (or detach, reattach) the DBs to a new instance of SQL 2005. What about the systems DBs, such as MSDB and the DTS packages ?? Also, If I migrate to a new instance of SQL, how will I re-establish the connections from other servers ? They are replicating or DTS-ing to ServerA, but now SQL2005 is on ServerASQL2005 (Same server, different instance.
In the scale of things, we have fairly simple environments, although our Production database is almost 300 Gig.
If I install a new instance of SQL 2005 on my SQL 2000 server, and migrate everything from 2000 to 2005, I now have 2 instances: ServerA and ServerASQL2005. All my other servers are referencing the original instance name of ServerA. How do I resolve that problem so that communication between the other servers will still work ??
I've installed a test instance of SQL 2000 on a test box. I want to try the In-Place upgrade to 2005. I installed 2005 on the test box also, but have been unable to see how to perform the upgrade. I thought running 2005 setup again would prompt me for an instance name .... but it just tells me 2005 is already installed. I must be missing something simple.
View 5 Replies View Related