Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Is it possible to move database from sql server 2005 to server 2000 ..?? Expand / Collapse
Author
Message
Posted Wednesday, January 7, 2009 10:09 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, April 27, 2010 1:12 AM
Points: 133, Visits: 48
Actually I have developed the project using sql server 2005 as a DB. But now the client wants to go with sql server 2000 only ........
and now i want to move my DB to ita lower version ....... so how can i do this
without causing any effect to the data and to the constraints in the DB

plzzz help me out to find the way........its urgent you can see it....

Thanks
Vaibhav
Post #632097
Posted Wednesday, January 7, 2009 11:17 PM


SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: General Forum Members
Last Login: Friday, October 24, 2014 11:52 AM
Points: 9,294, Visits: 9,484
Script the metadata from 2005, apply the scripts on the 2000 server. Then BCP out the data from each of the tables, then BCP them in to SQL 2000.

-- RBarryYoung, (302)375-0451 blog: MovingSQL.com, Twitter: @RBarryYoung
Proactive Performance Solutions, Inc.
"Performance is our middle name."
Post #632122
Posted Wednesday, January 7, 2009 11:25 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: 2 days ago @ 6:05 AM
Points: 40,258, Visits: 36,681
To add on to what Barry said, there is no way to take a backup of a 2005 database and restore it on 2000, nor is it possible to detach a SQL 2005 database and attach it to SQL 2000. The file structure is different, the system tables are different.

And before anyone suggests compatibility level, that just affects the T-SQL parser and the query processor, controlling how commands are interpreted. It does not affect the structure of the database file in an y way.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #632126
Posted Wednesday, January 7, 2009 11:43 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Tuesday, September 23, 2014 8:08 AM
Points: 2,365, Visits: 1,846
I hope you have'nt used any of the new features in SQL 2005 which will require code changes. If you have used you will need to make code changes.

"Keep Trying"
Post #632136
Posted Monday, February 8, 2010 2:01 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, October 13, 2014 12:44 AM
Points: 7, Visits: 195
I had the joy doing this little exercise last year. There is nothing to complex with this tasks. It is just @#$# work.
Post #861482
Posted Monday, February 8, 2010 12:41 PM


Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, March 14, 2014 9:11 AM
Points: 12, Visits: 237
I have done this few years ago.It's not hard as everyone thinks.I used SQL compare from redgate.

"First, create a new database on the SQL Server 2000 instance using Enterprise Manager, SSMS or writing a CREATE DATABASE [databasename] query.
Launch SQL Compare and choose your SQL 2005 database as the source and specify the empty SQL 2000 database as the target.
SQL Compare will produce a script to CREATE all objects in dependency order, and use syntax that is compatible with SQL Server 2000. Where possible, new features such as CLR assemblies are filtered out because they are incompatible with SQL Server 2000. Sometimes this is not possible, for instance if a stored procedure relies on a CLR function. Since the function cannot be created, the stored procedure cannot be successfully scripted. Analyzing your databases for these conditions first is recommended." from Redgate website.

Thanks,
Rohan
Post #861978
Posted Wednesday, February 10, 2010 7:40 AM


SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, April 13, 2011 9:52 PM
Points: 29, Visits: 29

Hello

What I have used is the Microsoft SQL Server Database Publishing Wizard , you can download it from the MSwebsite, it will generate a file with the T-SQL scripts for the objects in your database.
You can also include the data!

Then you can create the database in SQL 2000 and run the file in Query Analyzer and that's all.

However you need to be careful because if you're using some SQL 2005 features in your code (like Try-catch error in Stored Procedures) that won't work for SQL 2000

Hope this will be useful for you!
Post #863243
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse