In that situation, it is essential to use the cross-that data are stored by SharePoint and any other application where you intend to use the same data, which is entering through graphical user interface of SharePoint. The actual cost, time and productivity advantage of SharePoint can be used by ourselves to allow the use of portals and data entered through these for integration with other applications smoothly. As such, we have no control over how data is stored within SharePoint portal but that should not be an obstacle in the design of user interfaces with SharePoint. SharePoint provides methods to play with all the data you want to integrate with other external applications to SharePoint.
Principally, SharePoint Portal Server and Windows SharePoint Services uses a database from SQL Server to store all your documents, web pages, and metadata. Another database is used to store the most detail. In fact, almost everything related to SharePoint is stored in a SQL Server 2000 or MSDE database. By its very design, the database is the heart of SharePoint, and developers must be partners with its format to make use of it. During installation, you can define whether the SharePoint database is to MSDE or SQL Server 2000. SharePoint data is stored in a relational database either using MSDE or SQL Server 2000 in terms of how it was installed. All SharePoint data can be seen in Enterprise Manager on the SQL server involved.
The database name differs based on how the portals have been named there. A few crucial databases and their SharePoint nomenclature are like this:
- The database that ends with _Config_db: database stores the configuration for the whole SharePoint server / farm. Anything pertaining to the global configuration and set through the SharePoint Central Administration is stored in this database.
- Finish _SITE database: stores all the contents of a specific portal. Contains files, web pages, websites, sites, and all things related to SharePoint infrastructure.
- Finish _PROF database: stores all information about user profiles, but also holds the details of what information we collect on different user profiles.
- Ending _SERV database: Stores data for searching, reporting, and indexing. It stores the gatherer log information as well as text indexes content that is crawled. In fact it can be easily controlled by the right mouse button on any of the databases and choosing Properties. In fact, this could be one way of knowing how much space each function or activity on your site, you are assuming.
0 comments:
Post a Comment