What's relationship between DB WSS_Content and SharePoint site collection? Is separated DB created per each site collection or a single DB can contain multiple collections?
Regards,
A single DB can contain multiple site collections.
And a single web application can have multiple content databases.
Alternatively put:
A web app 'contains' 0 or more content databases.
A content database then contains 0 or more site collections.
SharePoint Terminology – Farms, Web Front Ends, Web Application and Sites
Each site collection can only use a
single content database (though
multiple site collections can use the
same content database) – this has
major design implications as there are
maximum recommended sizes for a
content database.
Related
Can users or groups in one collection access another collection?
We have 10 collections with a number of projects and users.
Our build servers our not allowed to communicate with internet so we need to download external nuget packages to a local store. To avvoid redundancy and double work we would like to store the nuget packages in a common collection open for groups in other collections.
I created a common collection but I can't find out how to give access to it for users in other collections. Can anybody tell?
How is the sharepoint data stored in the database? We had a sharepoint site which is not there anymore however the databases are still present. The names of the databases are:-
Sharepoint_AdminContent
Sharepoint_Config
WSS_Content
WSS_Search
Is it possible that I extract data from these database? Lets suppose I want data from an specific page of the site, which table should I look at for that?
Sharepoint_AdminContent: Central Administration content database. It stores all configuration data for the Central Administration site collection.
Sharepoint_Config: configuration database. The configuration database contains data about the following:
SharePoint databases
Internet Information Services (IIS) web sites
Web applications
Trusted solutions
Web Part packages
Site templates
Web applications
Distributed Cache configuration objects
WSS_Content: Content Database. Content databases store all content for a site collection. This includes site documents or files in document libraries, list data, Web Part properties, audit logs, and sandboxed solutions, in addition to user names and rights.
WSS_Search: Search service database. This database is used for the search services. It contains the information that is required for searching content.
The data from an specific page of the site should be stored in the content database WSS_Content.
Reference: https://learn.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions
I have finished creating two Orchard CMS websites. After looking into production hosting on Azure, I have decided I would like to host them in one of two ways:
As tenants of a single master site
Using a table prefix to share the SQL Server database
I know during initial set up you can specify a table prefix to allow multiple sites in one database. Is it possible to do this after initial set up? Will I have to set up a new site and then export/import all my data into the new site with the prefixed tables?
Is it possible to migrate a site to be a tenant? Or is this similar to above; create a new site and import all the data into the tenant?
As per Bertrand's comment, I created a new site with two tenants. I used the same SQL Server database with table prefixes. I exported all the data from my two sites and imported them into the tenants.
One thing I had to do was to delete the cache.dat file in App_Data and restart the website.
I have sharepoint sites provisioned on two machines A and B. I would like to take the content database from machine A and restore it into the site on machine B.
I used SQL backup to backup machine A's database, and restored it to machine B, overwriting the existing content database. However, my sharepoint site became unreachable - I would get a generic site not found error. Did I also have to back up and restore SharePoint_Config database too?
What is the best practices for this kind of scenario?
You need to tell sharepoint where your new database is. just go to the content database management page on central administration. there you will see your previous database mapped to the web application. remove it and and the new database. it will map the web app to it and your sites will come back. be careful when entering the server and database name, as you could create a new db instead of connecting to the existing one if you mistype the name
We're looking at doing a MOSS 2007 site which will have a fairly dynamic component (an external product catalog). The external produces will be stored in a database (not managed by SharePoint) and all interaction will occur via Web Parts.
Is it possible to configure the SharePoint search to index the textual content and the external database? Or can a custom search provider be written which is also used to query the external database?
The Business Data Catalog is intended as the solution in this case.
A BDC solution is crawlable out of the box.
Unfortunately the BDC requires the Enterprise licence for SharePoint, a hefty price increase.
Any other solution will require an html interface to the database either by including the data inside the SharePoint webpages themselves or a custom set of pages.
I have not tried using a custom search provider so I cannot make a comment on doing that.
It is easy enough to include searching on both content sources as OOB SharePoint provides the ability to distinguish between content sources and has the ability to create search scopes that allow rules based on content type or url to be created.