Mar 13
Sharepoint 2003 and 2007 Database Exporter
Hi,
Some months ago I was experimenting with Windows Sharepoint Services and found out that my machine was not powerfull enough to run Windows 2003, SQL Server and Sharepoint at a decent speed. I had data in Sharepoint I wanted to keep so I did an SQL Server backup of the database. I tought that I would re-setup everything easily after a machine upgrade… I was wrong! I never succeeded to restore the database backup in a running Sharepoint environment (I learned the hard way that I should have used WSS backup utilities instead of relying only on a database backup).
From that moment I decided to explore how Microsoft stores its data within Sharepoint. I found out about Docs and UserData tables and I thought I could develop a little tool to extract my data. In the mean time I discovered the Sharepoint Database Explorer from James Edelen. I was happy that I would’nt have to code it myself
… The tool is nice, but it didn’t allow me to export custom lists and metadata…
As a learning experience, I decided to build an exporter program. It happens that I find it usefull in a couple of situations… So I decided to share in case anybody would have the same needs than I had!
***** Updated (2010-02-01) *****
Features (v1.1.0.3):
- Export attachments with the same directory structure than original document library. Thanks to Amrit for providing the code.
***** Updated (2009-01-28) *****
Features (v1.1.0.2):
- Bug fix regarding the extraction of document librarie items. Some files where not “seen” and not exported (thanks to Finn Olesen for discovering the problem)
***** Updated (2008-02-21) *****
Features (v1.1.0.1):
- It is possible to preview the pending version (checked-out and saved, but not yet checked-in) of a file.
(on both: WSS 2.0 and WSS 3.0) (see this screenshot)
- Bug fix regarding the extraction of document librarie items when files are checked-out.
Features (v1.1.0.0):
- Connects to either Sharepoint 2003 or Sharepoint 2007 database structure (automatic detection).
- It is possible to preview the version history of a file and to export individually a previous version of a file.
Features (v1.0.0.1):
- Connects to Sharepoint 2003 databases directly
- Does not rely on a working Sharepoint environment… it only connects to the database
- You can preview the list contents (see screenshots)
- It is possible to export individual files from the preview window.
- You can export custom list attachments and document library files
- You can export metadata
Metadata is exported in an xml file. For attachments, you have the choice to export them in a folder or to embed them in the xml.
Known issues:
- When a list is not customized (kept as-is — no additional fields added), Microsoft does not store the column mapping (Sharepoint field name mapping to SQL Server column name). They probably store them in a resource file so its faster to retrieve than querying the database. For us, that means we have to hardcode the mapping for each list type (Custom List, Contact List, Discussion List, Calendar, etc.). For this reason, some list types may not export well.
Screenshots:
- Preview tab – Attachment history
- Preview tab – Custom List
- Preview tab – Listitem with attachment
- Export tab
- XML sample
Download (Latest Version):
- Sharepoint Database Exporter (v1.1.0.3) – Binaries Only
- Sharepoint Database Exporter (v1.1.0.3) – Sources and Binaries
- License (New BSD License)
Add-On:
- XSL Transformation to convert output into an HTML Table
(use this to import to an older Excel spreadsheet that does not have native XML support)
Download (Previous Versions):
- Sharepoint Database Exporter (v1.1.0.2) – Binaries Only
- Sharepoint Database Exporter (v1.1.0.2) – Sources and Binaries
- Sharepoint Database Exporter (v1.1.0.1) – Binaries Only
- Sharepoint Database Exporter (v1.1.0.1) – Sources and Binaries
- Sharepoint Database Exporter (v1.1.0.0) – Binaries Only
- Sharepoint Database Exporter (v1.1.0.0) – Sources and Binaries
- Sharepoint 2007 Database Exporter – Alpha 1 – Binaries
- Sharepoint 2007 Database Exporter – Alpha 1 – Sources and Binaries
- Sharepoint 2003 – Database Exporter (v1.0.0.1) – Binaries Only
- Sharepoint 2003 – Database Exporter (v1.0.0.1) – Source and Binaries
Final Notes:
This work is done on my free time, but I encourage to post bugs and feature requests so I can take a look when I’ll have time.
Also if you made your own modifications, feel free to post them back so I can integrate them, of course giving you the credits for what you’ve done…
100 comments
Version 1.0.0.1 is now available. It contains a fix of a bug that was giving an error while exporting document libraries that contained sub-folders.
My bad… I wanted to make to code cleaner before posting the first version to the site and I introduced a regression bug
.
A big thank you to Merijn Boom for reporting the bug and suggesting a fix.
Pascal.
I finded a problem with export attachements from lists in this version (1.0.0.1). When I try save attachement from list I have error:
System.Data.SqlClient.SqlException: Invalid column name ‘Content’. at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteScalar()
at Sharepoint2003.DBExporter.Data.DatabaseConnector.ExecuteScalar(string statement)
at Sharepoint2003.DBExporter.SP.SPDatabase.GetFileContent(StringdocumentId)
at Sharepoint2003.DBExporter.UI.ExplorerForm.PreviewFileListSaveAsMenuItem_Click(Object sender, EventArgse)
This tool is built for Sharepoint 2003.
This is the typical error when trying to connect to a Sharepoint 2007 database using this tool because Microsoft has changed its database structure.
If you’re really using Sharepoint 2003, feel free to write back.
Pascal.
I am currently working on a modified version for WSS 3.0. It is not ready to be published on this site yet. It currently works only for document libraries. But if any one is an urgent need, just drop me a message and I could send it by e-mail.
You can expect to see it appear on my blog in the coming weeks, depending on how much interest I receive. It’s summer here and the sun is shining so I’m much more motivated to ride my bike than to sit in front of the laptop…
I have been asked a couple of time to send the version for WSS 3.0. For now, the development is stalled because I don’t have much time. All I have is a hacked version that is only able to export documents from document libraries (which is 99% of what is usually asked for).
If you are in desperate needs of it, than here is the link of the Sharepoint 2007 Database Exporter ALPHA release:click here
*** Edit: See main post — current release now supports both WSS 2.0 and WSS 3.0
If it doesn’t work for you, or you need to export other types of lists, feel free to send me a comment and I’ll see what I can do.
Note to Max: I tried to send it to you by e-mail, but I either mistype your address or you had a typo in it (it keeps bouncing). Unfortunately, I cannot verify because I’ve been to fast on the delete button
.
Pascal.
Pascal…
Thanks for the link, I’m sure I probably typed something wrong.
I tried the Alpha Exporter and it works great. No issues what so over. Pulled out about 800 documents totaling 500MB.
You’d know better since you’ve worked on it, is it possible to extract the documents using the same folder structure that was on the site?
If you have the source for this version, I can play with it in my spare time, but like you, there isn’t much of that.
Great job on the program though. Saved our butts.
Well, I’m always happy to hear “success stories” about my little tool…
I put the alpha version in a hurry and didn’t take the time to publish the source code yet. But I’ll do.
For the directory structure, yes it could be possible to reproduce the same directory structure. I’ll put this in my todo list… It is still possible possible to “discover” the directory structure if you exported the metadata with the file. When exporting the metadata, the application generates an xml file containing the original location and its exported location. Based on the original location it would be possible to write a script to regenerate the directory tree…
Thanks so much for posting the alpha. Saved our shop a large amount of recovery time after an unexpected db upgrade (caused by another app).
Thanks for taking the time to work on this and for sharing!
The alpha works very well, did save us a lot of hastle after sharepoint services 3 simply did not do its job any more.
Thanks a lot!
I would be very interest in the source for the WSS 3.0 binaries when they are available. I used the binaries with success.
Hey thanks for putting the time into this open source project… I used the 2007 alph version to grab the file… Really appreciate it…
I urgently need to recover some deleted documents and associated metadata.
Thanks to your fabulous tool, I now have an extract with attachments embedded in the xml file. Now for the silly question: How do I import this into SharePoint?
Andy:
I’ll try to package it as soon as possible.
Kevin:
I was planning to build an importer that would use the sharepoint API to upload the files and metadata. Unfortunatly, I had no time for that. I built custom programs for specific situations for a customer but I can’t release the code since they are the owners.
What is your version of Sharepoint? I’ll see what I can do.
Pascal.
Pascal:
Appreciate your help. Not sure which version number is more relevant to you so here’s both. WSS 11.0.7969.0 IIS 6.0.2.8117 – WSS+SP2+KB924881.
Cheers
Kevin.
Ok that means you’re using WSS 2.0 (aka Sharepoint Services 2003). I was wondering if you were using the modified version for Sharepoint 2007.
Pascal.
Hi,
Do you have any guidelines / instructions / apps for importing data into Office Sharepoint 2007 (latest patched version) after it’s been exported using your tool?
Great app, btw…
Cheers,
Dave
Hi Dave,
It depends what you want to import… All of the feedback I received (with 1 exception) was from people exporting files from document libraries with no special metadata attached to them. That is easy to import using the new Sharepoint environment (ex: Explorer view of a document library).
Do you have metadata to import? If so, I’m currently working on an importer. I plan to build the core with no graphical user interface so it can be available sooner.
Pascal
For those who were interested into having the Sharepoint 2007 Database Exporter source code (for Alpha 1), I finally had the time to package the code and place it on this site for download: click here for source code
This alpha version is, in fact, the version for 2003 patched to work on SP2007. In the next release, the database exporter will be able to export both SP2003 and SP2007.
Pascal.
This is a fantastic tool but just out of curiosity can you tweak it to allow export of specific pages? I’ve got a list on a production server where the EditForm.aspx and DispForm.aspx pages have suddenly stopped working if passed the “ID” parameter for the list item – if the parameter isn’t specified the pages load fine.
Even Reset to Site Definition doesn’t work.
My only hope seems to be to check these files as they are inside a backup…
Hi,
This is a great utility!
I don’t suppose you could possibly tweak it so that we can export pages and forms?
I’m in desperate, desperate need of a utility that’ll pull the EditForm.aspx, DispForm.aspx and NewForm.aspx from a backup…
Tim: I think it is possible but I would need the version of Sharepoint you’re using.
WSS 2 (2003)?
WSS 3 (2007)?
Pascal.
You are great. I was in a big trouble in the past 3 weeks and your tool worked perfect. I’ ve just changed my table name AllUserData to UserData on the database and there is no modification except that. Thank you so much.
the export notifies : 7 records retrieved, exporting, completed.
The folder remains empty. what is the extenssion of the file, is it a hidden file, or something else? Thanks
In the export tab you choose how the metadata is exported (not exported or exported as xml) and how attachments are exported (not exported, embedded within the xml of metadata or as a separate file). Depending on the options, you may have to select a file name or a folder location.
In most situations, people exports document libraries and are not interested by the metadata. So the common options are:
Metadata export format = “none”
Attachments export format = “linked file”
Export to: c:\temp\myfiles
There is nothing exported has “hidden”. The extension used for attachments is the same as the original file stored in Sharepoint.
Is this answering your question?
Cool utility but I have a case it does not cover. I had a need to extract a document that was checked out and user did an undo check out by error. The document was saved in the DB backup but the tool only extracts the last saved document in a check-in state.
Interesting case… I remember that I explored the possibility of displaying (in the preview tab) the history of each file and it wouldn’t be hard.
I may end-up with something to help you in a day or two.
Pascal.
Hi Bertrand,
I just published a new version of the Sharepoint Database Exporter (v1.1.0.0) that may solve your problem.
Pascal.
Bertrand:
I finally built a test environment so I can add the requested feature. Version 1.1.0.1 does now support exporting checked-out file version on a WSS 2.0 and WSS 3.0 database version.
Pascal.
Pascal,
Are you interested in adding command-line capabilities to this? It works well, actually I find it a bit faster and easier than the Edelen tool. I think directly accessing the db was a good move.
For nightly exports, however, I’d like to automate it. In our company we are still using a giant network drive for all of our docs, so a few of us are trying out Sharepoint as an alternative but management is requiring us to still keep copies on our network drive. So an exporter that I can script to would be useful.
Thanks for making this available,
Tim
Thank you so much for posting this. I spent hours trying to restore a file and had tried the Edelen tool, but recieved errors. This was so easy and quick to use!
Any updates on getting the folder structure preserved? I appreciate your continued efforts with this tool.
Hi Mark,
This feature seems to have slip out of my hands last time I did an update… I guess I’ll find some time to implement it within the next week.
Pascal.
Hi Tim
I realized that I never answered your question…
This tool is intended for last-chance data recovery. It is not meant to be part of a backup strategy because I cannot garanty 100% success result. The tool is extracting data from database that only Microsoft knows all the details.
Based on its purpose, I don’t see much use of being converted to command-line. If you still wanna use it that way, it would be pretty easy to ask a developer to do it since the database access code is isolated from the user interface.
Pascal.
Hi Pascal,
I was experimenting with your excellent tool. I have a MOSS 2007 DB that contains elements from a SPS 2003 migration. I think I only can view elements with your application that were loded to the WSS Content DB after the migration. Or at least were openend and saved after the migration. Is there a way to also get access to the “hidden” data? For example I can see/extract about 200 files (40 MB) but there must be data over 1.4 GB…
Thanks for answering!
Best regards,
Martin
Hi,
I never experienced this problem but I never tried for a database upgraded from SPS 2003 to MOSS 2007. Also, this tool was developed for WSS sites, were you trying to export portal data? (ex: data stored within areas)
Pascal.
I appreciate your efforts as well, but would be interested in some method like Tim indicated above of somehow automating an extract. We too need to have the documents pulled from the database for users. If your tool can’t accomplish this does anyone know of a solution for having this done nightly?
Hi,
This tool is not intended to be used on a working environment since it is a “last resort” recovery tool. If Microsoft changes its internal structure it will stop working.
I found a tool made by krichie (http://blog.krichie.com) that is able to import/export a document library from the command line. I didn’t check the source code and didn’t test it yet but I’m pretty sure it should answer your needs.
krichie published the application with the source code here:
http://www.codeplex.com/SPIEFolder
Pascal.
As a side note, I will adapt my exporter to respect the original directory structure soon (as asked by Max before).
When completed, the SPIEFolder tool from krichie (see previous comment) should allow to re-import documents into libraries of a working environment. That will greatly help recovering files.
Pascal.
Pascal,
Awesome tool. Top marks. I’m current completely restoring a SharePoint 3.0 site as the stsadmin tool was not clear that I had to backup each top level site (I was converting from Windows Internal Database to SQL 2005)
So, I was wondering – do you have any scripts or programs that can easily convert the XML code of the custom lists into a Excel Spreadsheet? I just wanted to check with you first before writing my own.
Thanks in advance;
Gareth
Hi Gareth,
If you use Microsoft Excel 2007 (and probably Excel 2003 will also work), you just have to open the xml file into Excel. If you have an older version, the easiest method is to convert the xml into an HTML Table or CSV file.
I Added an “Add-on” section into this post with a link to an XSLT file that perform this transformation.
Pascal.
Pascal,
Oh ok couldnt be any easier – thanks alot for that – i’m running 2007 so it shouldnt be any issues. I wasnt looking at the problem from a simple enough approach
Thanks again,
Gareth
Sorry, one last question although I think I already know the answer to this: Is there any way of preserving the Custom Views on the lists and/or any calculated fields?
Thanks
Gareth
As you probably expected, currently there is no way to export the view definitions and formulas of calculated fields.
Pascal.
Thanks for that – I suspected as much. Irrespective your tool just saved me alot of trouble. Thanks a LOT.
Gareth
Hi,
Have worked on developing the webparts in sharepoint 2003 and .net1.0?
I have certain clarifications needed on this ..if u can help me it wud be gr8.
Sudha.
Thank you. You saved my life..
Thanks for this, but I was hoping it could recover a CSS file in the Style Library. It exports only a listing of the files in the style library. Can you help?
Thanks
You can choose to export a listing (meta data), the files (attachments) or both.
In the export tab, choose:
filename: [path to your xml file]
Export to: [name of folder to export files to]
Since you only want to recover a single file, you can “browse” to that file (in the Preview tab) and right-click on it to “save as” locally.
(see this screenshot)
Tell me if you succeed or if you still cannot recover your file.
Pascal.
Does this app export all versions of a document?
Yes this application is able to do it but only one by one.
If your intention is to export a complete list/library with all the versions of a file, this application cannot do it currently. I find it interesting and I take note of the feature. That won’t be hard to implement.
Pascal.
Hello, need your help.
I have a shearepoint db with 76GB i tried to open it with the “Sharepoint database exporter” and it does, althoug it gives some errors in some folders. when it gets to the file 85528 shows an error:
system.data.sqlexception:i/o error (bad pag id) detected during read at offset 0×00000d502d0000 in filr c:\……xxx.mdf’
at system data sqlclient.sqldata reader.read()
at sharepoint.db explorer.ui.explorer form.loadpreviewlist(listnode node)
at sharepoint.db explorer.ui.explorer form._sitestreeview_after select (object sender.treeview event args e)
What is the problem there are some files missing… how can i export the tree folders insteade of only the files.
Please help.
Looks like your database is corrupted, do you have a backup?
To export all the files of a document library, just use the export tab instead of the preview tab. For now the tool can only export files (not directory) but if you also export metadata it would be possible to reconstruct a folder structure from metadata.
Note: It is in my todo list to be able to export directory structure as well.
Pascal.
Hello,
I do not have a backup. This is it and i realy nead it…
How can you tell that the db is corrupted?? can it be fixed? When do you preview to be able to export directory?
Oscar Rocha
I deduced your database is corrupted based on the error you received. This is a native SQL Server IO error. I suggest to do a google search and see what can be done to repair the database. Perhaps it is just a SQL Server index that is corrupted and recreating it would fix the issue (I am not a DBA).
Right now you can export a whole document library using the export tab. I don’t know when I’ll have time to modify the program to be able to retain directory structure.
Pascal.
the problem with the export document is that it exports the documents but if there are sevaral docs with the same name it replaces them.
Oscar Rocha
Hi,
It should not reuse the same name. There is specific handling for that (and I just confirmed by verifying the code). If it does overwrite, than that’s a bug.
What it does if it finds a file with the same name already exported: it appends a number next to the name.
Example (myfile.txt):
1st: myfile.txt
2nd: myfile (2).txt
3rd: myfile (3).txt
When you export, you can export metadata. It will generate an xml file. From this file we can make the relationship between its original location (folder) and its exported name.
I know it is not ideal and I will try to put up some time to make the necessary modification to retain directory structure as soon as I can.
Pascal.
Hi.
When I try to find my data, it takes only a small part of them, not all of them, what can be wrong there.
Finn
Hi,
There may be multiple reasons. The first I see is because of unexpected data resulted in an error. Do you receive an error message? What type of list are you displaying? Document Library? Is happening to all of your lists? What version of Sharepoint are you using?
Pascal.
Hi.
I am using a WSS 3, there is no errors messages. it is my Document libery “Shared Documents”
If there is no error message, it may be unexpected data-handling resulting of records being excluded in a database table join, for example.
Is this problem occuring from all document libraries you have on this installation? Why are you using the sharepoint exporter? because of an environment crash? if so perhaps there is a database corruption.
Thank you for sharing.
Hi.
Yes I have a crash on the Wss it was the config database, If I am using the SQL Server management ST Express it can see all the datas under the dbo.AllDocs, but only some off them in “Sharepoint DBExporter” some of the data it can see in Sharepoint DBExporter is in the same lib. as the data it can not see. Hope it gives a sense, I do not really know how I can see the base is destroyed otherwise.
It is quite difficult to diagnose without data sample or a way to reproduce the situation.
Do you have a .NET software developer handy that could check with the Sharepoint DB Exporter source code? Or is it possible to have access to the problematic database (or a copy)?
Pascal.
Hi. I can but a copy of the database on my webpage then you can get it from there.
I can send you a email when it is on the site.
so plz send my you Email.
hi, can any successor here tell me how to use these tool? i need to get back my content for my partially upgraded sharepoint database. i reinstall WSS 2.0 and 3.0 to use back the existing partially upgraded database but not success. now what i have with me is only the partially upgraded database because i didn’t make any backup copy of it before this.
Thank you so much for this tool, you really really really really really really saved my butt!
Hi, Andy. how you did it? any application needed? i need back my data urgently. pls help on this.
Thank you very very much for this tool…..
Pascal, you’re my new best friend!! I somehow stumbled to your website looking for tool to help me and I already lost hope…
Thank you very much!
Hi Pascal,
I am losing my hope to restore WSS whole site to retrieve a single file that one of my colleagues overwritten.
Your tool really help me to extract out the file from old database.
Thanks a lot.
Hi Pascal,
It seems it doesn’t work on SQL Server 2008.
Stefan
Hi Stefan,
Unfortunately, I never tested it with SQL Server 2008. Can you tell me how it behaves? Do you receive an error message?
Thanks.
Pascal.
Hi Pascal,
This tool works really well for what I was looking for, the only question I have is if you have a simple way to filter what attachments you export based on something like created date?
Thanks,
Josh
Hi Josh,
Sorry, I didn’t implemented a filter. I admit that it would be interesting on large libraries or lists.
Pascal.
How many times have I been saved via the Web by smarter more generous people than me?
Thanks Pascal, you saved my job.
Best regards,
Matt
Hi,
It saved my job and time too…
Its very good tool. Nice work man…
The tool from James Edelen didnt work so well for me, but this version worked a treat. Many thanks Pascal.
Amazing, thanks a lot for sharing this tool!
This tools sounds good. Could you varify with me please if this can extract the user details out of sharepoint as well?
I am talking
name, lastname, username, email, and the listing of teamsites this person would have been given access to.
if this tool cannot would you know what can?
i appreciate your answer
Hi,
This tool cannot extract user details out of Sharepoint. That would be an interesting feature to add…
I don’t know about a tool that does it. Is ist from a broken Sharepoint Environment or from a working environment. With some googling, it is probably possible to find one for the latter.
Pascal.
I encountered an error when trying to view and export the site template gallery of a MOSS 2007 site from a content database. The error is:
“System.Data.SqlClient.SqlException: Ambiguous column name ‘tp_GUID’
at System.Data.SqlClient.SqlCommand.ExecuteReader
…etc…
at Sharepoint.DBExporter UI.ExplorerForm.LoadPreviewList(ListNode node)
at Sharepoint.DBExporter.UI.ExplorerForm.SitesTreeview_AfterSelect(Object sender, TreeViewEventArgs e)”
Awesome! Thanks.
@Steven.
Thanks for the information. I will try to take a look as soon as I can.
Pascal.
Great tool!
Also, for pulling data from a live sharepoint site, I’ve used this tool that worked well for me:
http://ezra.auerbach.co.il/2008/11/reporting-on-sharepoint-data-using-the-sharepoint-content-database/
Pascal,
Thanks much – You saved us a ton of time. Only one problem I notice; If your app lists a document as checked out (shows userid in Checked Out To field) it does not get exported. The hasAttachments field is true, but in the attachments list at the bottom there are no files listed. Thanks again.
Awesome, awesome, awesome tool! Beautifully simple and worked like a charm for me in SP2007 R2! Nice work.
Sorry, MOSS 2007 Sp1, not R2.
Great tool.
You saved me hours of digging into WSS specifications.
Cheers
Thank you very much
You saved me.
Cheers
Statues should be erected in honour of Pascal. He saved my live, and prevented doom and agony that I was certain to unleash on the world entire.
Thanx Alot
you saved me
Hi Pascal,
Great tool! I could even use it on a Windows 7 machine with SQL 2008.
Hi Pascal,
Great tool, thanks a lot. This tool helped me go through a SharePoint database that was 3 years old.
Hi Pascal,
Thanks for the excelent tool! I was just wondering if it would be possible to add somthing in? At the moment when you export data from lists it extracts it to the root of the folder, I have a image library with 5000 pictures in different folders; subfolders etc and I was wondering if it was possible to add the subfolder creation in? (Had a look at source but went straight over my head!!)
Thanks, Rob
Hi Rob,
I had this in my todo list as you are not the first one to ask for that. I am sure it wouldn’t be such a big deal. I can point out exactly where would be the fix if you want to. Otherwize, I will check if I can do something quick.
Pascal.
I edited the “LinkedAttachmentFormatter.cs” file to change the first line of “ExportAttachment” method as shown below:
public void ExportAttachment(int attachmentNumber, string sourceFolder, string sourceFilename, byte[] content)
{
//following changes made by Amrit to create folder structure
string sPath = System.IO.Path.Combine(_AttachmentFolder, sourceFolder.Replace(’/',’\\’));
System.IO.Directory.CreateDirectory(sPath);
sPath = System.IO.Path.Combine(sPath, sourceFilename);
//…
Thanks Amrit, I will integrate your changes into the class and recompile a new version.
Thanks again.
Pascal.
Hi Pascal, Thanks for making this tool available.
Have you had a chance to compile a version that restores directory structure? I’m in desperate need of restoring a large database and really need the directory structure in place.
-Nick
Hi Nick,
I have implemented the code provided by Amrit into version 1.1.0.3.
This version now export documents with the same directory structure as it was stored into the document library.
All thanks to Amrit.
Pascal.
Pascal,
I too would like to automate this tool. I got halfway, but once I get to exportmanager and the formaters, I get lost.
I understand you think this is only a last resort tool, but for those of us still running 2003 this would be a great way to allow single file restores.
I would be willing to pay for your time to implement this feature. Please email me.
Thanks!
PS. This tool saved my butt a couple of years ago… thanks so much!