Which of these should I index using Indexing Service
I have a 2K Server that hosts are few websites. One has about 5 years of data stored in a SQL 2K database.
What would be the best way to use indexing service to index this data?
Export it to htm files and index it?
Have indexing service index the SQL DB directly?
I would think the easiet would be indexing the SQL data directly, but I worry about indexing service. I've seen it eat CPU and RAM like candy in prior years, when I toyed with it.
Anyone here using indexing service to index SQL data and it works well?
It's a quick easy 500 points to point me in the right direction.
What would be the best way to use indexing service to index this data?
Export it to htm files and index it?
Have indexing service index the SQL DB directly?
I would think the easiet would be indexing the SQL data directly, but I worry about indexing service. I've seen it eat CPU and RAM like candy in prior years, when I toyed with it.
Anyone here using indexing service to index SQL data and it works well?
It's a quick easy 500 points to point me in the right direction.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
hmm... I would think it would take longer to figure out how to migrate data from SQL Server over to files to be stored on the server and to actually do that.. I guess it doesn't make sense to me to move stuff from a DB over to files in this case.
>> I jsut don;t ahev the time right now to setup Full Text in SQL
Setting up full text is easy and really quick. It's basically just clicking an option in the Enterprise Manager. The only changes you would make in the code for searching would be the Query itself. And I would hope you have all that as stored procedures so all you would actually need to do is build a new stored procedure and change the procdure name in the code.
Full text addresses the performance issue. Select stuff (the stuff you want searched) is basically cached and so downtime should be quite minimal.
>> I jsut don;t ahev the time right now to setup Full Text in SQL
Setting up full text is easy and really quick. It's basically just clicking an option in the Enterprise Manager. The only changes you would make in the code for searching would be the Query itself. And I would hope you have all that as stored procedures so all you would actually need to do is build a new stored procedure and change the procdure name in the code.
Full text addresses the performance issue. Select stuff (the stuff you want searched) is basically cached and so downtime should be quite minimal.
ASKER
Thanks guys! I guess I'll be diving into the Full Text Search.
Let me know if the point split worked out right. First time I've treid that.
Let me know if the point split worked out right. First time I've treid that.
ASKER