Mssearch.exe consuming High CPU over extended time period

Hello,
We are running SQL 2000 sp4 with full text search, recently we are
getting 100% CPU over extended period of time and the only way to
resolve this is by killing the Mssearch.exe process. (we tried to
restart the service but it hang) the Microsoft search service is
running under local system account.
our system topology is active/passive cluster with NAS disks, 4GB RAM
and 4 CPU for each server.
May be some one can help me?
The issue happen randomly with no specific job running at that time or
any thing, and when it happen the SQL queries are running very very
slow.
Thank you

No solution to your particular problem, except looking at a prioir post:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=93706&SiteID=1

In your particular case, when did the problem start? After upgrade, some configuration change, resource change, database size change?

This may help understand the problem.

Thanks,
Boris.|||I asked our dev team and there are no known problems of this kind. I would recommend contacting product support services and have them look at your particular configuration. Most likely the problem you are seeing is caused by the content being indexed.|||Hi,
We appear to be experiencing the same thing. There is no disk activity - just mssearch running at 100% utilization.
Have you found an answer yet?|||We used Microsoft support and nothing found we tried rebuild all catalogs , Fix some snapshot problem on the NAS and still we got the same problem finally we changed the affinity mask of the Mssearch and the SQL (SQL use CPU 1 and 2 and Mssearch the rest) we are still waiting to see if it help to solve the problem for now (4 days) it look fine even though the Mssearch took 100% the SQL continue to give services and the CPU drop back to normal with out human interference. So I will have more clear answer with in a week.

Mssearch.exe consuming High CPU over extended time period

Hello,
We are running SQL 2000 sp4 with full text search, recently we are
getting 100% CPU over extended period of time and the only way to
resolve this is by killing the Mssearch.exe process. (we tried to
restart the service but it hang) the Microsoft search service is
running under local system account.
our system topology is active/passive cluster with NAS disks, 4GB RAM
and 4 CPU for each server.
May be some one can help me?
The issue happen randomly with no specific job running at that time or
any thing, and when it happen the SQL queries are running very very
slow.
Thank you

No solution to your particular problem, except looking at a prioir post:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=93706&SiteID=1

In your particular case, when did the problem start? After upgrade, some configuration change, resource change, database size change?

This may help understand the problem.

Thanks,
Boris.|||I asked our dev team and there are no known problems of this kind. I would recommend contacting product support services and have them look at your particular configuration. Most likely the problem you are seeing is caused by the content being indexed.|||Hi,
We appear to be experiencing the same thing. There is no disk activity - just mssearch running at 100% utilization.
Have you found an answer yet?
|||We used Microsoft support and nothing found we tried rebuild all catalogs , Fix some snapshot problem on the NAS and still we got the same problem finally we changed the affinity mask of the Mssearch and the SQL (SQL use CPU 1 and 2 and Mssearch the rest) we are still waiting to see if it help to solve the problem for now (4 days) it look fine even though the Mssearch took 100% the SQL continue to give services and the CPU drop back to normal with out human interference. So I will have more clear answer with in a week.

MSSearch without SQL Server

We are using MSSearch via SQL Server to perform free-text searches.
However, we would rather not store the entire raw text in the SQL
Server. So is there a way to use the MSSearch service outside the
context of SQL Server? In other words, to populate MSSearch directly
with free-text, let it build its index and query either MSSearch
directly or indirectly via SQL Server but without actually storing the
free-text in SQL Server.
Hope someone can help me out here.
Thanks in advance
Thomas
Not really. What you could do is create a linked server to Index
Server/Indexing Services and then query it this way.
Here is how to add a linked server to the system catalog Indexing Services
uses.
sp_AddLinkedserver any_name, 'Indexing Service', 'MSIDXS', 'your catalog
name'
and then query like this
create procedure test_index @.strsearch varchar(20) as
declare @.strSQL varchar(244)
select @.strSQL='select FileName,path, vpath from scope() where contains ('
select @.strSQL=@.strSQL +char(39)+ char(39)+ @.strsearch
+char(39)+char(39)+')'
select @.strSQL='select * from openquery(any_name,'+ char(39)+
@.strSQL+char(39) +')' exec (@.strSQL)
The performance offered is not the best, so you might want your client to
access the Indexing Services query objects directly, ixsso offers better
performance than msidxs and ado.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Thomas Stryger Olsen" <thomas.stryger.olsen@.gmail.com> wrote in message
news:88bfcba4.0501070717.58614f1b@.posting.google.c om...
> We are using MSSearch via SQL Server to perform free-text searches.
> However, we would rather not store the entire raw text in the SQL
> Server. So is there a way to use the MSSearch service outside the
> context of SQL Server? In other words, to populate MSSearch directly
> with free-text, let it build its index and query either MSSearch
> directly or indirectly via SQL Server but without actually storing the
> free-text in SQL Server.
> Hope someone can help me out here.
> Thanks in advance
> Thomas
|||Thomas,
Where does most of your "raw text" reside today? In SQL Server 2000 table(s)
or in files on the server's hard disk?
If most of the raw table is on the server's local disk drive, you may want
to consider one of the many desktop search tools, such as those listed at
http://spaces.msn.com/members/jtkane/Blog/cns!1pWDBCiDX1uvH5ATJmNCVLPQ!249.entry
Specifically, dtSearch can index and search data in SQL Server as well as
files on the disk.
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Thomas Stryger Olsen" <thomas.stryger.olsen@.gmail.com> wrote in message
news:88bfcba4.0501070717.58614f1b@.posting.google.c om...
> We are using MSSearch via SQL Server to perform free-text searches.
> However, we would rather not store the entire raw text in the SQL
> Server. So is there a way to use the MSSearch service outside the
> context of SQL Server? In other words, to populate MSSearch directly
> with free-text, let it build its index and query either MSSearch
> directly or indirectly via SQL Server but without actually storing the
> free-text in SQL Server.
> Hope someone can help me out here.
> Thanks in advance
> Thomas

