Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

Due to storage limitations within our portal environment, a user's request to have a sp 2007 list that could potential grow to 100 gbs with our documents is not possible to implement.

Therefore, I'm looking for a solution where the user can attach documents to a SP list form and those documents would be uploaded to a external fileshare on the same domain as our portal servers. Verses the sharepoint content db houses the sp site collection.

I'm wondering if this is easy to do within an infopath form by directing the attach file control to a udcx file but I'm not sure how to implement it.

Any guidance would be appreciated. Thanks!

share|improve this question
add comment

3 Answers 3

up vote 0 down vote accepted

If you have Nintex Workflow then you can use one of their built in actions to move files to your local file system.

You can also use the free DocAve Extender. More RBS info can be found in this related question (and this one).

share|improve this answer
add comment

You can utilize EBS/RBS or a thrid party like StoragePoint to offload the files/blobs to fileshares.

share|improve this answer
    
thanks but i forgot to mention that this is sharepoint 2007 environment. i'd like to avoid third party tools if possible. –  user2825 May 31 '11 at 14:14
    
EBS is available in 2007. The complexities of blob offloading warrant the cost of third party tools in my opinion. –  PirateEric May 31 '11 at 14:24
add comment

Aside from EBS, the only other supportable option you have would be to write a custom IRouter for a Records Center (http://msdn.microsoft.com/en-us/library/microsoft.office.recordsmanagement.recordsrepository.irouter(v=office.12).aspx). You'd effectively write the BLOB out inside of the IRouter and replace it with a stub pointing to the external BLOB.

The IRouter is much less functional and transparent than EBS, but far easier to build than an EBS provider. I would recommend EBS because once implemented it is completely transparent to the end user and not limited to a Record Center. I would also recommend purchasing a solution from a 3rd party rather than rolling your own...lots of gotchas with EBS that aren't covered in the Msft doc on the interface and/or blog posts I've seen on the technology.

share|improve this answer
    
Rob is one of the authorities in this arena. If he's saying get a third party tool to handle it, that carries a lot of weight. –  PirateEric May 31 '11 at 15:26
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.