Full text searching in advanced services edition

I have installed the advanced services edition but cannot find out how to build and populate full text catalogs. Nothing shows on the MSSMSE tool and when I try to use a sql command to create a new catalog it says that the full text service is not installed. Am I missing something?

The Full-text Search menus in Management Studio have a dependency on SQL Agent, so they were excluded from Management Studio Express as SQL Express doesn't have SQL Agent.

As far as the error, it is completely possible that FTS is not installed as it is not part of the default installation of Express Advanced. If you did not choose to install FTS from the feature tree, it's not there. You'll need to launch the Express Advanced setup in maintenance mode and verify that you've installed all the components.

If you have installed all the components, then you should check the error log and relay the exact error so we can troubleshoot further.

Regards,

Mike Wachal
SQL Express team

-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1

Full text memory usage

Hi
I work with SQL 2005 and I know how it uses RAM but I know just some basic
stuff about Full-text catalogs and since we plan to implement them in the
future I need to know a few things.
1. Can you set min and max memory for full text service like it can be set
for SQL service?
2. Does it start using RAM as it needs it until it hits maximum and then
release it only if some other process needs RAM like SQL does?
3. How much RAM could be expected for Full text sevice to use on 20GB
catalog? (just estimate)
4. On x86 windows, full text service is limited to max 3GB of RAM (with /3GB
switch in boot.ini probably). Is on x64 Windows limitation 4GB and on IA64
there is no such limitations? Can you confirm that?
Thanks
Tom
answers inline.
Hilary 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
"Tom" <tomman@.hotmail.com> wrote in message
news:OI3fNNUfHHA.444@.TK2MSFTNGP04.phx.gbl...
> Hi
> I work with SQL 2005 and I know how it uses RAM but I know just some basic
> stuff about Full-text catalogs and since we plan to implement them in the
> future I need to know a few things.
> 1. Can you set min and max memory for full text service like it can be set
> for SQL service?
No.
> 2. Does it start using RAM as it needs it until it hits maximum and then
> release it only if some other process needs RAM like SQL does?
Not really, like any other windows application it can see up to 2 Gigs on a
32 bit system, on a 64 bit system it may see then entire physical memory. It
uses what it needs. Depending on the other applications running on this
server its working memory set may be paged to disk. It makes extensive use
of the file system cache.

> 3. How much RAM could be expected for Full text sevice to use on 20GB
> catalog? (just estimate)
We have about 12 20 gig catalogs - memory used is 40 Mgs.
That depends on your queries mainly. The indexer runs in process with SQL
Server.
> 4. On x86 windows, full text service is limited to max 3GB of RAM (with
> /3GB switch in boot.ini probably). Is on x64 Windows limitation 4GB and on
> IA64 there is no such limitations? Can you confirm that?
That is correct on 64 bit systems applications provided they are coded for
it can see the entire physical ram. So your entire catalogs could be in ram
on systems with larger memory.
>
> Thanks
> Tom
>
|||With SQL Server 2005, you typically will try to limit it to not starve the
OS. So, in an X64 environment with 12GB -- I might give 10 to SQL and allow
2 for the OS (everything else).
When you introduce full-text on this system of total 12GB, how do you
prevent FTE from starving the OS?
So, I would set 8GB for SQL and leave 4GB for the OS+FTE+everything else.
Is there nothing to guarentee that FTE doesn't over utilize that 4GB and
cause OS level latency?
I thought there might be some level of governing this by using the:
ft crawl bandwidth (max) & ft notify bandwidth (max)
sp_configure options but it doesn't seem that is what the purpose of those
are for.
Thanks,
Robert Towne
|||the full-text engine does not compete with the OS. SQL Server will complete
with other application, like sql fts. Set
sp_configure 'max server memory'
to 2 gigs less than the total memory, so fts has enough memory to operate.
"sql411@.nospam.com" <sql411nospamcom@.discussions.microsoft.com> wrote in
message news:0988A377-5262-4986-98CF-17BAAD4C9D32@.microsoft.com...
> With SQL Server 2005, you typically will try to limit it to not starve the
> OS. So, in an X64 environment with 12GB -- I might give 10 to SQL and
> allow
> 2 for the OS (everything else).
> When you introduce full-text on this system of total 12GB, how do you
> prevent FTE from starving the OS?
> So, I would set 8GB for SQL and leave 4GB for the OS+FTE+everything else.
> Is there nothing to guarentee that FTE doesn't over utilize that 4GB and
> cause OS level latency?
> I thought there might be some level of governing this by using the:
> ft crawl bandwidth (max) & ft notify bandwidth (max)
> sp_configure options but it doesn't seem that is what the purpose of those
> are for.
>
> Thanks,
> Robert Towne
>
|||OK, i was thinking that FTE in 2005 ran in a seperate memory space than what
is specified in SQL Server's 'max server memory'. Very helpful to know &
many thanks..
"Hilary Cotter" wrote:

> the full-text engine does not compete with the OS. SQL Server will complete
> with other application, like sql fts. Set
> sp_configure 'max server memory'
> to 2 gigs less than the total memory, so fts has enough memory to operate.
>
|||I thought the same as Robert.
So if FTS operates with large full-text indexes they will be cached in
memory space under SQLService?
How can I determin how much memory that SQL uses is actually used for
full-text catalog and how much for other data?
I usually use "Database pages" counter to see how much data and indexes are
cached in RAM.
Tom
"sql411@.nospam.com" <sql411nospamcom@.discussions.microsoft.com> wrote in
message news:4A8CC880-DB65-4DBA-8EDE-A67BB88DF9FE@.microsoft.com...
> OK, i was thinking that FTE in 2005 ran in a seperate memory space than
> what
> is specified in SQL Server's 'max server memory'. Very helpful to know &
> many thanks..
> "Hilary Cotter" wrote:
>
|||SQL FTE doesn't use much ram, but SQL Server will apply memory pressure on
all other applications on this box. That is why it is important to cap sql
server so SQL FTE has room to operate.
I don't think ms has exposed counters to determine how much memory of the
SQL Engine SQL FTS uses (some of the indexing operations are integrated into
the engine), but the indexes are not caches in SQL Server's data cache. They
are part of the file system cache.
"Tom" <tomman@.hotmail.com> wrote in message
news:ur1wkEzgHHA.4064@.TK2MSFTNGP02.phx.gbl...
>I thought the same as Robert.
> So if FTS operates with large full-text indexes they will be cached in
> memory space under SQLService?
> How can I determin how much memory that SQL uses is actually used for
> full-text catalog and how much for other data?
> I usually use "Database pages" counter to see how much data and indexes
> are cached in RAM.
> Tom
>
> "sql411@.nospam.com" <sql411nospamcom@.discussions.microsoft.com> wrote in
> message news:4A8CC880-DB65-4DBA-8EDE-A67BB88DF9FE@.microsoft.com...
>

Full Text Max Size?

Hi,

Does anyone have experience with Full Text catalogs on large tables? We have a full text catalog on a table with about 30 million rows. Acording to BOL, once you get over 1 million you'll need to make some adjustements. Our system works, but we randomly get the following errors with ad hoc queries. The server has 8GB of RAM and 4 3GHz processors. Does anyone have experience working with a table this big? Any suggetions as to what could cause these errors? The only thing I could find was BUG#: 469483 on MS's site, but we're not using any OR clauses

Thanks

Here's the errors...

(query)
SELECT * FROM acc_results ar
WHERE CONTAINS(finding_text, 'cell')

