Move data from 2000 to 2005

MS SQL SERVER

    Sponsored Links

    Next

  • 1. remote install SQL Server 2000
    when running a remote install the message "cannot find setup files verify UNC path ..." . The UNC path is correct and the access rights are granted, is there any other hidden problem with this?
  • 2. Trouble installing SS Express 2005
    Help! I have never had such a problem installing anything in my life! Does express operate only from a command line? After installing everything I think I had to install, all I have are Documentation and Tutorials, Configuration Tools and SQL Server Management Studio Express CTP. SQL Server Management Studio Express CTP, when clicked on does not fire (from Start -> Programs -> etc.) BTW, I got successful messages on all things installed. Something has to be missing! Any suggestions will be greatly appreciated! -- Sandy
  • 3. SQL Server 7.0 to 2000 conversion
    Can anyone tell me how easy (or hard) it is to convert a system from SQL Server 7.0 to SQL Server 2000 please? If anyone knows of any pitfalls to avoid or any tricks to makes things easier, those would be appreciated too. Also, sitting on top of the data is MTS - will this readily transfer too, or is there some process that has to be followed to move/convert it over? Lastly, there are some VB .COM components associated with all this. Again, are they able to be copied across okay, or does something need to be done to them? Regards, -- Kevin
  • 4. Renaming a SQL Server Machine... Whats Up??
    Okay, so I know with 6.5 and 7 and early on with 2000 there were issues with renaming the Server machine name on a SQL Server. You had to run the sp_dropserver and sp_addserver. Is this still the Case with SQL 2000 SP3a and SP4? I'm getting my Engineers telling me that its not an issue, though in all my experience and readings its still an issue. I'm asking as we are setting up our Training machines and they all have a Copy of SQL Server on them. We want to create one master Image and then send it out to all 12 machines. If we do that the original machine name will be renamed with the new station name once its pushed out. I've written a commandline app that you pass in the old server name and it runs the two stored procedures. Do I still need to do the drop and add or should I just reboot after the name is changes and go about my business? Thanks, Scott<-
  • 5. Sql Server 2000 Sp4 W3k 64 bits / Outlook
    Hello, I have a small problem with SQL Server 2000 (sp4) on Windows 2003 64Bits (Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)) My problem is my operators doesn't work ! When I try to send e-mail with test button i have this error Error 22022 : SQLServerAgent Error My server agent (services) is start with the good user (administrator and connected). My outlook 2000 run correctly. My SQLMail profil is the same that my exchange profil. And the test button there is OK What can I control ? Thanks Ben

Move data from 2000 to 2005

Postby Scott Townsend » Wed, 23 Nov 2005 01:54:50 GMT

We have 2 servers setup (2000 and 2005) and I can see them both in the SQL 
Management Studio.

What is the 'best practice' for migrating the data from the 2000 server to 
the 2005 server.

We have users, DBs and DTS Jobs.


Thanks,
  Scott<- 



RE: Move data from 2000 to 2005

Postby Sm9lIGZyb20gV0k » Thu, 24 Nov 2005 04:11:21 GMT

For databases, I'd suggest running Microsoft SQL Server 2005 Upgrade Advisor. 
 That will give you a heads up as to any migration problems.

You can backup or detach on SQL Server 2000 and restore or attach on SQL 
Server 2005.  SQL Server 2005 will automatically upgrade the database.  (Of 
course, you CANNOT move the database back to SQL Server 2000.)

Haven't dealt with users or DTS jobs yet.

Joe





Similar Threads:

1.Moving data from 2005 *back* to 2000?

Good morning!

Can anyone suggest possibilities, after upgrading a database from 2000-2005, 
to move data back to 2000 in a DR type situation?

We want to upgrade, but would really like a mechanism to rollback to sql2k 
in case "bad stuff" happens performance or data wise.  (if data corruption 
is the problem, we obviously do not want to roll the data back).

Log shipping won't work from 05-00 of course, and on my local box, it 
doesn't appear as if I can even copy data via the DTS objects from 05-00?

Anyway, if anyone has any suggestions...

Thanks in advance!

Derrick 


2.Move RS 2005 databases from SQL 2000 to SQL 2005

3.Moving from 2000 to a 2005 Cluster

Hey All,

We have SQL Server 2000 in our production environment and we have a
brand spanking new cluster that has more CPU power and RAM than our
current server. The issue I have is how to move the data. We have 10
Databases, most are small, but we have a few that are 5 to 9 GB and
one that is over 100 GB.

I've already loaded SQL Server 2005 SP2 on the cluster for testing
etc.

My goal is to reduce downtime, and my stress, when we go live with the
cluster. My fall back plan is, backup the databases, copy the backups
to the cluster and restore them on the cluster.

I had a thought of installing SQL Server 2000 on the clusters and log
ship the databases to the SQL 2000 instance on the cluster, since I
can't log ship from 2000 to 2005. Then when go live day comes, I just
need to restore the existing logs, recover the databases and detach
the databases from 2000, then attach the databases to the 2005. From
what I know this is doable, but has anyone done this or something
similar? Are there any gotchas?

Thanks

Dave Ott

4.move DTS package from SQL Server 2000 to 2005

5.How to move DTS from 2000 to 2005?

We have a new  machine with a fresh install of SQL2005. We have
restored some of the DB's from the SS2K box, now I need to move some of
the DTS to SS2005. We really are not ready to change our DTS to the new
SSIS so we would like to continue using DTS on 2005 for a little while
until we are ready to chnage our DTS to SSIS. I have read some articles
on the net where it suggested to download the DTS designer components
which I did as we will still need to edit the DTS in the 2005 box.

However I am not sure what the next step should be to bring over the
DTS from 2000 to 2005. Our DTS on the 2000 box are stored in
(Location:SQL Server ) however if I need to I can save them as
structured storage file.

Can anyone please help me with the next step?

Thanks

6. moving a db from 2005 to 2000

7. Move to different server SS 2000 to SS 2005

8. Moving from 2000 (and 2005) to 2008



Return to MS SQL SERVER

 

Who is online

Users browsing this forum: No registered users and 28 guest