I'm a stupid man - Erase a database part

gunther
Member Posts: 15
Hi every body...
I'm a stupid man, but I need some help, your are my last chance...
I had a big database 20 Go (space use 17 Go) and (because I'm stupid) I have extend it with a little part (100 Mo) just for test...
And of course I have erase the fdb file of 100 Mo... because I forgot what it is... 8-[
Now my problem, I think you understand, that I can't open my database... it need the part I erase (I've try some recovery software, it not work for my file)
Help !!! If you know a issue !
Thank in advance... O:)
I'm a stupid man, but I need some help, your are my last chance...
I had a big database 20 Go (space use 17 Go) and (because I'm stupid) I have extend it with a little part (100 Mo) just for test...
And of course I have erase the fdb file of 100 Mo... because I forgot what it is... 8-[
Now my problem, I think you understand, that I can't open my database... it need the part I erase (I've try some recovery software, it not work for my file)
Help !!! If you know a issue !
Thank in advance... O:)
0
Comments
-
I hope you made a backup because I don't think you can recover that.0
-
Um, yeah... That would be bad. As bad as if you'd deleted the main 20G file...
Your only choice that I can see is if you have a backup, you can create a brand new database and restore the data from the backup. A long shot could be to check with Microsoft to see if an engineer of theirs could edit the database file with any special-magical tool and make it forget about the 100M portion, but this seems highly unlikely to work.Kristopher Webb
Microsoft Dynamics NAV Developer0 -
Captain DX4 wrote:Um, yeah... That would be bad. As bad as if you'd deleted the main 20G file...
Your only choice that I can see is if you have a backup, you can create a brand new database and restore the data from the backup. A long shot could be to check with Microsoft to see if an engineer of theirs could edit the database file with any special-magical tool and make it forget about the 100M portion, but this seems highly unlikely to work.
small thinking, you can try at least. Make a new DB with 2 parts, one of 20GB, one of 100MB.
Then rename that second one (100MB) to stay in place of deleted corrupted part of first DB.
Even if that works-out, I think you'll have some data-loss and maybe other problems. You can try at least, I say.
And Do not do that on your active DB. Make a copy and than test it...0 -
That is an interesting idea Phenno! I'd be interested to hear if it works.Kristopher Webb
Microsoft Dynamics NAV Developer0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions