Tag Info

New answers tagged

0

Create external content type(s) using BCS and create list using that external content type. The complete SQL table schema and data will be fetched to list. And you can create CRUD operations on them using SharePoint. For more, refer to : http://www.codeproject.com/Articles/683749/Implementing-Business-Data-Connectivity-in-SharePo


0

BCS external content types and lists are the only OOTB way of surfacing the external data as per SharePoint guidelines. But you can always build your own solution in .Net on top of SharePoint.


1

Since the original site is in the same farm I would use the Backup-SPSite / Restore-SPSite commands. When the site is restored to a new location, it should be given a new ID. You can also see this happen sometimes when bringing in a content databases and the root site is not available (because the current DB contains the root site collection). When this ...


2

As per my experience, I don't think you can make of a copy of content DB with in same farm even with the different web app. because it contains the site collections IDs which will remain same even making the copy. Config db have those ids that why you cant see any site collection in new restored db. You can restore it to different farm. In order to prove ...


1

From your questions and comment, I understand you have a content Db with size of 1.7 TB along 328 Site collections. This is big content DB and it will take too much time, if you are not seeing any error then you have to wait. As a side note, I would highly recommend that split the database into multiple DBs. As per Best practice your db should be around ...


0

If this is the only server in the farm then you have to rebuild the farm. As you said, you have the Content DBs then it is easy to recover. Most important, Clean Uninstall. Remove all the folders on sharepoint path, clean the IIS etc. No left over should be on the server other wise it will cause issue for new install. Install the SharePoint on the server( ...


1

The key solution for your problem is: Re-install SharePoint and create a brand new web application. Detach the content database via powershell Attach content DB This will restore the site collections and the associated content from the old content DB. You can refer the scripts and complete details in the below article: Here


0

For the new SQL server, You have to configure it for RBS as well. You have to follow all the steps which you did on exisitng server.You just need configure the RBS on 2nd SQL server because on WFE it is already setup. Enable FILESTREAM on the database server. Provision a BLOB store for each content database Enable RBS for each content database Assign ...


0

There is no need to edit or run any sql database query or operation. the most simple way is to use powershell and the error is removed. As shown, the message reports a content database name (SharePoint_Content_Portal) and feature ID (8096285f-1463-42c7-82b7-f745e5bacf29), but not the sites or site collections where the feature exists. In addition to this, ...


0

I usually succeed using this script <# 1. To run the script - add your GUID on the last line of this script Example: [MissingFeature] feature:ID [8307a780-2546-f10b-551f-0e692d0fce39] 2. Add your SqlServer name and instance on the last line of this script. #> if ($ver.Version.Major -gt 1) {$host.Runspace.ThreadOptions = ...


0

This is a very handy tool in such scenarios: Feature Administration and Cleanup tool


0

I came across the same issue. I deleted the contentdatabase with Microsoft SQL Server Management Studio. I deleted the physical database from the harddrive. Then I tried to create a contentdatabase again and it created a WSS_Content_459f1985-2d80-4cfb-a678-befa22348098. By deleting the actual physical contentdatabase AND the logdatabase before creating the ...



Top 50 recent answers are included