Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...restoring a 2005 MSSQL database problemrestoring a 2005 MSSQL database problem
Previous
 
Next
New Post
4/11/2008 8:25 PM
 

O.k.  got a major problem.  I have a *.bak file of my database.  I changed servers..  Now I find that my new server is running mssql 2000  and it will not recognize the 2005 mssql database backup file. 

So..??????  Any idea's on how I can convert my 2005.bak file to a 2000.bak file...  Sounds impossible...

Will I have to totally start over again?  I sure hope not...

Can anyone at all help me,  or do this for me... or tell me I am in for a lot of work !!!

 

Thanks

 
New Post
4/12/2008 11:39 AM
 

Hi Msidfry,

You won't be able to use your .BAK file directly on the 2000 server.  The best you'll likely be able to do is to use the Import/Export wizard functionality to move your table data over.  If you have a direct connection between the two machines, then this process becomes much easier.

I do not believe you can use the Import/Export wizard to move over your programmable objects (SP, Userfunctions, etc).  You'll likely have to manually rescript these.

Sorry for the bad news, but hope this helps nonetheless!

Brandon


Brandon Haynes
BrandonHaynes.org
 
New Post
4/12/2008 5:58 PM
 

These folks have a backup tool which will script the entire database to SQL create and insert statements - including content - and this has been used to move from SQL 2005 to SQL 2000.

http://www.evotiva.com/

THe backupscript module, not backup native ...

I've not used it myself, but have eyed this product for some time. This might save you a lot of pain. You will have to go from a live MS SQL 2005 database, not a .bak file, I"m quite certain. So - you'd need to recreate an instance of your DNN site that is live on SQL 2005, install the module, and then use the output to create the SQL 2000 database.

 pmgerholdt AT hotmail.com - if you do not have a convenient way to get this up on an SQL 2005 instance, I might be able to help you get through this.


pmgerholdt
 
New Post
4/13/2008 6:46 PM
 

1. Restore your .bak file back to SQL2005.
2. Right-click the database and click "Properties"
3. Click "Options > Compatability Level"
4. Set Compatability Level > SQL Server 2000 (80).
5. Backup your database.
6. Restore to your SQL2000 box.

My guess is that "Compatability Level" is "SQL Server 2005 (90).  If I am correct by doing Step #4 you should be able to solve your problem.  I have not gone back to SQL 2000 compatability so we'll both learn something.

Good luck.

mikez

 
New Post
4/17/2008 1:59 PM
 

Mike:

This is an excellent idea! 

Msidfry:

As Mike seemed to indicate that he has not actually tried this in the field, please let us know if it rectifies your issue!

Brandon


Brandon Haynes
BrandonHaynes.org
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...restoring a 2005 MSSQL database problemrestoring a 2005 MSSQL database problem


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out