6 réponses à ce sujet

[sea-]

Due to a sudden system crash which has rendered me unable to boot into Windows directly, I've had to install Windows on a separate hard drive and use that to try to back up everything I need.

Unfortunately, I can't seem to figure out a way to easily back up everything regarding the Dragon Age Toolset, especially the database.  When I try to run the Toolset, I receive an error saying it cannot connect to the database, and I can't perform a backup using the backup utility - it ends up giving me an error message regarding permissions.

I have yet to try to reinstall the Toolset because I'm afraid that might wipe out the existing database, although considering it's on another drive, it may not.

Would disconnecting the hard drive with my data on it, and then installing the Toolset be a smart thing to do?  I imagine I'd end up with a situation of two separate databases, in which case, how could I use the old one for backup purposes?  In that case, do I want to just do a builder-to-builder export and make a DADBDATA file, or run the Backup.bat file in the Toolset directory?

This is a pretty dire situation.  I need to reinstall Windows on my old drive to get my system set up again, but I don't want to lose months of work.

Modifié par sea-, 29 mars 2011 - 09:25 .

[sea-]

Not even a nibble? I've tried pretty much everything on the Wiki but can't get the Toolset to properly recognise the old database - at best I can get it to display all the listings, but everything is blank and set to read-only when I try to open it.

[sea-]

I've come across the option of importing the database information manually using SQL Server Management Studio. However, it seems as if there's no effective way to add the existing database information - I keep getting miscellaneous errors when I try to do X or Y, and apparently the Express version I'm using lacks an Import option, which might make the process a lot easier.

[sea-]

Let's make this simpler: I have the DAODB and dbbak folders from the previous installation left over, along with the MDF, LDF and BAK files. Should I theoretically be able to get my old content back, or am I missing something?  The closest I have gotten is being able to view my old module, without being able to access its resources.

I haven't seen any information suggesting that the Toolset requires any more than these files, so I'm close to simply reformatting at this point and figuring it out later (provided someone more knowledgable than me lends a hand).

Modifié par sea-, 30 mars 2011 - 02:06 .

[Apolyon6k]

Unfortunately I can't help you there but I hope you get your work back and don't have to redo it

[Proleric]

I just went through a similar trauma.

Slightly different, in that I was able to make a new instance on a different laptop, then load a B2B extract from the old disc.

What's your ultimate objective? Would it be possible to reinstall Windows on the old disc? Or is the new disc going to become the definitive c: drive?

My instinct in the latter case is to back up everything on the old disc, try installing the toolset on the new disc, then restore the .bak on the new disc. (My hardware support guy says you can just copy the .mdf and .ldf files if they're more recent, but I never tested that).

I don't know enough to be certain that will work without screw-up, so you'd need to be confident about the regression plan.

[sea-]

I tried to get the database open using the Toolset for quite a while last night. As I said, the best I could do was to get the game to recognise the old database, but none of its entries were accessible... possibly a permissions error, but unfortunately the limitations of the Express version of SQL Management Studio mean that I couldn't import the existing database info the new one, and I'm not even sure that would help.

I've already reinstalled the operating system over the old drive, though I still have the raw database files left over just in case someone comes in to suggest a solution.  I think at this point I'm going to just start over... frustrating, but considering I have all my level layouts, it will take a lot less time to put things back together. I guess the lesson is that I should make a builder-to-builder file and database backup every time I make a significant change... which is a shame, because I actually was planning on doing that before my computer decided to end itself.

Oh well, thanks for the help all the same, you guys. At least I know I'm not alone in my suffering.

Modifié par sea-, 30 mars 2011 - 04:42 .