Sql – Attaching an MDF file without LDF file

Here are some notes (for SQL 2000) that might help. I've never tried these personally.

1. In EM create a DB with the same name as the original.
2. Stop the SQL service (instance).
3. Copy the old .MDF over the new one.
4. Start the service (instance).
5. DB will appear as suspect in EM.
6. Fire up Query Manager.
7. Connect to the running instance.

8. Put the DB into Emergency Bypass Status by doing the following:

   sp_configure 'allow', 1 
   go 
   reconfigure with overide. 
   
   update master..sysdatabases 
   set status=32768 
   where dbid=5    --check this ID is for your db 
   

9. Stop the SQL service (instance).

10. Delete the LDF.
11. Start the SQL service (instance).

12. Execute the following in QM:

    select dbid, status, name 
    from master..sysdatabases 
    dbcc rebuild_log ('dbname', 'full path and LDF name') 
    

13. Revert DB from Emergency Bypass Status by executng in QM:

     update master..sysdatabases 
     set status=16 
     where dbid=5 --Check this ID for your db 
    

14. Cleanup by executing the following in QM:

     sp_configure 'allow', 0 
     go 
     reconfigure with override 
    

Try:

mysql -u username -p database_name < file.sql

Check MySQL Options.

Note 1: It is better to use the full path of the SQL file file.sql.

Note 2: Use -R and --triggers to keep the routines and triggers of original database. They are not copied by default.

Note 3 You may have to create the (empty) database from MySQL if it doesn't exist already and the exported SQL don't contain CREATE DATABASE (exported with --no-create-db or -n option), before you can import it.