 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Other Technologies / Full-Text Search / January 2007General Search Strategy Advice
Hi there, I'm looking for some advice on the best methods / tools to implement an intranet search facility using ASP.NET and SQL2005. I need the ability to search both SQL Server content and files stored on the web servers file system (.doc, .xls, .pdf, etc). Is there one tool that will perform both of these tasks for me, or am I going to have to use a combination of fulltext search on the DB and Index Server ? I know I can store the files in the DB and use and IFilter to search the contents, but if possible I'd want to keep the files in the file system rather than move them all into the DB. Any pointers would be most appreciated. Regards, Larry. Ideally they will all be stored in the database or the file system. It really depends on whether you are joining them against relational tables whether you should store them in the database or not. Indexing Services isn't as scalable as SQL FTS, the boundary occurs somewhere between 1 million and 3 million documents.  SignatureHilary Cotter Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com > Hi there, > [quoted text clipped - 16 lines] > Regards, > Larry. Hi Larry, You may try doing: 1. Using the index server on one hand as filesystem indexing tool and read the result from SQLServer. To do this you must create a Linked server (from your sql server) pointing to your indexing server. And read the data from FileSystem with OPENQUERY (with select .... sqlserver style) 2. Have a table with a varbinary column where you can upload the files and index their content / based on the extension. HPH, xk > Hi there, > [quoted text clipped - 16 lines] > Regards, > Larry. Using a linked server to Indexing Services (Index Server was an NT 4.0 Product) is simply not scalable. SignatureHilary Cotter Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com > Hi Larry, > [quoted text clipped - 32 lines] >> Regards, >> Larry. Thanks for that Hilary, Do you think actually storing the documents in SQL FTS would provide the best performance ? Are there any 3rd party tools that anyone knows about ? Regards, Larry. > Using a linked server to Indexing Services (Index Server was an NT 4.0 > Product) is simply not scalable. [quoted text clipped - 36 lines] >>> Regards, >>> Larry. Definitely, especially if you are querying them relationally. However, returning them from the file system especially through a web server which is optimized for returning documents offers better performance than returning them through the db. Also if you store up to 100 documents per subdirectory and nest all subdirectories in groups of 100 you get optimal file system performance. SignatureHilary Cotter Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com > Thanks for that Hilary, > [quoted text clipped - 46 lines] >>>> Regards, >>>> Larry. Thanks Hilary, There's enough there for me to be working on for now. Regards, Larry. > Definitely, especially if you are querying them relationally. However, > returning them from the file system especially through a web server which [quoted text clipped - 57 lines] >>>>> Regards, >>>>> Larry. Hello Larry, I breifly looked at SQL Turbo last year and was impressed. It allows the filename to be stored in the DB rather than the whole document. It could be worth a try. Simon Sabin SQL Server MVP http://sqlblogcasts.com/blogs/simons > Thanks for that Hilary, > [quoted text clipped - 53 lines] >>>> Regards, >>>> Larry. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.