February 12, 2013 at 6:34 am
GilaMonster (6/18/2012)
All I can suggest is contact the author and/or MS Press and complain/ask for a working DB.
I am also facing the same problem....
February 12, 2013 at 6:49 am
I was able to come up with a workaround.
If you delete the log file and revise the script you can attach the database.
I would provide the script but I lost it when my hard drive went bad.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 12, 2013 at 6:53 am
Welsh Corgi (2/12/2013)
I was able to come up with a workaround.If you delete the log file and revise the script you can attach the database.
I would provide the script but I lost it when my hard drive went bad.
i have deleted the Log file and i am using the GUI and not script to attach the primary file but now its saying that info and also saying that the Log file is missing
February 12, 2013 at 6:58 am
GilaMonster (6/17/2012)
When you attach, explicitly remove the ldf in the dialog (if they didn't provide it). Or use CREATE DATABASE ... FOR ATTACH_REBUILD_LOG
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 12, 2013 at 7:04 am
GilaMonster (2/12/2013)
GilaMonster (6/17/2012)
When you attach, explicitly remove the ldf in the dialog (if they didn't provide it). Or use CREATE DATABASE ... FOR ATTACH_REBUILD_LOG
Yes the Script was useful ... i have deleted the Log file which it is referencing internally and executed it worked.. Thanks for u Guys 🙂
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply