SharePoint RBS Solution

Question - we are potentially looking at SQL 2008 RBS solution as part of our document management solution when we look to migrate our existing content over to SharePoint. We are planning that our teams (document management solution ) will each be a
single site collection with one content db per team (site collection) for internal SLA and data recovery.
What we would therefore like to know is do we only need one RBS storage location in total (all web applications) or just one for each web application, or one per site collection content db?

An RBS solution does present more IT management in terms of backup/restore as you have the SQL content and the file system content as part of the solution.
You mentioned your desire not to put the documents into the content databases directly (i.e. as Blobs). Why not? How much data are you planning to put into SharePoint for document management and how large are your files? You cite that you don't want to inflict
any overhead that is not necessary... What are you referring to here? The overhead of the SQL storage (as related to Blobs), or the processing of actually getting the files into or out of SharePoint. These are all considerations for moving towards
an RBS solution - but make sure it is the right decision for your organization. Given the right scenario, RBS can improve overall SharePoint performance as a document management system.
I would recommend that you continue your investigation for an RBS solution. See Overview of RBS for 2010 at http://technet.microsoft.com/en-us/library/ee748649.aspx. This page,
related links and other resources linked from this page offer great insight to the benefits of using RBS and use these articles as an initial guide to determine if you'll truly benefit from it.
Also, there are also third party products that integrate with RBS that you can look into as well. Do a Bing/Google search and you'll come up with many.
I hope this helps and good luck!
Craig

Similar Messages

When Deploying SharePoint 2010 solution using Powershell gives me nothing

When Deploying SharePoint 2010 solution using Powershell gives me nothing
And when go to Central Admin >> System Settings >> Farm Management >> Manage Farm Solution
I found my Solution Status is Deploying and still deploying and nothing.

Hi,
According to your description, my understanding is when you deploy the SharePoint solution, the deploy status stuck on the deploying status.
To resolve this issue, I suggest you can do as the followings:
1. On any server, start, run, services.msc, enter, this will open the services console.
2. Now type s, this will give you all the services that start with S, look for SharePoint timer service and make sure it’s in started mode.
3. This service should be started on all the front ends as well as application server.
More information:
Solution deployment stuck on deploying: SharePoint 2010
Thanks
Best Regards
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

SharePoint RBS and Oracle

We have existing SharePoint 2010 while 95% of content is documents (PDF and Images) uploaded to lists with folder structure , current the database size is up to 300GB and we're planning to use RBS , but the Oracle guys sending us request that if its applicable
to enable SharePoint RBS to store files to Oracle 11g for unkown reason for me and I have no idea if this applicable , I hope I find answer here.

If you're using RBS to remove your content from your SQL databases why on earth would you want to put it straight back into another database? RBS is sometimes worth while in 2010 but I question why you're doing it here, your first step should always be to
split the content out into other databases where possible.
As far as i'm aware nothing exists to allow you to store content in Oracle systems, other than using BDC which doesn't hold documents.

SharePoint Farm Solution Deployment without Downtime

Hi,
We are looking for a solution to deploy SharePoint .wsp in the farm without taking any downtime.
Load balancer is in place and there are more than 1 WFE, App and Search servers in the SharePoint farm.
If you have worked on similar solutions before or have any ideas/views regarding the same, also the pros and cons.
Request you to share the same.
Thanks & Regards,
Sudheer
Thanks & Regards, Sudheer

Since you have load balancer and more than one WFE, you may be able to deploy solutions first on one WFE and then on other WFE thereby preventing the outage. Check these posts for more info:
http://blog.ithinksharepoint.com/2012/07/16/deploying-sharepoint-wsp-solutions-without-downtime/
https://social.technet.microsoft.com/forums/sharepoint/en-US/fb4820b1-aca8-464e-a1ff-656c62c756a8/install-solution-packagewsp-with-no-downtime
Blog | SharePoint Learnings CodePlex Tools |
Export Version History To Excel |
Autocomplete Lookup Field

Problem with VS2012 and Sharepoint 2013 Solution

Hello everyone
I've got a problem that's driving me crazy. I'm migrating a Sharepoint 2010/Visual Studio 2010 Solution to Sharepoint 2013/visual Studio 2012 with the developer tools.
My solution consists of 3 class libraries (common, data access layer and business logic) and a Sharepoint 2013 project containing the features, and the webparts using the output of the class libraries. The references inside projects are set through "Add
Reference -> Solution -> Projects". I want a wsp-file containing the sharepoint artifacts and the assemblies from my class libraries. (those are added through the package explorer -> Advanced). If i use Build/Rebuild on the Solution it compiles fine,
as it should.
If i use the "deploy" or "publish" command on visual studio to create a solution package, the build fails with the message:
"The type or namespace name 'whatever' does not exist in the namespace 'Xyz.Project'' (are you missing an assembly reference?)
I can't find out what's wrong. if i deploy anything manually everything works fine. building/rebuilding my whole solution works fine. Everything is set to .NET 4.5. It seems to be that "wsp-package"-building process that has a problem.
Any hint/idea would be welcome.
Greetings
Carlos

To fix this, simply remove the reference to your "common" code library and re-add it as an assembly reference (as opposed to a project reference). I.e. Select 'Add reference...' and then browse to
the 'bin' folder of your "common" library.
I did in fact consider that. But it can hardly considered good style and you lose a lot of benefits. The biggest of all being that you can never be sure you are working with latest versions of your common class libraries.
While unloading/reloading worked in VS 2012 things are worse in VS 2013. In VS 2013 the solution doesn't package anymore at all. No matter what you do. Cleaning, rebuilding, reloading... I tried all of that in vain.
Edit: And while I'm at it... great job in marking a totally irrelevant posting as answer. Another trigger happy content moderator. I really wonder if their financial goals are tied to the number of postings they mark as answered.
Solution: See here: http://ddkonline.blogspot.de/2013/10/build-and-packagepublish-behaviour.html
The key thing is - your common project assemblies need to be added in a particular order (in the order your assemblies need to be built)

Migrate SharePoint OnPremise solution to SharePoint Farm

Hi,
I've some couple of queries regarding SharePoint solution migration from SharePoint premise to online.
1) We've some customs solutions which is developed using sandbox and the content database size upto 1TB. Can we able to migrate to SharePoint online. If it is possible how to migrate the content and what licensing model supports?
2) I've some 10,000 users in my SharePoint site collections. What is the best way to migrate users from on-premise to SharePoint online?
Balaji -Please click mark as answer if my reply solves your problem.

Hi Viet,
Have you used https for your SharePoint 2010 environment? or using AAM?
If yes, please check if you add the root certificates of the SSL certificate to the SharePoint 2010 per the following article.
http://karthickmicrosoft.blogspot.com/2012/10/https-site-infopath-issue-you-do-not.html
If not, please check and mark sure the below InfoPath service options are checked from Central Administration site and test again.
https://technet.microsoft.com/en-us/library/cc262263(v=office.14).aspx#authenticate
Allow user form templates to use authentication information contained in data connection files
Allow cross-domain data access for user form templates that use connection settings in a data connection file
If there is any further assistance needed, please feel free to post.
Thanks,
Daniel Yang
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Daniel Yang
TechNet Community Support

What cannot be and can be deployed in sharepoint sandbox solution

what cannot be and can be deployed in sharepoint sandbox solution

