BDC will work fine if you implement the specified "updated since" indexer query as detailed (rather poorly, to be honest) in the BDC SDK.
On 1/10/08, Sezai KOMUR <[EMAIL PROTECTED]> wrote: > > > > > >> the index service will only look at the change log of the sites/site coll > in question (SPSite.GetChanges(...)) > > > > Thanks for the info Mick, I've always wondered how an incremental sharepoint > site crawl works in V3. > > > > But what happens with a BDC incremental crawl ? Can I set them to 5mins too? > > > > I was just about to set incremental crawls to 5 mins on a BDC content source > as a test, but then realised it obviously can't use SPSite.GetChanges to get > the delta, so I googled bdc incremental crawl and found the following - > http://geekswithblogs.net/Tariq/archive/2007/05/23/112680.aspx > > > > "You would need some column on your table/view/or Stored-Proc to indicate > the last modified time of that entity instance " > > > > also > > > > "this property needs to be called __BDCLastModifiedTimestamp and should be > of type string" > > > > So if your lob application doesn't store the last modified time for each > individual row, incremental crawls won't work for a BDC content source…. > > > Sezai Kömür > Senior Developer - BEng, BSc - Microsoft Certified Technology Specialist > - http://www.moss2007.com.au/ > > > > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Mick Badran > Sent: Thursday, 10 January 2008 1:04 AM > > To: [email protected] > Subject: RE: [OzMOSS] programmatically add items to be crawled > > > > > > Hi Roger - (sorry for coming in late) > > > > > > Are your sites v2 or v3? > > > > > > If they are v3 the index service will only look at the change log of the > sites/site coll in question (SPSite.GetChanges(...)) so only the changes are > indexed for that last schedule interval. > > > > > > I generally use every 5 mins for the crawl interval (incremental) on large > sites with no worries (even if the V3 sites are on other boxes/farms) > > > > > > A good place to get a handle on all this is the "Enterprise Search Resource > Kit" - bunch of goodies on there from the prod team. > > > > > > 15 min intervals is what we used to do for V2 sites. > > > > > > > Mick Badran (MVP - BizTalk) | mb: +61 404842833 | > im:[EMAIL PROTECTED] > > > Breeze Training | Training + Integration Specialist | Microsoft Readiness > Instructor > > > blogs:http://blogs.breezetraining.com.au/mickb > > > > > ________________________________ > > > From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Roger > Noble [EMAIL PROTECTED] > Sent: Wednesday, 9 January 2008 4:43 PM > To: [email protected] > Subject: RE: [OzMOSS] programmatically add items to be crawled > > > > Ok, that sounds like a good place to start. > > Thanks for your help! > > > > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Hodges, Kristen > Sent: Wednesday, 9 January 2008 4:11 PM > To: [email protected] > Subject: [SPAM] - RE: [OzMOSS] programmatically add items to be crawled - > Found word(s) list error in the Text body > > > > Yeah that's correct. Recommendations we were given from Microsoft was 15 > minute intervals – and we have a large ContentDb + same server for search > and hosting. I have to admit though we don't do 15 minutes because we > didn't have any need. That said, MOM alerts have been configured if CPU > usage exceeds 80% - it never happens even when search is running. That's on > a 64-bit box with 4 CPUs and 4Gb memory. > > > > You could prove the performance baseline if you create a dummy copy and run > 5 minute incrementals on that? See what PerfMon shows. Then you'll know > for sure. > > > > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Roger Noble > Sent: Wednesday, 9 January 2008 4:32 PM > To: [email protected] > Subject: RE: [OzMOSS] programmatically add items to be crawled > > > > Correct me if I'm wrong, but my understanding of how an incremental crawl > works is to crawl the site in full an do a hash compare on each item to look > for changes. So the concern is the load on the servers hosting the sites and > the time it would take to do the crawl (depending on the amount and size of > the documents). > > > > (but I agree that it doesn't make a whole load of sense) > > > > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Hodges, Kristen > Sent: Wednesday, 9 January 2008 3:56 PM > To: [email protected] > Subject: [SPAM] - RE: [OzMOSS] programmatically add items to be crawled - > Found word(s) list error in the Text body > > > > That doesn't seem to make a whole lot of sense… If the search server is on > a separate server there are no performance implications??? You're only > talking about an incremental crawl right? > > > > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Roger Noble > Sent: Wednesday, 9 January 2008 4:23 PM > To: [email protected] > Subject: [OzMOSS] programmatically add items to be crawled > > > > Hi All, > > > > I have a question regarding search. > > I'm trying to see if it's at all possible to programmatically add items into > the search index. I have a situation where the client wants documents to be > searchable almost immediately after they have added them. > > I've suggested that the only solution is to schedule an incremental crawl > every 5min or so, but they are not happy with that solution. Mainly due to > performance concerns (they are running a separate search server). > > > > Any help / comments are appreciated. > > Thanks > > Roger > > > IMPORTANT NOTICE: This e-mail message is intended to be received only by > persons entitled to receive the confidential information it may contain. > E-mail messages to clients of Oconics Pty Ltd may contain information that > is confidential and legally privileged. Please do not read, copy, forward or > store this message unless you are an intended recipient of it. If you have > received this message in error, please forward it back to the sender and > delete it completely from your computer system. > > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the list > with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the list > with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > > > IMPORTANT NOTICE: This e-mail message is intended to be received only by > persons entitled to receive the confidential information it may contain. > E-mail messages to clients of Oconics Pty Ltd may contain information that > is confidential and legally privileged. Please do not read, copy, forward or > store this message unless you are an intended recipient of it. If you have > received this message in error, please forward it back to the sender and > delete it completely from your computer system. > > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the list > with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the list > with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > > > IMPORTANT NOTICE: This e-mail message is intended to be received only by > persons entitled to receive the confidential information it may contain. > E-mail messages to clients of Oconics Pty Ltd may contain information that > is confidential and legally privileged. Please do not read, copy, forward or > store this message unless you are an intended recipient of it. If you have > received this message in error, please forward it back to the sender and > delete it completely from your computer system. > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the list > with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the list > with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the list > with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net
