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 ??
Is there a tool available (or planned) to migrate SQL Server 2000 database to SQL Server 2005 ? I came across this (http://www.timespring.net/TS_TD_SQL05offer.htm?track=NL-464&ad=524331) but are there any other tools ?
Has Microsoft planned anything of its own for this ?
i'm migrating my dbase from SQL 2000 to SQL 2005..i've restore the dbase to SQL 2005..but what about the SQL job?..do i need to create them back in SQL 2005?..how to do that?..1 more question..how to migrate DTS from SQL 2000 to SQL 2005?..i've ActiveX script in my DTS...really need help from all of u.. thanks
I am planning to migrate sql server 2000 databases to sql server 2005(sql server 2005 in a separate box) .I have few questions regarding the migration:
1. Do I have to run Upgrade wizard on 2000 even though I am not upgrading my sql server?
2.Which other databases do I need to move in addition to the user databases. (i.e. do i have to move any system databases?).
3. What do I need to do to move sql server logins with the password to the new machine?
I've got the responsibility over a small SQL server with 8 Database and approx. 100GByte data online. Most database are used and need to be available 24*7*366. Also a number of local data transformation packages are defined and used on a regular basis. Furthermore a number of third party applications rely on this database.
My question if it is worth the effort to migrate this to 2005? I know there are all kinds of nice migration wizards but do they really work? What if one of the 3rd party apps don't like 2005?
Love to hear both good and bad experiences migrating -> 2005 .
Hi Everybody, does anyone know how I can migrate SQL 2000 data to SQL 2005 database? I'm trying to create an application that will connect to SQL 2000 database using VS2003 and transfer data to SQL2005 database but it doesn't seem to work. Any suggestion is greatly appriciated. devmetz.
Dear All, at present all our servers are running with sql server 2000. we are planned to upgrade to sql server 2005 standard edition. what is the approach i need to follow? can i directly go for installation of sql server 2005, and then use copy database wizard? this is a production environment, and we even not give 5 min of downtime. please help me in this regard
Arnav Even you learn 1%, Learn it with 100% confidence.
Hi all, in my current environment, I have a single server SQL 2000 setup that's being replaced. I'm in the process of installing a new SQL 2005 cluster with the thought of taking advantage of 2005 mirroring and clustering, but have a few questions.
1. My thinking is that I can migrate my 2000 databases to 2005, but leave the databases in 8.0 (2000) mode. Are there any issues with this? I know they won't take advantage of the 2005 performance boost
2. Some of the apps don't support 2005 yet so I need to leave them in 2000 mode until they do. Is SQL 2005 fully backwards compatible with a SQL 2000 database?
3. Will mirroring work on SQL 2005 with a database that is still in 2000 mode?
I plan to migrate a SQL 2000 instance with everything in it to another SQL2000 server, and eventually in the future to SQL 2005.
I've pretty much figured out how to migrate everything execept the linked server configuration (there're many linked servers configured in the old server with different security credentials). I'm wondering if there's way I can save the linked server configuration and restore it to the other server.
I've got about 2 months worth of daily databases created in SQL Express 2005 for a pilot project, which the client is converting to a purchase. Unfortunately they're using SQL Server 2000 and I can't figure out how to migrate the databases to the older version. All my searching turns up how to do it in the expected direction.
Any pointers to how or where to search appreciated.
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.
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.
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).
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.
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.....
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?
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.
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?
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?
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!
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.
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.
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 all, i have written a small checklist for my upgrades of databases from 2000 to 2005 servers. I was hoping you can take a look and see if im missing something.
TIA
1.Create backup of 2000 Database to a file group a.Full Backup b.Overwrite Existing Media Set c.To File with Extension .BAK d.Locate backup on DEV @ X:SqlServer_DataMSSQL2K5BACKUP e.Make sure Backup File Name has _for_2k5_migration.BAK at the end 2.Create Database on SQL Server 2005 System on DEV a.MYSERVERDEVELOPMENT2K5 b.Data files go to : X:SqlServer_DataMSSQL2K5DATA c.Log files go to : X:SqlServer_DataMSSQL2K5LOG d.Set Compatibility to 80 (SQL SERVER 2000) 3.Restore Backup to 2005 From File a.Options Tab – Check Overwrite existing database b.Once Restore is completed set compatibility mode to 90 (Sql Server 2005) 4.Script all Logins to 2K5 a.Go into 2000 server Security -> Logins b.Script as CREATE TO Clipboard c.Open query on 2K5 DB d.Paste and run (Database must be installed on 2K5 first)
i have not done anything about maintenece plans - is this okay as it is or am i forgetting / not knowing anything else!
First off, thanks to all for taking the time to read and respond to this question of mine. Greatly appreciated.
Let me explain my current scenario followed with the question. We currently have our VB application written and working at various client sites on SQL 2000. We did received a number of request on upgrading to SQL 2005. We did some preliminary testing in-house on SQL 2005 (backed up the 2000 database and restored on 2005 which worked just great). It is also my hope that technically, everything should work just fine since 2005 is backward compatible to 2000.
Is anybody aware of any issues with taking a 2000 database and getting it to work on SQL 2005 without any mods?
