renaming mdf files consequences

renaming mdf files consequences

Post by bert » Sat, 05 Feb 2000 04:00:00

SQL Server 7.0

Hey all :
I recently renamed db's (single user >> sp_renamedb >> multi user)
on a certain server, but they
maintained the old mdf database name.
Is there a safe way of changing the name of the file ?
Are there any consequences ?
I tried just detaching and renaming the mdf file then reattaching...
This gave me some errors.  I left the whole thing...
Don't have the luxury now...
The Server's mdf files are a mess and hard to keep track of...


1. clone database from 1 mdf file to multiple .mdf files (.mdf and .ndf)

I need to replicate a 26GB database.  The source database has only 1
logical name and 1 physical file (26GB .mdf file).  Unfortunately, on
my target server I don't have one big file system.  I manage to
combine space by create a new database with multiple files.  But
restore fails because I don't have the same file configuration.  Has
any one successfuly done this type of clone?
I'd love to hear a different approach.

2. hypercard as a CAD Databse/databsase

3. consequences of renaming server with SQL 2K

4. 'Hard Question' Update Problem

5. Renaming the MDF file

6. Oracle Sqlreportwriter Problem

7. Consequence of renaming table for triggers ?

8. Looking for UNIX databases

9. Consequences of limiting size of Data file and log file Newby

10. Tempdb.mdf and other *.mdf files??

11. Tempdb.mdf / other mdf files ????

12. Move all tables from a .ndf file to the .mdf file and eliminate the .ndf file

13. How to Convert .DMP file into .MDF file