Hi,
Sandboxed Solution Limitations
When a sandboxed solution is deployed, the array of SharePoint functionality available to it is limited to help reduce any security vulnerabilities it may have. Some of these limitations include the following:
Sandboxed solutions have a restricted subset of deployable solution elements available to them. Potentially vulnerable SharePoint project templates, such as site definitions and workflows, are not available.
SharePoint runs sandboxed solution code in a process (SPUCWorkerProcess.exe) separate from the main IIS application pool (w3wp.exe) process.
Mapped folders cannot be added to the project.
Types in the Microsoft SharePoint Server 2010 assembly Microsoft.Office.Server cannot be used in sandboxed solutions. Also, only types in the Microsoft SharePoint Foundation 2010 assembly Microsoft.SharePoint can be used in sandboxed solutions.
It is important to note that specifying a SharePoint solution as a sandboxed solution has no affect on SharePoint server; it only determines how the SharePoint project is deployed to SharePoint from Visual Studio and what assemblies it binds to. It does not
affect the generated .wsp file, and the .wsp file has no data that directly correlates to the Sandboxed Solution property.
Capabilities and Elements in Sandboxed Solutions
Sandboxed solutions support the following capabilities and elements:
Content Types/Fields
Custom actions
Declarative workflows
Event receivers
Feature callouts
List Definitions
List Instances
Module/files
Navigation
Onet.xml
SPItemEventReceiver
SPListEventReceiver
SPWebEventReceiver
Support for all Web Parts that derive from System.Web.UI.WebControls.WebParts.WebPart
Web Parts
WebTemplate feature elements (instead of Webtemp.xml)
Visual Web Parts
Sandboxed solutions do not support the following capabilities and elements:
Application Pages
Custom Action Group
Farm-scoped features
HideCustomAction element
Web Application-scoped features
Workflows with code
Refer to the article
http://msdn.microsoft.com/en-us/library/ee231562.aspx
Please Mark as Answer if its HelpFul

Developing SharePoint Online Solution

Client using SharePoint Online and need to use several task list templates. However when download to SharePoint 2013 On-Premises with Dec 2013 CU and create local lists, cannot open the lists. Get correlation Id but ULS message not meaningful
to me.
Any idea why cannot create migrate SharePoint Online lists to SharePoint On-Premises?
John

Hi,
Just for your information, SharePoint Online is always updated - as Office team apply the latest patches in SharePoint Online and later release the patches for on-premises.
Have you tried to use the list temlates in another site in SharePoint Online? If it works in another site in SharePoint Online then I think the problem is somehow the Online has more recent patches than on-premise. Also is the list refering to another list/content
types that might not be imported in the on-premise site?
Thanks,
Sohel Rana
http://ranaictiu-technicalblog.blogspot.com

How to deploy SCOM Dashboard solution to sharepoint online

i have come through many articles saying how to deploy scom dashboard solution to sharepoint server,
but how do i deploy SCOM WSP solution to sharepoint online office 365.
i need to show my SCOM dashboards on sharepoint online.
Can anyone help me in doing this?
Thanks & Regards, Suresh Gaddam

Yes i did the same thing but when i hit activate it threw some error saying you cannot deploy farm solution to sharepoint
This solution
contains invalid markup or elements that cannot be deployed as part of a sandboxed solution. Solution manifest for solution 'c125f6b7-8c1e-40ae-86e2-bd2d5e568ca2' failed validation, file manifest.xml, line 14, character 4: The element 'Solution' in namespace
'http://schemas.microsoft.com/sharepoint/' has invalid child element 'RootFiles' in namespace 'http://schemas.microsoft.com/sharepoint/'. List of possible elements expected: 'ActivationDependencies, FeatureManifests' in namespace 'http://schemas.microsoft.com/sharepoint/'.
TECHNICAL
DETAILS
Thanks & Regards, Suresh Gaddam

Ajax in Sharepoint 2013 Sandboxed solution

I want to use ajax in sandboxed solution for sharepoint 2013,is it possible we can use ajax in sandboxed solution ?
if yes then please me know the steps to implement ajax in sandboxed solution for sharepoint 2013.
if we cannot use ajax in sandboxed solution then please let me know the steps to implement in farm solution for sharepoint 2013 also please mention which version of ajax toolkit we can use in sharepoint 2013