#1
Server: Msg 7619, Level 16, State 1, Line 1
Execution of a full-text operation failed. Not enough storage is available to process this command.


#2
Server: Msg 7342, Level 16, State 1, Line 1
Unexpected NULL value returned for column '[FULLTEXT:acc_results].KEY' from the OLE DB provider 'Full-text Search Engine'. This column cannot be NULL.
OLE DB error trace [Non-interface error: Unexpected NULL value returned for the column: ProviderName='Full-text Search Engine', TableName='[FULLTEXT:acc_results]', ColumnName='KEY'].


#3
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'Full-text Search Engine' reported an error.
[OLE/DB provider returned message: Not enough storage is available to process this command.]
OLE DB error trace [OLE/DB Provider 'Full-text Search Engine' IRowset::GetNextRows returned 0x80004005: ].just taking #1 and #3 at face value (I know nothing is what it seems), I would imagine you need more space on your hard drive.

Full Text Max Size?

Hi,
Does anyone have experience with Full Text catalogs on large tables? We
have a full text catalog on a table with about 30 million rows. Acording
to BOL, once you get over 1 million you'll need to make some
adjustements. Our system works, but often we get the following errors
with ad hoc queries. The server has 8GB of RAM and 4 3GHz processors.
Does anyone have experience working with a table this big? Any
suggetions as to what could cause these errors? The only thing I could
find was BUG#: 469483 on MS's site, but we're not using any OR clauses
Thanks
Here's the errors...
(query)
SELECT * FROM acc_results ar
WHERE CONTAINS(finding_text, 'cell')
#1
Server: Msg 7619, Level 16, State 1, Line 1
Execution of a full-text operation failed. Not enough storage is
available to process this command.
#2
Server: Msg 7342, Level 16, State 1, Line 1
Unexpected NULL value returned for column '[FULLTEXT:acc_results].KEY'
from the OLE DB provider 'Full-text Search Engine'. This column cannot
be NULL.
OLE DB error trace [Non-interface error: Unexpected NULL value returned
for the column: ProviderName='Full-text Search Engine',
TableName='[FULLTEXT:acc_results]', ColumnName='KEY'].
#3
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'Full-text Search Engine' reported an error.
[OLE/DB provider returned message: Not enough storage is available to
process this command.]
OLE DB error trace [OLE/DB Provider 'Full-text Search Engine'
IRowset::GetNextRows returned 0x80004005: ].
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Not enough storage is a common OS related error - relating to available
memory I think. Can you do things like surf on this machine, map network
drives, etc? I have heard of a 35 million row SQL FTS search solution -
IIRC.
SQL FTS 2005 has been tested to 2 billion rows.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Charlie Pyne" <cpyne@.partners.org> wrote in message
news:%23SjvpQb%23EHA.3988@.TK2MSFTNGP11.phx.gbl...
> Hi,
> Does anyone have experience with Full Text catalogs on large tables? We
> have a full text catalog on a table with about 30 million rows. Acording
> to BOL, once you get over 1 million you'll need to make some
> adjustements. Our system works, but often we get the following errors
> with ad hoc queries. The server has 8GB of RAM and 4 3GHz processors.
> Does anyone have experience working with a table this big? Any
> suggetions as to what could cause these errors? The only thing I could
> find was BUG#: 469483 on MS's site, but we're not using any OR clauses
> Thanks
> Here's the errors...
> (query)
> SELECT * FROM acc_results ar
> WHERE CONTAINS(finding_text, 'cell')
> #1
> Server: Msg 7619, Level 16, State 1, Line 1
> Execution of a full-text operation failed. Not enough storage is
> available to process this command.
>
> #2
> Server: Msg 7342, Level 16, State 1, Line 1
> Unexpected NULL value returned for column '[FULLTEXT:acc_results].KEY'
> from the OLE DB provider 'Full-text Search Engine'. This column cannot
> be NULL.
> OLE DB error trace [Non-interface error: Unexpected NULL value returned
> for the column: ProviderName='Full-text Search Engine',
> TableName='[FULLTEXT:acc_results]', ColumnName='KEY'].
>
> #3
> Server: Msg 7399, Level 16, State 1, Line 1
> OLE DB provider 'Full-text Search Engine' reported an error.
> [OLE/DB provider returned message: Not enough storage is available to
> process this command.]
> OLE DB error trace [OLE/DB Provider 'Full-text Search Engine'
> IRowset::GetNextRows returned 0x80004005: ].
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||Everything else seems to work fine. What is IIRC? I searched on it,
but got a bunch of different results back.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||IIRC = If I Recall Correctly.
Ok, can you review your application log for events from MSSearch saying
master merge paused.
Also is this a cluster?
"Charlie Pyne" <cpyne@.partners.org> wrote in message
news:elauz0b%23EHA.3368@.TK2MSFTNGP10.phx.gbl...
> Everything else seems to work fine. What is IIRC? I searched on it,
> but got a bunch of different results back.
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||Charlie,
Yes, I do. First of all, what is the exact version of SQL Server (7.0 or
2000) and on what OS platform is it deployed? Could you post the full output
of -- SELECT @.@.version -- as this is VERY helpful information in
troubleshooting such SQL FTS performance issues!
Secondly, and depending upon what your is your SQL Server version and SP
level as well as the exact query that your are getting these errors, you may
want to checkout KB article 818883 "PRB: You may receive error 7619 when you
run a full-text query that contains many OR operators in the search string"
at http://support.microsoft.com/default...b;en-us;818883 as one of
the symptoms is error: "Not enough storage is available to complete this
operation" as this occurs on SQL Server 2000 SP3 and when your CONTAINS
query contains many logical OR operators.
However, because of the larger number of rows (30 million), in your
FT-enable table, you may have encountered additional problems related to the
Master Merge. Specifically, you should review your server's Application
Event log for "Microsoft Search" or MssCi source events - errors, warnings
AND informational for any related Master Merge paused conditions.
Furthermore, you should review the Performance Monitor (Perfmon) counters
for Microsoft Gatherer: Reason to back off, Microsoft Gatherer Projects:
Gatherer Paused Flag, and Microsoft Search Indexer Catalogs: Merge Progress
to determine if there is an existing issue with the Master Merge process.
Depending upon your reply, I can provide you with more specific
recommendations.
Thanks,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Charlie Pyne" <cpyne@.partners.org> wrote in message
news:#SjvpQb#EHA.3988@.TK2MSFTNGP11.phx.gbl...
> Hi,
> Does anyone have experience with Full Text catalogs on large tables? We
> have a full text catalog on a table with about 30 million rows. Acording
> to BOL, once you get over 1 million you'll need to make some
> adjustements. Our system works, but often we get the following errors
> with ad hoc queries. The server has 8GB of RAM and 4 3GHz processors.
> Does anyone have experience working with a table this big? Any
> suggetions as to what could cause these errors? The only thing I could
> find was BUG#: 469483 on MS's site, but we're not using any OR clauses
> Thanks
> Here's the errors...
> (query)
> SELECT * FROM acc_results ar
> WHERE CONTAINS(finding_text, 'cell')
> #1
> Server: Msg 7619, Level 16, State 1, Line 1
> Execution of a full-text operation failed. Not enough storage is
> available to process this command.
>
> #2
> Server: Msg 7342, Level 16, State 1, Line 1
> Unexpected NULL value returned for column '[FULLTEXT:acc_results].KEY'
> from the OLE DB provider 'Full-text Search Engine'. This column cannot
> be NULL.
> OLE DB error trace [Non-interface error: Unexpected NULL value returned
> for the column: ProviderName='Full-text Search Engine',
> TableName='[FULLTEXT:acc_results]', ColumnName='KEY'].
>
> #3
> Server: Msg 7399, Level 16, State 1, Line 1
> OLE DB provider 'Full-text Search Engine' reported an error.
> [OLE/DB provider returned message: Not enough storage is available to
> process this command.]
> OLE DB error trace [OLE/DB Provider 'Full-text Search Engine'
> IRowset::GetNextRows returned 0x80004005: ].
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||Charlie,
A quick follow-up... I think you may benefit from this KB article:
303459 (Q303459) "INF: How to Improve the Performance of FTS Queries for
Large Tables" http://support.microsoft.com/?id=303459 and make changes to
the MaxPropStoreCachedSize registry key value as well as use the Top_N_Rank
parameter in all of your SQL FTS queries, per KB article: 240833 (Q240833)
"FIX: Full-Text Search Performance Improved via Support for TOP"
http://support.microsoft.com//defaul...b;EN-US;240833
Thanks,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"John Kane" <jt-kane@.comcast.net> wrote in message
news:u3WGySe#EHA.2016@.TK2MSFTNGP15.phx.gbl...
> Charlie,
> Yes, I do. First of all, what is the exact version of SQL Server (7.0 or
> 2000) and on what OS platform is it deployed? Could you post the full
output
> of -- SELECT @.@.version -- as this is VERY helpful information in
> troubleshooting such SQL FTS performance issues!
> Secondly, and depending upon what your is your SQL Server version and SP
> level as well as the exact query that your are getting these errors, you
may
> want to checkout KB article 818883 "PRB: You may receive error 7619 when
you
> run a full-text query that contains many OR operators in the search
string"
> at http://support.microsoft.com/default...b;en-us;818883 as one
of
> the symptoms is error: "Not enough storage is available to complete this
> operation" as this occurs on SQL Server 2000 SP3 and when your CONTAINS
> query contains many logical OR operators.
> However, because of the larger number of rows (30 million), in your
> FT-enable table, you may have encountered additional problems related to
the
> Master Merge. Specifically, you should review your server's Application
> Event log for "Microsoft Search" or MssCi source events - errors, warnings
> AND informational for any related Master Merge paused conditions.
> Furthermore, you should review the Performance Monitor (Perfmon) counters
> for Microsoft Gatherer: Reason to back off, Microsoft Gatherer
Projects:
> Gatherer Paused Flag, and Microsoft Search Indexer Catalogs: Merge
Progress
> to determine if there is an existing issue with the Master Merge process.
> Depending upon your reply, I can provide you with more specific
> recommendations.
> Thanks,
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
> "Charlie Pyne" <cpyne@.partners.org> wrote in message
> news:#SjvpQb#EHA.3988@.TK2MSFTNGP11.phx.gbl...
>
|||Hi John,
Thanks for the reply. I'm not at work so I can't run @.@.version at this
time, but I can tell you that this server is SQL 2000 Enterprise Edition
with SP3a on Win2k Advanced Server with SP3.
We do have the MaxPropStoreCachedSize parameter in place and currently
it is set to 2000. The size of those two files listed in the article is
> 2GB. One thing I noticed last night when testing this against our test
server, (same hardware/os/sql), is the errors don't seem to happen when
this parameter is removed. The mssearch.exe process stays around 100MB
and the query completes successfully. With this key in place, the
memory used by mssearch grows to around 1 or 1.5GB and then we get the
"not enough storage" error. Mssearch.exe then just sits there holding
that amount of ram until we stop/start the search service.
I haven't had a chance to experiment with this yet, but someone else
thought that both the /3GB and /PAE switches that are currently present
could be causing problems. SQL is configured to only use 4GB of the 8GB
total, but for some reason performance of non-full text queries take a
major hit when we remove /3GB. WE've tried making the same 4GB
available to SQL with just the /PAE switch, but it doesn't seem to work
as well.
I'll check for the event log errors that you mentioned next week.
Thanks for your help. Please let me know if you have any other ideas.
Charlie
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||You're welcome, Charlie,
When you get to work, also check the server's Application event log for
"Microsoft Search" or MssCi source events - errors, warnings AND
informational for any related Master Merge paused conditions as this where
you'll find the true cause of what is causing the MSSearch service to appear
to hang. Additionally, you may want to start with smaller numbers for
setting the MaxPropStoreCachedSize value, say 500 MB to 1000 (or 1GB) and
then test until you get the failure as tuning this parameter is not an exact
science.
No, using the /3GB and /PAE switches is not the problem as the MSSearch
service with the resource_usage level set to 5 (dedicated) can only use a
max. of 512MB of RAM, if and only if this memory is available and not used
by any other process. Furthermore, the MSSearch service cannot use the
memory above the 2Gb limit.
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Charlie Pyne" <cpyne@.partners.org> wrote in message
news:uVSXfgj#EHA.600@.TK2MSFTNGP09.phx.gbl...
> Hi John,
> Thanks for the reply. I'm not at work so I can't run @.@.version at this
> time, but I can tell you that this server is SQL 2000 Enterprise Edition
> with SP3a on Win2k Advanced Server with SP3.
> We do have the MaxPropStoreCachedSize parameter in place and currently
> it is set to 2000. The size of those two files listed in the article is
> server, (same hardware/os/sql), is the errors don't seem to happen when
> this parameter is removed. The mssearch.exe process stays around 100MB
> and the query completes successfully. With this key in place, the
> memory used by mssearch grows to around 1 or 1.5GB and then we get the
> "not enough storage" error. Mssearch.exe then just sits there holding
> that amount of ram until we stop/start the search service.
> I haven't had a chance to experiment with this yet, but someone else
> thought that both the /3GB and /PAE switches that are currently present
> could be causing problems. SQL is configured to only use 4GB of the 8GB
> total, but for some reason performance of non-full text queries take a
> major hit when we remove /3GB. WE've tried making the same 4GB
> available to SQL with just the /PAE switch, but it doesn't seem to work
> as well.
> I'll check for the event log errors that you mentioned next week.
> Thanks for your help. Please let me know if you have any other ideas.
> Charlie
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||Hi John,
I don't see any errors related to Master Merge. I do see this error a
bunch of times during our initial full population...
The entry <MSSQL75://SQLSERVER/286302EC/00000342> in the hash map on
project <SQLServer SQL0000600005> cannot be updated. Error: 8007054e - A
description for this error could not be found.
MS had told us to set MaxPropStoreCachedSize based on the size of these
two files...
00000001.ps1 = 775MB
00000001.ps2 = 2.26GB
If I set this to 256, the problem seems to go away. With 256 set, I've
let the SELECT * query that we've been using to reproduce the error run
for about 10 minutes before I cancel it. With 2000 set, we'll get the
"not enough storage" error after about 2 minutes.
We also have the priorty of the service set to the default of 3. I
haven't found much in terms of how this should be set other than
1=background and 5=dedicated. Do you have any suggestions? This is a
system that is used by doctors to save case notes and query historical
notes using full text and standard sql queries. We'd like to maximize
the performance of full text, but we don't want to have a negative
effect on regular SQL. We'd also like to cut down on the time needed
for full & incremental rebuilds. Fulls now take 1 week and incrementals
take about 1 day. From what I've read, we should be using change
tracking. We plan on doing this as soon as we have this current problem
resolved. Any other suggestions beyond this?
Thanks for your help
Charlie
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Hi Charlie,
With SQL Server 2000 FTS you're somewhat limited with tables of this scale.
You could try to horizontally partition the table into multiple smaller
tables (say partition on a date range or some other column specific range of
values) and the FT Index the smaller tables using separate FT Catalogs. I'd
also highly recommend that you use CONTAINSTABLE or FREETEXTTABLE with the
Top_N_Rank value (see KB article Q240833) when running FTS SELECT * queries
against the larger FT Catalog. I'd also highly recommend that you look at
SQL Server 2005 as many of these limitations go away with Yukon FTS.
If you're server has lots of RAM, you can use sp_fulltext_service
'resource_usage', 5 to set the MSSearch service to 5 (dedicated), and it
will use the max amount of RAM (512Mb), but only if the RAM is not being
used by either the OS or by SQL Server. However, this will not fix the error
caused by large *.ps* files, as does setting the MaxPropStoreCachedSize
registry key value.
Once you've resolved this issue, use Change tracking with Update Index in
background, but be aware that an automatic Incremental or Full Population
will be run when you set this feature, so the MSSearch service can re-sync
up the FT Catalog with the SQL table data.
Thanks,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Charlie Pyne" <cpyne@.partners.org> wrote in message
news:OeQeKOY$EHA.4092@.TK2MSFTNGP09.phx.gbl...
> Hi John,
> I don't see any errors related to Master Merge. I do see this error a
> bunch of times during our initial full population...
> The entry <MSSQL75://SQLSERVER/286302EC/00000342> in the hash map on
> project <SQLServer SQL0000600005> cannot be updated. Error: 8007054e - A
> description for this error could not be found.
> MS had told us to set MaxPropStoreCachedSize based on the size of these
> two files...
> 00000001.ps1 = 775MB
> 00000001.ps2 = 2.26GB
> If I set this to 256, the problem seems to go away. With 256 set, I've
> let the SELECT * query that we've been using to reproduce the error run
> for about 10 minutes before I cancel it. With 2000 set, we'll get the
> "not enough storage" error after about 2 minutes.
> We also have the priorty of the service set to the default of 3. I
> haven't found much in terms of how this should be set other than
> 1=background and 5=dedicated. Do you have any suggestions? This is a
> system that is used by doctors to save case notes and query historical
> notes using full text and standard sql queries. We'd like to maximize
> the performance of full text, but we don't want to have a negative
> effect on regular SQL. We'd also like to cut down on the time needed
> for full & incremental rebuilds. Fulls now take 1 week and incrementals
> take about 1 day. From what I've read, we should be using change
> tracking. We plan on doing this as soon as we have this current problem
> resolved. Any other suggestions beyond this?
> Thanks for your help
> Charlie
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!

