Chapter 2: MOSS Search

Schema
.AllManagedProperties
.QueryCrawledProperties

ManagedProperty
.GetMappings()

Mapping
.CrawledPropertyName

schema.AllManagedProperties.Create(name, type);

MappingCollection

CrawledProperty
mappings.Add(new Mapping(crawledprop.Propset, crawledprop.Name, crawledprop.VariantType, managedprop.PID));

managedproperty.SetMappings(mappings);

Customizing the Search Center

• Lite - does not require Publishing Feature
• IIS Web Application is associated to an SSP
• With Tabs - fully customizable
• Page layouts - Search Page (Search Box WP), Search Results Page, Advanced Search Page (Advanced Search Box WP), People Search Results Page 
• Tabs - All Sites, People; are items stored in two lists
• Search Box WP - has a Scopes Dropdown
• Search Summary WP - corrects the Spelling
• Search Core Results WP - stemming is disabled by default. Example: buy matches buying, bought. Noise word query is enabled by default. Example: the, a, an. Can be configured to have a fixed keyword query. Has a Selected Columns property that you can add/remove from.

Sample Stored Procedure, Query for SSRS

CREATE PROCEDURE prCustomerOrders
@startDate DATETIME, @endDate DATETIME
AS
SELECT
c.CustomerID, c.CompanyName,
c.City, c.ContactName,
o.OrderID, o.OrderDate,
od.UnitPrice, od.Quantity,
od.UnitPrice * od.Quantity AS ExtendedPrice
FROM
Customers c
INNER JOIN
Orders o ON c.CustomerID = o.CustomerID
INNER JOIN
[Order Details] od ON o.OrderID = od.OrderID
WHERE
o.OrderDate BETWEEN @startDate AND @endDate
ORDER BY
c.CompanyName, o.OrderDate

---------------------

SELECT
S.OrderDate, DATENAME(weekday, S.OrderDate) as Weekday,

S.SalesOrderNumber, S.TotalDue, C.FirstName, C.LastName
FROM
HumanResources.Employee E
INNER JOIN
Person.Contact C ON E.ContactID = C.ContactID
INNER JOIN
Sales.SalesOrderHeader S ON E.EmployeeID = S.SalesPersonID
WHERE
(S.OrderDate BETWEEN (@StartDate) AND (@EndDate) AND
S.SalesPersonID IN (@SalesPersonID))

Finding the Id (Guid) for a SharePoint List

From Nick Grattan:
There are times when you need to find the Id (a Guid) of a list – for example, when setting the Task list to be used with SharePoint Designer Workflows (see my blog post here). Here’s a simple way of doing this:


•Navigate to the SharePoint list using the browser.
•Select the Settings + List Settings menu command.
•Copy the Url from the browser address bar into Notepad. It will look something like:

http://moss2007/ProjectX/_layouts/listedit.aspx?List=%7B26534EF9%2DAB3A%2D46E0%2DAE56%2DEFF168BE562F%7D

•Delete everying before and including “List=”.
•Change “%7B” to “{”
•Change all “%2D” to “-“
•Chnage “%7D” to “}”

You are now left with the Id: {26534EF9-AB3A-46E0-AE56-EFF168BE562F}

From Ken Pespisa:
A (slightly) easier way if you have MOSS 2007 is to go to the List or Library settings as described above, then right-click on the “Audience targeting settings” or “Information management policy settings” links and choose Copy Shortcut.



You can then paste the URL and there’s no need to decode the GUID. For some reason these links aren’t URL encoded.

Source: http://nickgrattan.wordpress.com/2008/04/29/finding-the-id-guid-for-a-sharepoint-list/

How to Activate the Report Server Feature

1. Click Start, click Administrative Tools, and then click SharePoint 3.0 Central Administration.
2. Click Site Actions.
3. Click Site Settings.
4. Click Site Collection Features.
5. Find Report Server Integration Feature in the list.
6. Click Activate.

MOSS+SSRS Related Topics

• To debug during the setup of "Reporting Services Add-In for Sharepoint: There is a setup log file in the %temp% folder for the user (under Local Settings folder) who is installing the Reporting Services Add-in. The file name is RS_SP_.log
• If the "Reporting Services" feature do not show up within Central Administration, it is because the feature failed to activate within the Site Collection during setup. You must run the "Add-In" with the same user account you used to install MOSS 2007.
• If the Report Server feature is not fully installed within a site collection, execute the following command: stsadm -o activatefeature -name ReportServer -url http://siteCollectionURL
• After applying SP2, under "Database Setup" when you try to create a new database: you may encounter an error that says the DB cannot be found. When you check within the SQL Server, you will observe that the Database has been created. This means, there's nothing wrong with permissions... the "update" scripts failed due to a BUG. What I did is to name the Report Server DBs without appending the "ReportServer" name. After doing so, the DB Setup completed without problems.
• Old Name: MOSSDEVReportserver
• New Name: MOSSDEV
• What to customize per report: Query Parameters or Filters, Number Format, Sorting, Header/Footer, Totals

Filters vs. Parameters
Reporting Services has several methods for dynamically filtering report contents, including the following:
Query parameters filter data at the source as it is retrieved.

Report filters, applied to a dataset or data region, limit the data that is displayed from a generated report.

Using filters retrieves all data, but only data that is relevant to the user is displayed. This may be less efficient on an individual report basis than filtering at the source. However, it lets you retrieve the data once from the source and store in it a snapshot to serve many different user communities. On the other hand, when using query parameters, you must revisit the data source for each new value of the query parameters. Filters enable you to use execution snapshots and still get full parameterization.

Source: http://technet.microsoft.com/en-us/library/cc966445.aspx

Resources:
SSRS 2005 Installation
SSRS 2005 Creation of Reports Tutorial
SSRS 2005 Troubleshooting