Thursday, March 24, 2016
Tuesday, March 22, 2016
Monday, March 21, 2016
Thursday, March 17, 2016
Search Topology Components
Types of components in SharePoint 2013 Search Topology:
Index replicas: To achieve fault tolerance and redundancy, you can create additional index replicas for each index partition. These index replicas can be distributed over multiple servers.
- Search Admin Component
- Index
- Crawler
- Content Processor
- Analytic Processor
- Query Processor
1)Administration Component:-
The search administration component runs the system processes that are essential to search. This is the component that performs provisioning to add and initialize instances of other all search components.
2) Index:-
The index consists of one or more index partitions, and each can have multiple replicas.
Index partitions: You can divide the index into discrete portions, each holding a separate part of the index. Search index is the aggregation of all index partitions.
These index partitions are stored in a set of files on the disk.Index replicas: To achieve fault tolerance and redundancy, you can create additional index replicas for each index partition. These index replicas can be distributed over multiple servers.
3)Crawler:-
The Crawl Component crawls the content based on what is specified in the crawl databases.To retrieve information, the crawl component connects to the content sources by invoking the appropriate indexing connector or protocol handler. After retrieving the content, the crawl component passes crawled items to the content processing component.
4)Content Processor:-
The Content Processing Component processes crawled items passed by the Crawler, and sends these items to the Index. It performs operations such as document parsing and property mapping. It also performs linguistics processing and transforms crawled items into artifacts that are included in the search index.
5)Analytic Processor:-
The Analytics Processing Component performs both search analytics and usage analytics. This component uses information from these analyses to improve search relevance, create search reports, and generate recommendations and deep links.
6)Query Processor:-
Query Processing Component analyzes and processes search queries and results.
When the query processing component receives a query, it performs linguistic processing first (like word breaking and stemming), then analyzes and further processes the query to optimize precision, recall and relevance. In the end, the processed query will be submitted to the index component.
The index component returns a result set based on the processed query, and the Query Processor in turn processes that result set, before returning it to the search front-end.
Sunday, March 13, 2016
SharePoint Online: will not receive e-mail notifications even when Send an email invitationoption is selected.
keep in mind that Groups that are created in the Office 365 admin center and security groups that are imported from local Active Directory by using Directory Synchronization will not receive e-mail notifications even when Send an email invitationoption is selected. This is a default behavior of SharePoint Online.
Thursday, March 10, 2016
Useful SQL Queries for SharePoint Practitioners
The SQL queries listed below can be very useful for SharePoint Farm administrators to manage/administer the SharePoint content databases .
Note: The queries mentioned below are not specific only to SharePoint databases and can be used with any SQL database.
1.To get the total number of space utilized by all the SharePoint databases in SQL server:
SELECT CONVERT(DECIMAL(10,2),(SUM(size * 8.00) / 1024.00 / 1024.00)) As UsedSpace
FROM master.sys.master_files
FROM master.sys.master_files
2.To get the name of all the SharePoint databases in a SQL instance :
Select * from Sys.Databases
3.To find the space used by a SharePoint DB and its free size :
*Replace MY_DB with the concerned database name
use “MY_DB”
exec sp_spaceused
exec sp_spaceused
4.To find the size consumed by SharePoint Databases individually in SQL Server:
SELECT DB_NAME(database_id) AS DatabaseName,
Name AS Logical_Name,
Physical_Name, (size*8)/1024 SizeMB
FROM sys.master_files
5.To get the total number of SharePoint databases in the SQL server:
select * from sys.databases
or
select COUNT(*) from sys.databases
6.To find the path for SQL Server error logs:
sp_readerrorlog
7.To get the total number of site collections in a Web application :
select count(*) as ‘Total Site Collection’ from sites
Note: Point to the content database hosting that site collection and run this query
8.To get the total number of sites in a web application :
select count(*) from Webs
Note: Point to the content database hosting that site collection and run this query
9.To get the Site Title and Site ID :
select Title as ‘Site title’,FullUrl, SiteId as ‘Site Collection Id’ from Webs order by SiteId
10.To get the number of sites under each site collection in a web application :
select SiteId, count(*) as ‘Total Sub Sites’ from Webs inner join Sites on Sites.Id = Webs.SiteId group by SiteId
Note: Point to the content database hosting that site collection and run this query
Tuesday, March 1, 2016
Sharepoint designer workflows will not work with AAM
Sharepoint designer workflows will not work with AAM, when we change the default url to AAM host url.
Note: We should keep the default url as default.
Thanks,
Venkat
Note: We should keep the default url as default.
Thanks,
Venkat
Subscribe to:
Posts (Atom)