Hi,
We can use jQuery Ajax in the sandboxed solution, the following thread for your reference:
http://social.technet.microsoft.com/Forums/en-US/cb69509c-7740-4903-be93-c2bb66aa7ad3/sharepoint-sandboxed-solution-make-ajax-post-call?forum=sharepointgeneralprevious
We can also customize web services in SharePoint Online.
Custom Webservices with SharePoint Online for Office 365
http://www.codeproject.com/Articles/327919/Custom-Webservices-with-Sharepoint
In SharePoint 2013, I suggest you create a APP to achieve your requirement.
Best Regards
Dennis Guo
TechNet Community Support

Deploy SharePoint 2010 Sandbox solution to SharePoint 2013

Hi All,
I have sand-box solution which is developed in Visual Studio 2010 for SharePoint 2010 ,And it is specially developed for branding the SharePoint 2010 site. Now I need
to add the sandbox solution to SharePoint 2013 Site.
Can any one help how can I do this.
Thanks, Quality Communication Provides Quality Work. http://siddiq-sharepoint2010.blogspot.in/ Siddiqali Mohammad .

Hi siddiqali,
According to your description, my understanding is that you want to deploy SharePoint 2010 Sandbox solution to SharePoint 2013.
Most of the wsp Solutions deployed in SharePoint 2010 should work fine in SharePoint 2013. This is because of the Support for both 14 Hive and 15 Hive directories that are Created in SharePoint 2013 by default.
Initially, when you deploy a SharePoint 2010 Solution it gets deployed to 14 Hive and not 15 Hive. To force the solution to install in 15 Hive you need to modify manifest.xml file of your solution and add addSharePointVersion=”15.0” attribute to it. The
Solutions can be forced to install in 15 hive. However, some of the files especially that refers to _layouts might not work. All SharePoint 2010 Solution files that refers to _layouts folder (i.e. Features, Layouts-files, Images, ControlTemplates)needs to
be updated, the best approach is to re-create the Solution in Visual Studio 2012.
More information, please refer to the link:
http://www.learningsharepoint.com/2013/03/24/deploy-sharepoint-2010-solutions-in-sharepoint-2013/
Here are some similar posts for you to take a look at:
http://www.threewill.com/2013/10/migrating-a-sharepoint-2010-solution-to-a-sharepoint-2013/
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/30fe4cb9-ea11-46d0-868d-4306d915b4db/how-to-convert-sp2010-wsp-to-sp2013?forum=sharepointdevelopment
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

Hashing password in UAG for FBA solution in Sharepoint 2013

We have configured FBA SharePoint 2013 Pack from Codeplex on our SharePoint 2013 environment. Creating new users will hash the user passwords in the database. When we try to authenticate the FBA users via UAG (not joined to domain) the password
will compare in clear text to the hashed password in the database. Is there any way to configure the UAG to hash the passwords the same way so we can compare it with the hashed value in our database?
Any help here would be appriciated.

Hi siddiqali,
According to your description, my understanding is that you want to deploy SharePoint 2010 Sandbox solution to SharePoint 2013.
Most of the wsp Solutions deployed in SharePoint 2010 should work fine in SharePoint 2013. This is because of the Support for both 14 Hive and 15 Hive directories that are Created in SharePoint 2013 by default.
Initially, when you deploy a SharePoint 2010 Solution it gets deployed to 14 Hive and not 15 Hive. To force the solution to install in 15 Hive you need to modify manifest.xml file of your solution and add addSharePointVersion=”15.0” attribute to it. The
Solutions can be forced to install in 15 hive. However, some of the files especially that refers to _layouts might not work. All SharePoint 2010 Solution files that refers to _layouts folder (i.e. Features, Layouts-files, Images, ControlTemplates)needs to
be updated, the best approach is to re-create the Solution in Visual Studio 2012.
More information, please refer to the link:
http://www.learningsharepoint.com/2013/03/24/deploy-sharepoint-2010-solutions-in-sharepoint-2013/
Here are some similar posts for you to take a look at:
http://www.threewill.com/2013/10/migrating-a-sharepoint-2010-solution-to-a-sharepoint-2013/
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/30fe4cb9-ea11-46d0-868d-4306d915b4db/how-to-convert-sp2010-wsp-to-sp2013?forum=sharepointdevelopment
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

