Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Full-Text Search / December 2006

Tip: Looking for answers? Try searching our database.

Initial search taking a long time

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
bryon.chan - 08 Nov 2006 04:44 GMT
Hi,
I am using SQL server full text indexing for indexing and searching
webpages.

If I do a search after about 20 minutes of not searching, I get a long
wait (>40 secs). Searches after that take <1 sec. Is this a memory
issue, i.e. the index needs to be loaded into memory, which is causing
the long wait?

The indexes are small <1MB, so that's not the issue.

I am using SQL Server 2005, I don't recall having this problem with
2000.

Thanks in advance
Bryon
Hilary Cotter - 08 Nov 2006 10:45 GMT
It could well be. What is your value of sp_configure 'max server memory
(MB)', you should leave 512 to 1 Gig for the OS (and MSFTESQL).

Signature

Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

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,
> I am using SQL server full text indexing for indexing and searching
[quoted text clipped - 12 lines]
> Thanks in advance
> Bryon
bryon.chan - 08 Nov 2006 20:52 GMT
sp_configure 'max server memory (MB)'

max server memory (MB)    16    2147483647    2147483647    2147483647
Hilary Cotter - 08 Nov 2006 21:02 GMT
Holy moley, you have 2,147,483.647 Gigs of Ram! Is this your laptop? the
unit is in mgs. If this is SQL 2005 take the physical RAM on your machine
and subtract one gig from it. This should be the value you are using here.

Signature

Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

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

> sp_configure 'max server memory (MB)'
>
> max server memory (MB) 16 2147483647 2147483647 2147483647
bryon.chan - 08 Nov 2006 21:32 GMT
There is one gig of physical ram, although its running on a virtual
machine.

I need to talk with the "tech" guys about this setting, because they
are responsible for it not me. But doesn't this mean that theres more
than enough memory for the SQLFT.?

Do you know how else I could diagnose the situation? for example, any
tools I could use to monitor whats happening when one of the long
searches is executing?

> Holy moley, you have 2,147,483.647 Gigs of Ram! Is this your laptop? the
> unit is in mgs. If this is SQL 2005 take the physical RAM on your machine
[quoted text clipped - 17 lines]
> >
> > max server memory (MB) 16 2147483647 2147483647 2147483647
bryon.chan - 08 Nov 2006 21:39 GMT
Just noticed something important..

The time between searches does not matter, it seems that every 20
minutes or so (regardless of whether there were searches during this
period), something "resets" and the first search occuring after that
time takes a really long time to execute..

So I think this might not be a memory issue.

> There is one gig of physical ram, although its running on a virtual
> machine.
[quoted text clipped - 28 lines]
> > >
> > > max server memory (MB) 16 2147483647 2147483647 2147483647
bryon.chan - 09 Nov 2006 03:49 GMT
Found this article on MSDN:
You may experience a 45-second delay when you run a full-text query in
an instance of SQL Server 2005 that is running on a server without
Internet access

http://support.microsoft.com/kb/915850

Actually I'm still testing if it did the trick.. but it looks hopeful.

And thanks Hilary for your efforts :)

Bryon

sp_fulltext_service 'verify_signature', 0;
GO
> Just noticed something important..
>
[quoted text clipped - 37 lines]
> > > >
> > > > max server memory (MB) 16 2147483647 2147483647 2147483647
Hilary Cotter - 09 Nov 2006 04:41 GMT
so if you issue a

sp_fulltext_service 'verify_signature', 0;
GO

does the problem go away?

Signature

Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

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

> Found this article on MSDN:
> You may experience a 45-second delay when you run a full-text query in
[quoted text clipped - 57 lines]
>> > > >
>> > > > max server memory (MB) 16 2147483647 2147483647 2147483647
bryon.chan - 31 Dec 2006 11:48 GMT
Yes :)

> so if you issue a
>
[quoted text clipped - 78 lines]
> >> > > >
> >> > > > max server memory (MB) 16 2147483647 2147483647 2147483647
 
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.