Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

2.  Fix your history usage data according to your URL Mappings. The following example replaces the internal server name with the FQDN (Edit the timestamp in the SQL query to a relevant date range for you).
     Create a script based on this example to fix history data according for the URL Mapping you have created. Then execute it against the CardioLog database.

Info
iconfalse

 

/* Example: Replace the internal server name to the portal name - http://websrv01/ > http://www.intlock.com/ */
Use CardioLog
GO
declare @top int
declare @startTime datetime
declare @endTime datetime
set @top = 10000
set @startTime = '2010-09-01' /* Edit the start date (date format: YYYY-MM-DD) */
set @endTime = GETDATE() + 1
select top 1 '1' from tab_event_log
while @@rowCOunt > 0
begin
print cast(@top as varchar(50))
;with a as (select top (@top) url, searchUrl, QueryString
from tab_event_log LG
where
eventtype in (0,1)
and Timestamp >= @startTime
and Timestamp < @endTime
and entityid = '00000000-0000-0000-0000-000000000000'
and SearchURL like 'http://websrv01/%'
)

update a
set QueryString = Url,
Url = substring(replace(url, 'http://websrv01/','http://www.intlock.com/'), 0, 1000),
SearchUrl = substring(replace(SearchUrl, 'http://websrv01/','http://www.intlock.com/'), 0, 400)
end

GO 

3.  Execute the following SQL script against the CardioLog database to map the lost events to their corresponding SharePoint tree item. This can be done for a specific date range editing the timestamp in the SQL query:

...

To enable/disable the SharePoint Tree Automatic Fine Tuning web service, edit the [CardioLog Installation Folder]/CardioLogScheduleServices/CardioLog.Services.exe.config (located on the CardioLog application server):

...