Linking Solution Manager Project Documentation - MS Sharepoint

Hello,
When working on a project in Solman we upload documents as needed in each phase or scenario. This is well known to all... But we already also, have an MS Sharepoint portal sometimes with documents already stored there.
Is there a way to include the link to sharepoint ?
In other words.. Is there a way to utilize the folder structure provided by sharepoint in solution manager without replicating documents ?

Hello,
I think we found a way... Just during uploading a file to Solman, choose the option "web link", then your documentation tile will jump to the sharepoint folders.
Thanks,,
Edited by: Khalid Al-Tayaran on Nov 11, 2009 8:18 AM

Resource Files in SandBoxed Solutions SharePoint 2013

Hi,
I want to create Resource files MyResource_en.resx and MyResource_ar.resx in the sandboxed solutions,how can i do that because as per my understandings we cannot access resource files from the App_GlobalResources folder in our virtual directory when working
on sand boxed solutions.
Can anyone suggest me the work around to use resource files in sand boxed solutions.

Hi,
According to your post, my understanding is that you wanted to create Resource files in the sandboxed solutions.
There is an article for your reference, although it is about the SharePoint 2010, it is similar to SharePoint 2013.
Embedding Resources in Sandbox Solutions
Per my knowledage, SharePoint sandboxed solutions are deprecated in SharePoint 2013 Preview in favor of developing apps for SharePoint.
I recommend to create App to achive what you want.
More information:
SharePoint 2013: Sandboxed Solutions are deprecated
SharePoint 2013: What to Do? Farm Solution vs Sandbox vs App
Build apps for SharePoint
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Migration from Sandbox solution to SharePoint apps

Hi,
We have a requirement that we need to migrate SharePoint Sandbox Solution to SharePoint Apps. Few things which I would like to know that if the Sandbox solution has some custom code / server based code then how we have to migrate into Apps. Because
Apps only support client based. And in some cases, sandbox has no code solution. In that case, how we can migrate into Apps..
Recently, many companies are trying to migrate from Sandbox solution to apps becuase microsoft depreciated sandbox in SharePoint 2013. In future, they may stop to support sandbox solution. Please share your views on how to proceed on migration code
and without code based solution to Apps...
Balaji -Please click mark as answer if my reply solves your problem.

HI Balaji,
I assume you are having on premise Farm not office 365 so in that case
http://msdn.microsoft.com/en-us/library/office/fp179887(v=office.15).aspx
http://msdn.microsoft.com/en-us/library/office/fp179930(v=office.15).aspx
you have the following options for code:
1- SharePoint Hosted Apps: you will write Javascript code and use Javascript to access client object model
http://msdn.microsoft.com/en-us/library/office/fp142379(v=office.15).aspx
2-Provider Hosted Apps: you will write 2 parts , the first one is an application that will be deplpyed to SharePoint server the second one is a web site (asp.net or mvc) that can be hosted on the SharePoint server or on a separate Application server and
here you you can put all the logic of your .net code and you can have remote event recievers
http://msdn.microsoft.com/en-us/library/office/fp142381(v=office.15).aspx
for non code option what you will be doing is using SharePoint designer but mostly you will still to have SharePoint hosted apps
some codes
https://apps.codeplex.com/
https://corporatenewsapp.codeplex.com/
Hope this is clear and helpful
Kind Regards, John Naguib Technical Consultant/Architect MCITP, MCPD, MCTS, MCT, TOGAF 9 Foundation

SharePoint RBS Solution

Similar Messages

Maybe you are looking for