If it's an .MDF, then it's not a Veritas file.  How big is the .MDF
file?  Also, try using a DOS prompt (yes, old fashioned), and do a "type
TheFile.MDF" and see what comes out.

Is it possible that it's because they gave you a SQL7 MDF, and SQL2k
doesn't like it?  (speaks to the backup/restore discussion earlier,
which translates as it goes)


-----Original Message-----
From: Charles Nahm [mailto:[EMAIL PROTECTED] 
Sent: Thursday, December 23, 2004 10:06
To: SQL
Subject: RE: .mdf file - please help this rookie

Thank you Jacob.  I tried this and I got a pop up that says, "this file
is
not a valid SQL database".  I have a feeling the data we received is a
Veritas backup of their full system.  I don't think they would have
stopped
SQL server to make this backup.  Does that make a difference and is
there
anything we can do?

Thanks very much Tim and Jacob for the quick replies,
Charles

> -----Original Message-----
> From: Jacob Cameron [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 23, 2004 10:39 AM
> To: SQL
> Subject: RE: .mdf file - please help this rookie
>
>
> Copy to your SQL server, right click in enterprise manager (on the
word
> database) and try to attach (under all tasks) the database to your
server.
> If it is SQL 7 or 2000, it will be imported.  You may have to change
where
> the files point though.
>
> I have transferred files many times.  As long as SQL Server was
stopped on
> their end when they copied the file the file should be fine.  Try
> attaching
> it, then let us know if that worked.
>
> Jacob
>
> Jacob Cameron
> Blue Lantern, Inc.
> (972) 226-9595
> [EMAIL PROTECTED]
> http://www.blue-lantern.com
>
> -----Original Message-----
> From: Raster, Tim [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 23, 2004 9:25 AM
> To: SQL
> Subject: RE: .mdf file - please help this rookie
>
> Yikes.  MDFs are the data files in their native format.  It is not
advised
> to try to move those from server to server.  It would be better
> for them to
> create a backup of the database, which copies the contents into a
> (usually)
> .BAK file.  Then you would "restore" this .BAK file to an empty
> database on
> your server.  SQL2k can read SQL7 .BAK files just fine.
>
> All he has to do is right-click on the database in his Enterprise
Manager,
> hit Backup, and tell it where to put the .BAK file.  Simple.
>
>
> -----Original Message-----
> From: Charles Nahm [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 23, 2004 09:34
> To: SQL
> Subject: .mdf file - please help this rookie
>
> Hello, I am an SQL rookie.  We have received an .mdf file from a
> client that
> is used in conjuction with a photo hosting website.  Judging from data
we
> received, we think it could be MSSql7.  We are using MS Sql 2000.
>  We cannot
> be sure of the version as the client doesn't know either.
>
> Are there any conversion tools available, or in the case of a
> possible file
> corruption, are there any SQL database recovery specialists that
> we can hire
> to get at this data?
>
> Thank you very much,
> Charles Nahm
>
>
>
>
>
>
> 



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Special thanks to the CF Community Suite Silver Sponsor - RUWebby
http://www.ruwebby.com

Message: http://www.houseoffusion.com/lists.cfm/link=i:6:2079
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/6
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:6
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.6
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to