Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
microworks
Starting Member
3 Posts |
 Posted - 2006-06-01 : 15:27:16
|
| Recently I decided to start using DotNetNuke, which uses an SQL Server database. My webhoster offers SQL Server 2000, and I was able to install and run DNN successfully there. However, I wish to have a local copy of DNN on my PC with the same contents as is on the web. It means that I need either to convert SQL Server 2000 database to my local SQL Server 2005 Express database, or vice versa.Although I programmed in (Visual) FoxPro for many years, I am new to SQL Server and I am overwhelmed by the vast number of new terms. Can anyone tell me in simple English, how to perform the above mentioned conversions? My webhoster allows me to backup the SQL Server 2000 database in an *.sql file, but how shall I convert this file into an SQL Server 2005 Express *.mdf file? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-06-01 : 15:41:28
|
| To upgrade from 2000 to 2005, you can simply backup the 2000 database, then restore this file to your 2005 server. SQL Server handles the upgrade process during the restore.Tara Kizeraka tduggan |
 |
|
|
microworks
Starting Member
3 Posts |
Posted - 2006-06-01 : 16:09:44
|
| Thanks for the answer, but can you be more specific?By making a database backup in my webhoster's administration, I have obtained a file with .SQL extension. Now, how shall I "restore" this file to my local SQL Server 2005 Express so that the existing local database named DotNetNuke (physically DotNetNuke.mdf) is overwritten or updated with the contents of the .SQL file? In MS SQL Server Management Studio Express, if I right-click the DotNetNuke database and select Tasks/Restore/Database..., I cannot select a .SQL file as a restore source. Shall I use another method? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-06-01 : 16:17:59
|
| Is the .SQL file really a database backup though? SQL files are typically files with commands in it such as SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, ... Typically, a backup file has an extension of bak or bkp. So how was the SQL file created?Tara Kizeraka tduggan |
|
|
|
microworks
Starting Member
3 Posts |
Posted - 2006-06-01 : 16:40:19
|
| As far as I can say, the database could be reconstructed from the .SQL file contents. In its header, there is mentioned that the following items were exported to the file: drop-commands, table-schema, table-data, stored-procedures and comments. Looking at several random places in the file, I would say that by running (somehow) the .SQL file, it could create the database. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-06-01 : 16:48:41
|
| I don't understand why they generated this type of file for you. But if it includes everything that you need, then you can run it in Management Studio (SQL Server 2005 tool).Tara Kizeraka tduggan |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-06-02 : 02:00:19
|
| register the 2000 server on the ssms, then right click the database and copy database to the sql2005 server--------------------keeping it simple... |
|
|
|
|
|
|
|
|
DB conversions - SQL Server 2000 x 2005 Express