msg 4866

I have created a tab delimited text file using MS Foxpro 2.6 for Unix.
The last field on each line is followed only by a linefeed \n.
When I try to use bulk insert I get the message that the 40th (last) field on the line is too long.
I have tried adding a tab after the last field but this makes no difference.
I have added an ! (exclamation mark) after the last field and changed the rowterminator attribute to !\n. Still doesn't work?
I am using sftp to copy the file from the unix system to windows, and there is no change in the size of the file, so I don't think that a carrriage return is being inserted.
Any suggestions?

If I reduce the size of the input file to one record, then the insert works.|||Never mind, I figured it out. Lines have to end with '\r\n' regardless of the fact that the documentation says the default ROWTERMINATOR is '\n'

MSFT Please Help

Hi,

I am working on localizing SSRS reports and wanted to store the text for the labels in the database for different languages. The Language id would be passed by the user as a parameter. Based on this Language ID, the required data for the labels would be fetched and stored in a dataset in the custom code. This dataset would then be searched for relevant LabelIDs and the label caption in the particular language would be returned. The dataset would be a shared variable so it would get initialized the first time. For initializing the dataset I would need the datasource information, which would either be stored in the Shared Data source or embedded in the Report.

Can I refer to the shared data source being used by the current report in the Custom Code Window ? Or can I retrieve the data source information embedded in the report and use it in the Custom Code? If so, how ?

Thanks In Advance.

Ashish

Hi Guys,

Does any one know as to how can we access the data source connection information from Custom Code ?

I need that information to populate a custom dataset created in the Custom Code.

Please help.

TIA.

Ashish

MSDTC and Full Text Indexing

Happy Christmas everyone,
I have just visited an active/active win2K(sp2) and SQL 2000(sp3a) cluster
that is not too happy. The virtual servers will not fail over between the
nodes as the MSDTC will not restart if moved. Full text indexing exists
only in one virtual server and needs to be on both instances.
I suspect that comclust wasn't run at installation but has been subsequently
run on one node only. Is there a safe way of now recreating the MSDTC or
reinstalling somehow without reinstalling SQL?
Thanks in advance.
Tim
I never wish I was not what I was not when I didn't wish what I was not was
not what I am not.
Hi Tim!
Yes, you can remove and reinstall MSDTC 'underneath' SQL.
However, the health of this cluster sounds pretty suspect!
I would caution you to BACK EVERYTHING UP before you do anything to this
cluster.
:-)
All system db's...everything.
If it's not moving, back it up!
Ok, with that said, you can follow this KB article on moving and rebuilding
the MSDTC resource:
294209 How to rebuild or move MSDTC used with a SQL failover cluster
There is also this article:
Microsoft Distributed Transaction Coordinator (MSDTC) Recovery Techniques
in Windows 2000 Cluster Server (243204)
Which is not really SQL specific.
As for the FTSearch issue...that is a little more complicated.
Generally there are two reasons FTS doesn't work in a cluster.
1. Search setup was not successful
2. You have missing registry keys.
For number 1, you will need to do some detective work.
First collect the most recent sqlstp#.log from both nodes.
Look for the searchsetup.exe section.
Any errors? If there is an error number, go to a cmd prompt, type net
helpmsg <errornumber>
What's the error? This will be important. At that point you should engage
PSS to rebuild FTS, as it's tricky at best.
For number 2, follow this article to confirm you have the correct registry
entries for FTS:
http://support.microsoft.com/default...B;EN-US;810056
INF: You Must Use Resource-Specific Registry Keys for SQL Server Cluster
Resources (810056)
If missing, put them in there. If that doesn't fix it, again, call PSS,
you probably have more at play than just missing registry keys.
Hope your sickly cluster recovers!
Thanks!
Donna Lambert
SQL Server Product Support