Full Text Index

helloin Full Text SearchAre there method when add record in Field for properties "Full Text Index " , update catalogs ?thankshelloplease help me !!!thanks|||

Yavari:

helloin Full Text SearchAre there method when add record in Field for properties "Full Text Index " , update catalogs ?thanks

I have no idea what you are asking. Could you rephrase your question(s?) differently?

Full Text Error

Hi,
We can successfully create catalogs on a database on our server. However,
we can never get any data from any of the searches. We have since
discovered a few errors in the Application log.
Version of SQL running is:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copy
right (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows
NT 5.2 (Build 3790: )
SP3 has been applied and re-applied.
Errors are as follows:
The crawl on project <SQLServer SQL0000700005> cannot be started. All of the
crawl seeds have been ignored because of host, extension, or other URL
restrictions. Error: 80040d07 - The specified URL is excluded and will not
be cataloged. The URL restriction rules may have to be modified to include
this URL.
One or more warnings or errors for Gatherer project <SQLServer
SQL0000700005> were logged to file <C:\Program Files\Microsoft SQL
Server\MSSQL\FTDATA\SQLServer\GatherLogs\SQL000070 0005.1.gthr>. If you are
interested in these messages, please, look at the file using the gatherer
log query object (gthrlog.vbs, log viewer web page).
The crawl on project <SQLServer SQL0000700005> cannot be started. All of the
crawl seeds have been ignored because of host, extension, or other URL
restrictions. Error: 80040d07 - The specified URL is excluded and will not
be cataloged. The URL restriction rules may have to be modified to include
this URL.
Error from the gthrlog.vbs file reveals the following:
C:\Program Files\Common Files\System\MSSearch\Bin>cscript gthrlog.vbs
"C:\Progra
m Files\Microsoft SQL
Server\MSSQL\FTDATA\SQLServer\GatherLogs\SQL000070 0005.1.g
thr"
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
5/18/2004 11:26:44 AM Add The gatherer has started
5/18/2004 11:26:48 AM Add The initialization has completed
5/18/2004 11:27:16 AM Add Started Full crawl
5/18/2004 11:27:16 AM MSSQL75://SQLServer/75d7831f Add URL is
excluded
because the URL protocol is not recognized or restricted
5/18/2004 11:27:16 AM Add Completed Full crawl
C:\Program Files\Common Files\System\MSSearch\Bin>
Yours desperately.
Os
The crawl seeds error is normally generated by changing the SQL Server Service account through the services applet in Control Panel.
Please refer to these kbs for more information on how to solve this error.
http://support.microsoft.com/default...b;en-us;277549
http://support.microsoft.com/default...b;en-us;283811
http://support.microsoft.com/default...b;en-us;308787
Your error does look a little different from the usual ones. Can you give us any history about this problem? Do you have Sharepoint Portal Server 2003 or any other server application on this machine?
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||I think you will need to open a second dblib connection to get this to work.
Microsoft is advising its customers not to use dblib any more as it may not be supported in future versions of the product, is slower than other access methods (ole-db), can't connect to instances or is unaware of instances (but you can make this work by
using an alias).
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||Oz,
Hilary, it seems to me that the following "Error: 80040d07 - The specified
URL is excluded and will not be cataloged. The URL restriction rules may
have to be modified to include this URL." and this error is not addressed in
any of the below KB articles.
I previously posted the following info here in the fulltext newsgroup back
in March 2004, "The key error is "80040d07 - The specified URL is excluded
and will not be cataloged". This is very unusual error for SQL FTS, but I
*believe* not so unusual for a SPS/WSS upgrade to SQL Server. Specifically,
the crawl seed is "MSSQL75://SQLServer/75d7831f " which SQL Server 2000 and
your FT enabled table. Did you enable FTS within SPS? Specifically, see WSS
Admin Guide title "Managing and Customizing Search" and "Enabling Search"
for more info. I *believe* this error is a symptom of not "Enabling Search"
after upgrading WSS to SQL Server 2000. Below is more info...
Examine the URL associated with this message and check the list of path
rules defined. This URL corresponds to one of the URLs or URL expressions
defined in the path rules. If you are interested in this URL, modify the
path rules. If you are satisfied with the current rules, then this warning
message is benign and can be ignored.
Regards,
John
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:502691A0-7D26-400D-8FD3-932519C47A61@.microsoft.com...
> The crawl seeds error is normally generated by changing the SQL Server
Service account through the services applet in Control Panel.
> Please refer to these kbs for more information on how to solve this error.
> http://support.microsoft.com/default...b;en-us;277549
> http://support.microsoft.com/default...b;en-us;283811
> http://support.microsoft.com/default...b;en-us;308787
> Your error does look a little different from the usual ones. Can you give
us any history about this problem? Do you have Sharepoint Portal Server
2003 or any other server application on this machine?
>
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>

