Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
kwilliams
194 Posts |
 Posted - 2003-11-18 : 15:24:12
|
| MS ARTICLE: http://www.microsoft.com/ntserver/techresources/webserv/IndexServer.asp#sqlCan Index Server Index Dynamic Pages from SQL Server??? According to the article, I believe what happens is the following: 1) I'll create a template ASP page to be populated with DB data2) SQL Server will create a web page for each record using the ASP page3) We create an INSERT trigger that inserts a Web page whenever a record is inserted into the table.4) We create an UPDATE trigger that updates a Web page whenever a record is updated from the table.5) We create a DELETE trigger that deletes a Web page whenever a record is deleted from the table. What I'm confused about is that I know that we can use Index Server on the site pretty well (w/IFilter). And I know that I can create a page that can do a full-index search on the database into a dynamic web page according to the primary key. I just don't understand why we can't somehow tie these two processes together without having to store web pages for each record in a database. I haven't found a way to do them together yet, but I'm still looking. Any suggestions??KWilliams |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2003-11-18 : 20:29:56
|
| My suggestion is don't bother with steps 1 through 5. Just go with the "I can create a page that can do a full-index search on the database into a dynamic web page". Generating pages and FT-indexing them will just waste a lot of space and won't improve anything, since you already have the data in the database. External pages that don't contain database data WOULD be worth FT-indexing however. |
 |
|
|
kwilliams
194 Posts |
Posted - 2003-11-19 : 10:04:34
|
| Thanks for the quick response robvolk,But I still have a problem. I agree with you that MS's setup of creating a webpage for each record would be a waste of space & time, but finding another option is difficult. As I stated in my original post, I have a solution for the site-wide search and for the DB table search, but how do I tie the 2 together into the same search & results pages.Logically, there would only be a few options for setting this up:1) The first option would be to somehow put the SQL Data into webpages for Index Server to search. And we've already agreed that this solution is a waste of space.2) The second option would be to somehow search the Index Server catalogs with SQL's full-index search capability. But I haven't seen any literature on this idea.3) The last option would be to have the Index Server catalogs kept with Index Server, have the SQL Server catalogs kept with SQL Server, and to somehow tie the two together on the same search & results pages.What's your opinion on these options, and do you have any other suggestions? Thanks.KWilliams |
|
|
|
mohdowais
Sheikh of Yak Knowledge
1456 Posts |
|
|
|
|
|
|
|
Indexing Dynamic Pages Using Index Server