Tag Info

Hot answers tagged

5

Short answer, the quote above does say RBS and the content database must not exceed the limit. Not just the content DB when RBS is used. Database size is such a gray area with SharePoint. MS's recommendation of 200GB is to ease the maintenance of the database. "Content databases exceeding 200 GB and up to 4 TB support much of the same flexibility as ...


3

IMO, you should definitely use RBS because majority of files are larger than 1MB. In your case, your DB can further grow exceptionally large because of all the binary large object (BLOB) data. And, Reading and writing BLOBs, as well as other relational data, can slow down SQL Server performance because it’s not the ideal place for storing BLOBs. By using RBS ...


3

We have a web application dedicated for serving up files and this is what I can tell you from my experience. The design of the web app is to house executables, license codes, and installation guides, so pretty similar to your requirements. The executables can range from 4MB to 1.5 GB with guides in the 200k range. Under normal load, there aren't too many ...


2

With RBS FILESTREAM the only filter you have available to you is size. There is no list item context when a BLOB externalized, so file type and other filters are not natively available. Additionally, the file name and extension will not be promoted to the BLOB store...you'd see something like \server\blobstore\GUID instead of an actual filename. Different ...


2

If you have very basic requirements then the RBS FILESTREAM provider may be sufficient, but it really is a very limited capability. I would also caution you against the idea that it is "built in". It's every bit an add-on as a 3rd party would be and is completely administered via PowerShell...no Central Admin UI at all. If you're not concerned with saving ...


2

What is the purpose behind the table? Accessing the BLOB data directly outside of the SP API is not supported. That being said, MS has a sample RBS implementation and details how it works which may help you out. http://msdn.microsoft.com/en-us/library/cc905212(v=sql.100).aspx


2

While externalizing BLOBs may solve some of your performance concerns it doesn't sound like it is going to solve your core problem which is the amount of content and speed that you are throwing this content into SharePoint. Make sure you heavily review your architecture to ensure you are supporting the database IOPS required as well as understand the ...


2

Start Command Prompt using the Run as administrator option. msiexec /qn /lvx* rbs_install_log.txt /i RBS.msi TRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME="SP_Content" DBINSTANCE="SP2010-WFE1" FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1 to Confirm the installation of RBS, open rbs_install_Log.txt, and then ...


2

It sounds like you're using the ItemUpdated event. If you used ItemUpdating I believe you could modify the AfterProperties instead of performing a second update. This may be of use to you: NBSP: Event Receivers


2

Note: You cannot enable FILESTREAM on a 32-bit version of SQL Server running on a 64-bit OS Please go over the steps for enabling FILESTREAM, maybe you missed a step. This is how I would enable FILESTREAM for SQL Server 2008 R2: On the Start menu, point to All Programs, point to Microsoft SQL Server 2008 R2, point to Configuration Tools, and then click ...


1

Even if it was available in the online versions, Remote Blob Storage would just offload the files to the file system of the SharePoint servers (or wherever MS would deem appropriate), not keep them locally. In conjunction Wictor's suggestion, you could also try to use a Page Viewer web part and point it to the local file share. This will surface the files ...


1

I don't see why not. I havn't tried myself, but as long as you put your VMs and storage accounts in same affinity group, I would assume that Azure's internal disks are fast enough to be wihtin the 20ms latency requirement, but a test would be the only way to know for sure. Also be sure to look into striping your disks if you want to obtain good IOPS. Read ...


1

I would say that the problem isn't a SharePoint problem (SharePoint is really speaking just a ASP.Net website reading and writing to a SQL database), but more of a SQL Problem. I found a good article where Microsoft did some research on the topic. Read here: http://research.microsoft.com/pubs/64525/tr-2006-45.pdf


1

Bill, Steps 1 thru 5 are applicable when you set up RBS for the first time. For additional site collections all you have to do is follow step 2 and 4 (per Microsoft's Tech Support). I had a open ticket with them and ask them if they would clarify this for me. After exchanging 7 emails they agreed that only step 2 and 4 is necessary for additional site ...


1

Edit: rereading it, your right to question it! It looks like you need to run the command again with your second content database. Frankly that's really terrible language on Microsoft's part, as I believe they are trying to explain that there is only one instance of the install even though you run the configuration command multiple times.


1

This is really one of those "it depends" type of questions. If you are targeting performance, Accessing files 256KB or LESS is generally better via DB, and anything larger can be externalized. Plan for RBS: http://technet.microsoft.com/en-us/library/ff628583.aspx In addition to above MS has this whitepaper on SQL performance of RBS: ...


1

You wont be able to guarantee or even control performance unless you own all the connections. It is possibly to increase your chances of success by adding WAN optimizer at your locations, such as Riverbed devices. You may also be able to achieve similar benefit at less cost if you utilize proxies at remote locations that can pre-fetch your large object and ...


1

There really is very little you can do to overcome the challenges of a global SharePoint deployment when it comes to the handling of large files. Normally we'd talk about a CDN or some other mechanism of using ones geographic context to establish where content should come from (i.e. it would be beneficial to have a user in the U.K. fetch a document from a ...


1

We have few offices around the World and SP is not the only system here, because sometimes it is not good enought for our needs. We don't want to store large files on SharePoint at all. Users can upload 50 MB per one file, but it depends. HR and TT departments working with video files, presentations or trainings and we created streaming server for them. Big ...


1

If you have InfoPath licensed, that is certainly a decent way to go for building input forms, but building them with Visual Studio in VB or C# is not a monumental task either: http://msdn.microsoft.com/en-us/library/bb418732(v=office.12).aspx http://blogs.msdn.com/b/cjohnson/archive/2006/09/05/application-development-on-moss-2007-amp-wss-v3.aspx ...


1

So the problem here is that a blob in SQL Server is not hyper-linkable. Your web part can generate a link, but what would the link point to - it has to be a resource a Web Server can actually address. To solve this problem, you need need an intermediary between the hyperlink and the SQL Blog. Example - your web part provides a hyper-link to a custom page ...


1

Will all files of all Site collections in that web application be stored in the RBS? Not all files will be stored on the file system (RBS store). By default, files larger than 100 KB will be stored on the RBS store you specify in your configuration. You can modify this value. Is RBS a feasible method? If I understand you correctly, what you meant ...


1

If you can see past the Marchitecture then StoragePoint shows one way in which RBS can manifest itself in SharePoint. The end user shouldn't see anything it just determines where file blobs are stored and is used by admins to reduce storage costs. I'm not affiliated with StoragePoint and have never used their product.


1

With RBS, "blobs" are defined by file extension, so only the file extensions you configure are shipped to the filesystem. I'm not sure I understand question 2, you tell a site collection to use a specific SQL instance, and that's where the content DB resides. If RBS is set up for that content DB, files will be shipped to the filesystem configured for that ...



Only top voted, non community-wiki answers of a minimum length are eligible