Full Text Error

Hi,
We can successfully create catalogs on a database on our server. However,
we can never get any data from any of the searches. We have since
discovered a few errors in the Application log.
Version of SQL running is:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copy
right (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows
NT 5.2 (Build 3790: )
SP3 has been applied and re-applied.
Errors are as follows:
The crawl on project <SQLServer SQL0000700005> cannot be started. All of the
crawl seeds have been ignored because of host, extension, or other URL
restrictions. Error: 80040d07 - The specified URL is excluded and will not
be cataloged. The URL restriction rules may have to be modified to include
this URL.
One or more warnings or errors for Gatherer project <SQLServer
SQL0000700005> were logged to file <C:\Program Files\Microsoft SQL
Server\MSSQL\FTDATA\SQLServer\GatherLogs\SQL000070 0005.1.gthr>. If you are
interested in these messages, please, look at the file using the gatherer
log query object (gthrlog.vbs, log viewer web page).
The crawl on project <SQLServer SQL0000700005> cannot be started. All of the
crawl seeds have been ignored because of host, extension, or other URL
restrictions. Error: 80040d07 - The specified URL is excluded and will not
be cataloged. The URL restriction rules may have to be modified to include
this URL.
Error from the gthrlog.vbs file reveals the following:
C:\Program Files\Common Files\System\MSSearch\Bin>cscript gthrlog.vbs
"C:\Progra
m Files\Microsoft SQL
Server\MSSQL\FTDATA\SQLServer\GatherLogs\SQL000070 0005.1.g
thr"
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
5/18/2004 11:26:44 AM Add The gatherer has started
5/18/2004 11:26:48 AM Add The initialization has completed
5/18/2004 11:27:16 AM Add Started Full crawl
5/18/2004 11:27:16 AM MSSQL75://SQLServer/75d7831f Add URL is
excluded
because the URL protocol is not recognized or restricted
5/18/2004 11:27:16 AM Add Completed Full crawl
C:\Program Files\Common Files\System\MSSearch\Bin>
Yours desperately.
Os
Oz,
Hilary, it seems to me that the following "Error: 80040d07 - The specified
URL is excluded and will not be cataloged. The URL restriction rules may
have to be modified to include this URL." and this error is not addressed in
any of the below KB articles.
I previously posted the following info here in the fulltext newsgroup back
in March 2004, "The key error is "80040d07 - The specified URL is excluded
and will not be cataloged". This is very unusual error for SQL FTS, but I
*believe* not so unusual for a SPS/WSS upgrade to SQL Server. Specifically,
the crawl seed is "MSSQL75://SQLServer/75d7831f " which SQL Server 2000 and
your FT enabled table. Did you enable FTS within SPS? Specifically, see WSS
Admin Guide title "Managing and Customizing Search" and "Enabling Search"
for more info. I *believe* this error is a symptom of not "Enabling Search"
after upgrading WSS to SQL Server 2000. Below is more info...
Examine the URL associated with this message and check the list of path
rules defined. This URL corresponds to one of the URLs or URL expressions
defined in the path rules. If you are interested in this URL, modify the
path rules. If you are satisfied with the current rules, then this warning
message is benign and can be ignored.
Regards,
John
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:502691A0-7D26-400D-8FD3-932519C47A61@.microsoft.com...
> The crawl seeds error is normally generated by changing the SQL Server
Service account through the services applet in Control Panel.
> Please refer to these kbs for more information on how to solve this error.
> http://support.microsoft.com/default...b;en-us;277549
> http://support.microsoft.com/default...b;en-us;283811
> http://support.microsoft.com/default...b;en-us;308787
> Your error does look a little different from the usual ones. Can you give
us any history about this problem? Do you have Sharepoint Portal Server
2003 or any other server application on this machine?
>
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>

Full Text Error

Hi,
We can successfully create catalogs on a database on our server. However,
we can never get any data from any of the searches. We have since
discovered a few errors in the Application log.
Version of SQL running is:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copy
right (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows
NT 5.2 (Build 3790: )
SP3 has been applied and re-applied.
Errors are as follows:
The crawl on project <SQLServer SQL0000700005> cannot be started. All of the
crawl seeds have been ignored because of host, extension, or other URL
restrictions. Error: 80040d07 - The specified URL is excluded and will not
be cataloged. The URL restriction rules may have to be modified to include
this URL.
One or more warnings or errors for Gatherer project <SQLServer
SQL0000700005> were logged to file <C:\Program Files\Microsoft SQL
Server\MSSQL\FTDATA\SQLServer\GatherLogs\SQL0000700005.1.gthr>. If you are
interested in these messages, please, look at the file using the gatherer
log query object (gthrlog.vbs, log viewer web page).
The crawl on project <SQLServer SQL0000700005> cannot be started. All of the
crawl seeds have been ignored because of host, extension, or other URL
restrictions. Error: 80040d07 - The specified URL is excluded and will not
be cataloged. The URL restriction rules may have to be modified to include
this URL.
Error from the gthrlog.vbs file reveals the following:
C:\Program Files\Common Files\System\MSSearch\Bin>cscript gthrlog.vbs
"C:\Progra
m Files\Microsoft SQL
Server\MSSQL\FTDATA\SQLServer\GatherLogs\SQL0000700005.1.g
thr"
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
5/18/2004 11:26:44 AM Add The gatherer has started
5/18/2004 11:26:48 AM Add The initialization has completed
5/18/2004 11:27:16 AM Add Started Full crawl
5/18/2004 11:27:16 AM MSSQL75://SQLServer/75d7831f Add URL is
excluded
because the URL protocol is not recognized or restricted
5/18/2004 11:27:16 AM Add Completed Full crawl
C:\Program Files\Common Files\System\MSSearch\Bin>
Yours desperately.
OsOz,
Hilary, it seems to me that the following "Error: 80040d07 - The specified
URL is excluded and will not be cataloged. The URL restriction rules may
have to be modified to include this URL." and this error is not addressed in
any of the below KB articles.
I previously posted the following info here in the fulltext newsgroup back
in March 2004, "The key error is "80040d07 - The specified URL is excluded
and will not be cataloged". This is very unusual error for SQL FTS, but I
*believe* not so unusual for a SPS/WSS upgrade to SQL Server. Specifically,
the crawl seed is "MSSQL75://SQLServer/75d7831f " which SQL Server 2000 and
your FT enabled table. Did you enable FTS within SPS? Specifically, see WSS
Admin Guide title "Managing and Customizing Search" and "Enabling Search"
for more info. I *believe* this error is a symptom of not "Enabling Search"
after upgrading WSS to SQL Server 2000. Below is more info...
Examine the URL associated with this message and check the list of path
rules defined. This URL corresponds to one of the URLs or URL expressions
defined in the path rules. If you are interested in this URL, modify the
path rules. If you are satisfied with the current rules, then this warning
message is benign and can be ignored.
Regards,
John
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:502691A0-7D26-400D-8FD3-932519C47A61@.microsoft.com...
> The crawl seeds error is normally generated by changing the SQL Server
Service account through the services applet in Control Panel.
> Please refer to these kbs for more information on how to solve this error.
> http://support.microsoft.com/default.aspx?scid=kb;en-us;277549
> http://support.microsoft.com/default.aspx?scid=kb;en-us;283811
> http://support.microsoft.com/default.aspx?scid=kb;en-us;308787
> Your error does look a little different from the usual ones. Can you give
us any history about this problem? Do you have Sharepoint Portal Server
2003 or any other server application on this machine?
>
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>

Full Text Error

Hi,
We can successfully create catalogs on a database on our server. However,
we can never get any data from any of the searches. We have since
discovered a few errors in the Application log.
Version of SQL running is:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copy
right (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows
NT 5.2 (Build 3790: )
SP3 has been applied and re-applied.
Errors are as follows:
The crawl on project <SQLServer SQL0000700005> cannot be started. All of the
crawl seeds have been ignored because of host, extension, or other URL
restrictions. Error: 80040d07 - The specified URL is excluded and will not
be cataloged. The URL restriction rules may have to be modified to include
this URL.
One or more warnings or errors for Gatherer project <SQLServer
SQL0000700005> were logged to file <C:\Program Files\Microsoft SQL
Server\MSSQL\FTDATA\SQLServer\GatherLogs
\SQL0000700005.1.gthr>. If you are
interested in these messages, please, look at the file using the gatherer
log query object (gthrlog.vbs, log viewer web page).
The crawl on project <SQLServer SQL0000700005> cannot be started. All of the
crawl seeds have been ignored because of host, extension, or other URL
restrictions. Error: 80040d07 - The specified URL is excluded and will not
be cataloged. The URL restriction rules may have to be modified to include
this URL.
Error from the gthrlog.vbs file reveals the following:
C:\Program Files\Common Files\System\MSSearch\Bin>cscript gthrlog.vbs
"C:\Progra
m Files\Microsoft SQL
Server\MSSQL\FTDATA\SQLServer\GatherLogs
\SQL0000700005.1.g
thr"
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
5/18/2004 11:26:44 AM Add The gatherer has started
5/18/2004 11:26:48 AM Add The initialization has completed
5/18/2004 11:27:16 AM Add Started Full crawl
5/18/2004 11:27:16 AM MSSQL75://SQLServer/75d7831f Add URL is
excluded
because the URL protocol is not recognized or restricted
5/18/2004 11:27:16 AM Add Completed Full crawl
C:\Program Files\Common Files\System\MSSearch\Bin>
Yours desperately.
OsOz,
Hilary, it seems to me that the following "Error: 80040d07 - The specified
URL is excluded and will not be cataloged. The URL restriction rules may
have to be modified to include this URL." and this error is not addressed in
any of the below KB articles.
I previously posted the following info here in the fulltext newsgroup back
in March 2004, "The key error is "80040d07 - The specified URL is excluded
and will not be cataloged". This is very unusual error for SQL FTS, but I
*believe* not so unusual for a SPS/WSS upgrade to SQL Server. Specifically,
the crawl seed is "MSSQL75://SQLServer/75d7831f " which SQL Server 2000 and
your FT enabled table. Did you enable FTS within SPS? Specifically, see WSS
Admin Guide title "Managing and Customizing Search" and "Enabling Search"
for more info. I *believe* this error is a symptom of not "Enabling Search"
after upgrading WSS to SQL Server 2000. Below is more info...
Examine the URL associated with this message and check the list of path
rules defined. This URL corresponds to one of the URLs or URL expressions
defined in the path rules. If you are interested in this URL, modify the
path rules. If you are satisfied with the current rules, then this warning
message is benign and can be ignored.
Regards,
John
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:502691A0-7D26-400D-8FD3-932519C47A61@.microsoft.com...
> The crawl seeds error is normally generated by changing the SQL Server
Service account through the services applet in Control Panel.
> Please refer to these kbs for more information on how to solve this error.
> http://support.microsoft.com/defaul...kb;en-us;277549
> http://support.microsoft.com/defaul...kb;en-us;283811
> http://support.microsoft.com/defaul...kb;en-us;308787
> Your error does look a little different from the usual ones. Can you give
us any history about this problem? Do you have Sharepoint Portal Server
2003 or any other server application on this machine?
>
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>

Full Text Commands in SQL Query?

My host does allow me to create full text catalogs. I use SQL Server Management Studio Express, so I'd have to do it "by hand" as opposed to point-clicking menus and going through wizards. Where do I go to find those commands? I've seen them before but I can't remember where to get them. They're the ones that begin with sp_.

I need the commands for:

Creating a full text catalog

Specifying which columns and tables to enable full text searching

Scheduling when to update the catalog (when to repopulate, etc.)

Clearing the catalog to start over again

Any other handy/necessary commands?

Any help will be appreciated. Thank you.

i sent you that info here:http://forums.asp.net/t/1127286.aspx

|||

i sent you that info here:http://forums.asp.net/t/1127286.aspx

|||

That's creating the catalog and enabling table/column for full-text. I got those.

What about for scheduling population?

|||

1. Activate your database for full-text search:
sp_fulltext_database 'enable'
(Warning! An already existing index will be reset to the default settings.)

2. Create the full text index: To continue, a so-called catalog must be created:
sp_fulltext_catalog 'Fulltextcatalog1','create'
('Fulltextcatalog1' is the name of the catalog for this example)

and a virtual index:
sp_fulltext_table 'Employee','create','Fulltextcatalog1','pkID_Field'
(pkID_Field is the name of the Primary Key of table Employee.)

3. Add the fields that you want to be indexed:
(The fields have to be either the type char, varchar, nchar, nvarchar or text.)
sp_fulltext_column 'Employee','lastname','add'
sp_fulltext_column 'Employee','firstname','add'

where 'lastname' and 'firstname' are the field names used in this example.

4. Next you have to activate the index:
sp_fulltext_table 'Employee','activate'

5. After that the index can be generated with the following command:
sp_fulltext_table 'Employee','start_full'

6. Now activate the 'Change Tracking'. Required for this, is a field with the data
type 'timestamp'. Through this, the newly created index will automatically be
updated, as soon as the data in the columns has been changed.

sp_fulltext_table Employee, 'Start_change_tracking'
sp_fulltext_table Employee, 'Start_background_updateindex'

Deleting Full-text Indexing on a table named fulltext1

1. First delete the index:
sp_fulltext_table 'Employee', 'drop'

2. And then the catalog:
sp_fulltext_catalog 'fulltextcatalog1','drop'

FULL TEXT CATALOGS CANT BE OPEN

I have number of catalogs on my server. when i am clicking on the full text
catalogs section on the enterprise manager the enterprise manager is stucked
and i cant see any catalogs. anyone knows what is the problem? thanks!
Run sp_who2 to see if there is any deadlocking. Also run profiler to
determine what is going on on your system.
Hilary 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
"Ruby Nadler" <RubyNadler@.discussions.microsoft.com> wrote in message
news:EF872289-8106-4DEA-B7E4-8CC6D16842FF@.microsoft.com...
> I have number of catalogs on my server. when i am clicking on the full
text
> catalogs section on the enterprise manager the enterprise manager is
stucked
> and i cant see any catalogs. anyone knows what is the problem? thanks!

Full Text Catalogs and Permission

Hi

When I create a full text catalog via sql code, does the account the sql server is running under need any special permissions, since some files are created?

Or is it just the same as running any other sql code?

Thanks

Hi.

User must have CREATE FULLTEXT CATALOG permission on the database, or be a member of the db_owner, or db_ddladmin fixed database roles.

Full Text Catalogs and Permission

Hi

When I create a full text catalog via sql code, does the account the sql server is running under need any special permissions, since some files are created?

Or is it just the same as running any other sql code?

Thanks

Hi.

User must have CREATE FULLTEXT CATALOG permission on the database, or be a member of the db_owner, or db_ddladmin fixed database roles.

Full text catalogs

I need to move my Full text catalog for SQL 2005 from one location to
another.Is there any way to do it .
Thanks>I need to move my Full text catalog for SQL 2005 from one location to
>another.Is there any way to do it .
You can use ALTER DATABASE or the FOR ATTACH clause of the CREATE DATABASE
statement. There are full-text catalog examples for both of these methods in
the BOL topic Moving User Databases.
ms-help://sql90/udb9/html/ad9a4e92-13fb-457d-996a-66ffc2d55b79.htm
--
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
Download the latest version of Books Online from
http://technet.microsoft.com/en-us/sqlserver/bb428874.aspx
<msnews.microsoft.com> wrote in message
news:OM0w72HAIHA.4752@.TK2MSFTNGP04.phx.gbl...
>I need to move my Full text catalog for SQL 2005 from one location to
>another.Is there any way to do it .
> Thanks
>
>

Full text catalog is paused

I have 2 full text catalogs, and one of them (sometimes both) goes to pause
status occasionally. I suspect this occurs during a backup.
I checked the status of the Microsoft search service and it states that it
is "started", but I've found that restarting the service unpauses the
catalog.
This is an improvement on my previous solution of rebuilding the catalog...
Any ideas what may be causing the pausing?
Or failing that, how can I issue a restart command to the service?
I have VB6 apps running that can detect the paused catalog, so restarting
would be simple if I knew how.
TIA
Message posted via http://www.sqlmonster.com
I should have mentioned that the error from the event log when the pausing
occurs is:
The entry
<MSSQL75://SQLSERVER/619B8048/38323766373135392D356666392D343238342D626235382D30 3738356466653130323562>
cannot be inserted into the history for project <SQLServer SQL0000700006>.
Error: 80070426 - The service has not been started. .
Message posted via http://www.sqlmonster.com
|||Is this a cluster?
"Roger Hocking via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:fea4a010a3224b3aab9c310c37f33da8@.SQLMonster.c om...
>I should have mentioned that the error from the event log when the pausing
> occurs is:
> The entry
> <MSSQL75://SQLSERVER/619B8048/38323766373135392D356666392D343238342D626235382D30 3738356466653130323562>
> cannot be inserted into the history for project <SQLServer SQL0000700006>.
> Error: 80070426 - The service has not been started. .
> --
> Message posted via http://www.sqlmonster.com
|||No, just a single server.
Message posted via http://www.sqlmonster.com

Full Catalog Update

Hi,
I ve found an issue about my seach engine text by using full-text catalogs.
So, my question is.. (maybe is stupid)
How to automatically update the catalog, when I update the tables ?
I ve seen there's a scheduler but does it mean, when I add some records into
the tables, the catalogue is not updated until the procedure starts ?
Stan>
> Hi,
> I ve found an issue about my seach engine text by using full-text
catalogs.
> So, my question is.. (maybe is stupid)
> How to automatically update the catalog, when I update the tables ?
> I ve seen there's a scheduler but does it mean, when I add some records
into
> the tables, the catalogue is not updated until the procedure starts ?
> Stan
--
Here is an extract from SQL Books online:
Maintaining Full-Text Indexes
There are three ways to maintain a full-text index:
Full rebuild
Rescans all rows. Completely rebuilds the full-text index. You can perform
a full rebuild immediately or on a schedule, using SQL Server Agent.
Timestamp-based incremental rebuild
Rescans those rows that have changed since the last full or incremental
rebuild. This requires a timestamp column on the table. Changes that do not
update the timestamp, such as WRITETEXT and UPDATETEXT, are not detected.
You can perform an incremental rebuild immediately or on a schedule.
Change tracking
Maintains a list of all changes to the indexed data. Changes made with
WRITETEXT and UPDATETEXT are not detected. You can update the full-text
index with these changes immediately, on a schedule, or as they occur,
using the background update index option.
The method you use depends on factors such as the CPU and available memory,
the amount and rate of change of data, the amount of available disk space,
and the importance of the full-text index being current. Use these
recommendations as a guide for selecting a maintenance method.
Use change tracking with the background update index option when CPU and
memory are available, the value of an up-to-date index is high, and
immediate propagation can keep up with the rate of changes.
Use change tracking with scheduled propagation when CPU and memory can be
used at scheduled times, disk space for storing changes is available, and
changes between the scheduled times are not so significant that the
propagation takes longer than a full rebuild.
Use a full rebuild when a large percentage of records change or are added
at once. If a large percentage of records change over an extended period of
time, consider using change tracking with scheduled or background update
index.
Use an incremental rebuild when a large number, but not a large percentage,
of documents change at one time. If a large number of records change over
an extended period of time, consider using change tracking with scheduled
or background update index.
Hope this helps,
--
Eric Cárdenas
support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Full Catalog Update

Hi,
I ve found an issue about my seach engine text by using full-text catalogs.
So, my question is.. (maybe is stupid)
How to automatically update the catalog, when I update the tables ?
I ve seen there's a scheduler but does it mean, when I add some records into
the tables, the catalogue is not updated until the procedure starts ?
Stan
>
> Hi,
> I ve found an issue about my seach engine text by using full-text
catalogs.
> So, my question is.. (maybe is stupid)
> How to automatically update the catalog, when I update the tables ?
> I ve seen there's a scheduler but does it mean, when I add some records
into
> the tables, the catalogue is not updated until the procedure starts ?
> Stan
Here is an extract from SQL Books online:
Maintaining Full-Text Indexes
There are three ways to maintain a full-text index:
Full rebuild
Rescans all rows. Completely rebuilds the full-text index. You can perform
a full rebuild immediately or on a schedule, using SQL Server Agent.
Timestamp-based incremental rebuild
Rescans those rows that have changed since the last full or incremental
rebuild. This requires a timestamp column on the table. Changes that do not
update the timestamp, such as WRITETEXT and UPDATETEXT, are not detected.
You can perform an incremental rebuild immediately or on a schedule.
Change tracking
Maintains a list of all changes to the indexed data. Changes made with
WRITETEXT and UPDATETEXT are not detected. You can update the full-text
index with these changes immediately, on a schedule, or as they occur,
using the background update index option.
The method you use depends on factors such as the CPU and available memory,
the amount and rate of change of data, the amount of available disk space,
and the importance of the full-text index being current. Use these
recommendations as a guide for selecting a maintenance method.
Use change tracking with the background update index option when CPU and
memory are available, the value of an up-to-date index is high, and
immediate propagation can keep up with the rate of changes.
Use change tracking with scheduled propagation when CPU and memory can be
used at scheduled times, disk space for storing changes is available, and
changes between the scheduled times are not so significant that the
propagation takes longer than a full rebuild.
Use a full rebuild when a large percentage of records change or are added
at once. If a large percentage of records change over an extended period of
time, consider using change tracking with scheduled or background update
index.
Use an incremental rebuild when a large number, but not a large percentage,
of documents change at one time. If a large number of records change over
an extended period of time, consider using change tracking with scheduled
or background update index.
Hope this helps,
Eric Crdenas
support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

FTS Security Issue

Hi,
FTS will not populate the catalogs. 0 Items.
I have a new installation W2003 with SQL2K Sp3.
The SQL Server is running with a high security configuration.
All the SQL services are running under an account Domain\SQLService which is a plain old user in the domain and on the SQL Server box.
The local system account was chosen during installation. I changed to the domain user via the Enterprise Manager after the fact. SQL Server and SQL Agent run fine. BUILTIN\Administrators has been removed.
I saw a post that said changing the service account from one account and back to the original should fix the problem. It did not. I see "Login failed for NT AUTHORITY\SYSTEM" in the SQL Error Log when I try to build the catalog. I checked the account th
at is running MS Search in the Services dialog and it is still Local System. When I changed accounts on SQL Server, I changed it to myself a local admin and then back to the Domain\SQLService account. I tried changing the MS Search account via the Service
s dialog to Domain\SQLService account and now it will not start. Domain\SQLService has full control on the FTDATA directory. Any other directories or registery keys that perhaps Domain\SQLService needs access to, but is not being set?
Thanks,
Norman
Follow up...
Here are some messages from the event log:
12:14:21 PMSearch Service 7052The Search service has loaded project <SQLServer SQL0002000005>.
12:14:19 PMIndexer 7070The Search service has added project <SQL0002000005>.
12:14:19 PMIndexer 7071The Search service has removed project <SQL0002000005>.
12:14:19 PMIndexer 7042Project <SQLServer SQL0002000005> has been shut down as requested by user.
12:14:05 PMIndexer 7045The catalog was not propagated, because no new files were detected for the project <SQLServer SQL0002000005>.
12:14:05 PMGatherer 3018The end of crawl for project <SQLServer SQL0002000005> has been detected. The Gatherer successfully processed 0 documents totaling 0K. It failed to filter 1 documents. 0 URLs could not be reached or were denied access.
12:14:05 PMGatherer 3024The crawl for project <SQLServer SQL0002000005> could not be started, because no crawl seeds could be accessed. Fix the errors and try the crawl again.
12:14:05 PMGatherer 3036The crawl seed <MSSQL75://SQLServer/37fa4c37> in project <SQLServer SQL0002000005> cannot be accessed. Error: 800700e9 - No process is on the other end of the pipe. .
12:14:04 PMGatherer 3019The crawl on project <SQLServer SQL0002000005> has started.
|||Norman,
The MSSearch service requires that either the BUILTIN\Administrators login
be present or that [NT Authority\System] localsystem login have the below
rights and this is why you are seeing ("Login failed for NT
AUTHORITY\SYSTEM" ) after removing the BUILTIN\Administrators login:
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System','us_english'
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
See also KB article Q263712 "INF: How To Prevent Windows NT Administrators
From Administering a Clustered SQL Server"
at http://support.microsoft.com/default...;EN-US;q263712 for more
info.
Regards,
John
"Norman" <anonymous@.discussions.microsoft.com> wrote in message
news:C6CE845A-0975-4801-8B0B-5B02D848F336@.microsoft.com...
> Follow up...
> Here are some messages from the event log:
> 12:14:21 PM Search Service 7052 The Search service has loaded project
<SQLServer SQL0002000005>.
> 12:14:19 PM Indexer 7070 The Search service has added project
<SQL0002000005>.
> 12:14:19 PM Indexer 7071 The Search service has removed project
<SQL0002000005>.
> 12:14:19 PM Indexer 7042 Project <SQLServer SQL0002000005> has been shut
down as requested by user.
> 12:14:05 PM Indexer 7045 The catalog was not propagated, because no new
files were detected for the project <SQLServer SQL0002000005>.
> 12:14:05 PM Gatherer 3018 The end of crawl for project <SQLServer
SQL0002000005> has been detected. The Gatherer successfully processed 0
documents totaling 0K. It failed to filter 1 documents. 0 URLs could not be
reached or were denied access.
> 12:14:05 PM Gatherer 3024 The crawl for project <SQLServer SQL0002000005>
could not be started, because no crawl seeds could be accessed. Fix the
errors and try the crawl again.
> 12:14:05 PM Gatherer 3036 The crawl seed <MSSQL75://SQLServer/37fa4c37> in
project <SQLServer SQL0002000005> cannot be accessed. Error: 800700e9 - No
process is on the other end of the pipe. .
> 12:14:04 PM Gatherer 3019 The crawl on project <SQLServer SQL0002000005>
has started.
>
|||John,
No kudos to Microsoft for the high level security requiements for MS Search and not providing a KB with a work around for highly secure environments.
FYI:
Even though I found posts that indicate the contrary, the MS Search service remains Local System Account regardless of which account you put in the the SQL Service or SQL Agent at installation or after the fact via the Enterprise Manager. I tried it on se
veral SQL Server installations on W2K and W2003.
My compromise solution was to create a domain account specifically for the MS Search service and make it local admin and sa in the SQL Server. This seems to function correctly for all the test I have tried. The SQL Server service is then still locked down
as long as there are no holes to exploit via the FTS queries. (I won't hold my breath)
Norman
|||Norman,
Unfortunately, I'd have to agree with you. FYI, the "Microsoft Search"
(mssearch.exe) service should ALWAYS be started and running under the
"system" or LocalSystem account as that how it is currently designed in SQL
Server 2000. However, for SQL Server 2005 (Yukon) this has changed and the
new MSSearch service, will be able to run under the same service account as
the MSSQLServer service.
If I was in the SQL MVP program, I'd be glad to volunteer and write such a
KB article, but alas I'm not *yet* in that program...
Regards,
John
"Norman" <anonymous@.discussions.microsoft.com> wrote in message
news:F954B2E0-FCDA-4692-8F80-D10DB1F5F701@.microsoft.com...
> John,
> No kudos to Microsoft for the high level security requiements for MS
Search and not providing a KB with a work around for highly secure
environments.
> FYI:
> Even though I found posts that indicate the contrary, the MS Search
service remains Local System Account regardless of which account you put in
the the SQL Service or SQL Agent at installation or after the fact via the
Enterprise Manager. I tried it on several SQL Server installations on W2K
and W2003.
> My compromise solution was to create a domain account specifically for the
MS Search service and make it local admin and sa in the SQL Server. This
seems to function correctly for all the test I have tried. The SQL Server
service is then still locked down as long as there are no holes to exploit
via the FTS queries. (I won't hold my breath)
> Norman

FTS Catalogs won't populate

Hi

After creating a full text catalog in SQL Server 2000 and performing the initial population, the catalog say has an index count of 1 (should be several thousand) and all "contains" queries return no results. The gather log contains the following error message: Error Fetching URL, (80070002 - The system can not find the file specified) . Any catalog I try to make has the same problem. All catalogs were working fine last week. Any help would be very appreciated.

Thanks!

We are having the exact same problem. Did you find a resolution? Thanks. Also, is your SQL 2000 databases in a SQL cluster? Ours is, but don't know if that's part of the problem.|||Hey, we fixed our problem by re-registering tquery.dll on SQL Server. See http://support.microsoft.com/kb/817301/en-us. Hope this helps.|||Our DB is on a cluster too. I will definitely try your solution tomorrow and see what happens. Thanks!|||Hope it fixes it. Best of luck.

FTS Catalogs won't populate

Hi

After creating a full text catalog in SQL Server 2000 and performing the initial population, the catalog say has an index count of 1 (should be several thousand) and all "contains" queries return no results. The gather log contains the following error message: Error Fetching URL, (80070002 - The system can not find the file specified) . Any catalog I try to make has the same problem. All catalogs were working fine last week. Any help would be very appreciated.

Thanks!

We are having the exact same problem. Did you find a resolution? Thanks. Also, is your SQL 2000 databases in a SQL cluster? Ours is, but don't know if that's part of the problem.|||Hey, we fixed our problem by re-registering tquery.dll on SQL Server. See http://support.microsoft.com/kb/817301/en-us. Hope this helps.|||Our DB is on a cluster too. I will definitely try your solution tomorrow and see what happens. Thanks!|||Hope it fixes it. Best of luck.