Yikes again. :) Veritas performs its backups for SQL using a "database agent" because otherwise the .MDF is held open by SQL Server and normal backups can't get at the file (unless they shut it down).
Instead of restoring the raw .MDF file, try doing a Veritas "database" restore (I'm not sure where you see it in Veritas). For ours, we select it under databases, and tell it which SQL Server to restore to, what destination database name to use, and just hit go. You might have better luck that way. -----Original Message----- From: Charles Nahm [mailto:[EMAIL PROTECTED] Sent: Thursday, December 23, 2004 10:39 To: SQL Subject: RE: .mdf file - please help this rookie Oops, sorry. I meant the MDF had been restored from a tape backup which was generated by veritas. I did the type thing and it was a bunch of gobbledeegook. The .mdf is about 400 MB. The reason why we think it might be sql7, is because in one of their folders, there is a folder C:\mssql7, but we don't know if this is a legacy thing or the current version. This has been a very messy process from the start and I appreciate your help Tim. Charles ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Silver Sponsor - RUWebby http://www.ruwebby.com Message: http://www.houseoffusion.com/lists.cfm/link=i:6:2083 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
