Showing posts with label edition. Show all posts
Showing posts with label edition. Show all posts

Thursday, March 29, 2012

General Network Error while backing up databases

Microsoft SQL Server 2000 - 8.00.780 (Intel X86)
Mar 3 2003 10:28:28
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 3)
Client is Windows XP SP 1
I have this intermittent problem when attempting to backup a database
from another machine. Each time SQL Server communicates back the
status of the backup, I get a general network error as follows:
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
(WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
10 percent backed up.
Connection Broken
My backup script is very simple, as I am just backing up a test
database:
BACKUP DATABASE Development
TO DISK = 'Development_2003_09_04.bak'
WITH STATS = 10
It is not a query timeout, because I checked. I also varied the STATS
parameter to smaller values and the connection breaks at different
times, as follows:
Disconnect@.15 seconds:
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
(WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
10 percent backed up.
Connection Broken
Disconnect@.9 seconds:
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
(WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
5 percent backed up.
Connection Broken
Disconnect@.4 seconds:
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
(WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
2 percent backed up.
Connection Broken
The SQL Server log only lists that the backup fails, but doesn't give
a reason. The event log also listed the backup failures but didn't
give any more information than the sql log. I did notice the
following error in the server's application log:
Event Type: Error
Event Source: MSSQLServer
Event Category: (8)
Event ID: 19011
Date: 9/4/2003
Time: 3:02:29 AM
User: N/A
Computer: DAEDALUS
Description:
SuperSocket info: Failed to get Exclusive port use(MSAFD Tcpip
[TCP/IP]) : Error 10013.
followed by this warning:
Event Type: Warning
Event Source: MSSQLServer
Event Category: (8)
Event ID: 19011
Date: 9/4/2003
Time: 3:02:30 AM
User: N/A
Computer: DAEDALUS
Description:
SuperSocket info: (SpnRegister) : Error 8344.
Ideas?
Brandon Lilly
--
"In the beginning the universe was created. This has made a lot of
people very angry, and has been widely regarded as a bad move." -
Douglas Noel Adams (1952-2001)"jeff" <jeff@.hotmail.com> wrote in message
news:217001c37318$11a76be0$a601280a@.phx.gbl...
> Looks like a permission issue. Try adding sql server
> startup account to local NT admin, restart sql server,
> connect using sysadmin or sa from the xp client, and issue
> backup command again.
I added the account to Builtin\Administrators and also to Domain
Admins to no avail. After stopping and starting SQL Server, the
backup command would still fail if run from my client, regardless of
whether I logged in as SA, or using windows authentication (I am the
domain admin).
I am able to backup a different database remotely, but it is very
small (< 3MB) as opposed to the development database which is about 1
GB. They have the same security.
Brandon
--
"In the beginning the universe was created. This has made a lot of
people very angry, and has been widely regarded as a bad move." -
Douglas Noel Adams (1952-2001)|||I don't know anything more on this. Try posting your
question to microsoft.public.win2000.networking group, or
to one of winsock progrrammers group.
Good luck.
>--Original Message--
>"jeff" <jeff@.hotmail.com> wrote in message
>news:217001c37318$11a76be0$a601280a@.phx.gbl...
>> Looks like a permission issue. Try adding sql server
>> startup account to local NT admin, restart sql server,
>> connect using sysadmin or sa from the xp client, and
issue
>> backup command again.
>I added the account to Builtin\Administrators and also to
Domain
>Admins to no avail. After stopping and starting SQL
Server, the
>backup command would still fail if run from my client,
regardless of
>whether I logged in as SA, or using windows
authentication (I am the
>domain admin).
>I am able to backup a different database remotely, but it
is very
>small (< 3MB) as opposed to the development database
which is about 1
>GB. They have the same security.
>Brandon
>--
>"In the beginning the universe was created. This has
made a lot of
>people very angry, and has been widely regarded as a bad
move." -
>Douglas Noel Adams (1952-2001)
>
>.
>|||Brandon,
I am a little confused as to what your actually trying to do. You state
your backing up to a remote server but your backup command does not show
that.
> BACKUP DATABASE Development
> TO DISK = 'Development_2003_09_04.bak'
> WITH STATS = 10
Actually it doesn't show a location at all. You should probably be using
UNC to specify the device if it's remote.
--
Andrew J. Kelly
SQL Server MVP
"Brandon Lilly" <brandon.lilly@.nospam_medevolve.com> wrote in message
news:epoqWBwcDHA.2436@.TK2MSFTNGP12.phx.gbl...
> Microsoft SQL Server 2000 - 8.00.780 (Intel X86)
> Mar 3 2003 10:28:28
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 3)
>
> Client is Windows XP SP 1
>
> I have this intermittent problem when attempting to backup a database
> from another machine. Each time SQL Server communicates back the
> status of the backup, I get a general network error as follows:
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> 10 percent backed up.
> Connection Broken
>
> My backup script is very simple, as I am just backing up a test
> database:
> BACKUP DATABASE Development
> TO DISK = 'Development_2003_09_04.bak'
> WITH STATS = 10
>
> It is not a query timeout, because I checked. I also varied the STATS
> parameter to smaller values and the connection breaks at different
> times, as follows:
> Disconnect@.15 seconds:
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> 10 percent backed up.
> Connection Broken
>
> Disconnect@.9 seconds:
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> 5 percent backed up.
> Connection Broken
>
> Disconnect@.4 seconds:
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> 2 percent backed up.
> Connection Broken
>
> The SQL Server log only lists that the backup fails, but doesn't give
> a reason. The event log also listed the backup failures but didn't
> give any more information than the sql log. I did notice the
> following error in the server's application log:
>
> Event Type: Error
> Event Source: MSSQLServer
> Event Category: (8)
> Event ID: 19011
> Date: 9/4/2003
> Time: 3:02:29 AM
> User: N/A
> Computer: DAEDALUS
> Description:
> SuperSocket info: Failed to get Exclusive port use(MSAFD Tcpip
> [TCP/IP]) : Error 10013.
> followed by this warning:
> Event Type: Warning
> Event Source: MSSQLServer
> Event Category: (8)
> Event ID: 19011
> Date: 9/4/2003
> Time: 3:02:30 AM
> User: N/A
> Computer: DAEDALUS
> Description:
> SuperSocket info: (SpnRegister) : Error 8344.
> Ideas?
>
> Brandon Lilly
> --
> "In the beginning the universe was created. This has made a lot of
> people very angry, and has been widely regarded as a bad move." -
> Douglas Noel Adams (1952-2001)
>|||OK, I see now.. It looks like your using named pipes, have you tried
connecting with tcp instead and see if that makes any difference?
--
Andrew J. Kelly
SQL Server MVP
"Brandon Lilly" <brandon.lilly@.nospam_medevolve.com> wrote in message
news:u5jcPl%23cDHA.2392@.TK2MSFTNGP10.phx.gbl...
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:Oji9ot7cDHA.2564@.TK2MSFTNGP09.phx.gbl...
> > I am a little confused as to what your actually trying to do. You
> state
> > your backing up to a remote server but your backup command does not
> show
> > that.
> > Actually it doesn't show a location at all. You should probably be
> using
> > UNC to specify the device if it's remote.
> I am backing up a remote server, meaning that I am not at that machine
> running query analyzer - I am at a client machine on the domain
> executing the backup script. I don't specify a location, because I am
> just wanting it to backup to the default location
> Sorry if my post was misleading.
> Brandon
> --
> "In the beginning the universe was created. This has made a lot of
> people very angry, and has been widely regarded as a bad move." -
> Douglas Noel Adams (1952-2001)
>

Friday, March 23, 2012

Fuzzy Lookup/product level is insufficient

I installed SQL Server 2005 Standard Edition on my XP sp2 workstation, developed an SSIS package, which has run for a week on my workstation.

I installed SQL Server 2005 Standard Edition on a Win2003 sp1 server, created the dtsx and install manifest on my workstation, and installed it on the server.

If I run the package on my workstation, pointed to the server database it runs fine.

If I run the dtsx on the server, it fails with the error:

The product level is insufficient for component "Fuzzy Lookup on Name" (83)

Yes, I have SSIS installed on both machines, I have verified that I have the SSIS service on the server.

Any Ideas?

Thanks!

BobP

Bob,
Fuzzy Lookup/Fuzzy Grouping components are part of the Advanced Transformations that are only available in the Enterprise Edition of SQL.
Per MS all transformations/features are available in the BIDS when you are developing. So you really need to becareful about what features you use in your packages.
Larry Poep|||

Thanks
BobP

Sunday, February 26, 2012

Full-Text-Search

Hi friends

i work with sql server 2005 express(Management Studio)

can i use full text search service with that edition of sql server?

and how i can use that.

thank u.Smile [:)]

The Full-Text Search feature is not available in SQL Server 2005 Express.

HTH,
Ryan

|||

thank u for ur answering.

so which edition of sql server support that?

|||

fahima wrote:

so which edition of sql server support that?

The Workgroup, Standard, and Enterprise editions all support Full-text Search.

HTH,
Ryan

|||

ok

is it hard to work with service?

|||

fahima wrote:

is it hard to work with service?

Do you mean is it difficult to get Full-text Search to work? I've never played with Full-text Search, but here's an article that should give you a better understanding of it:Understanding SQL Server Full-Text Indexing.

HTH,
Ryan

|||

the Express Edition does in fact have full text search feature available. to get this you need to download a different file, SQL Server with Advance services -http://msdn.microsoft.com/vstudio/express/sql/compare/default.aspx

Not sure if this was released since the last post here - just though i would answer seeing as i was floating around.

regards

Friday, February 24, 2012

Full-Text Search Error - Server: Msg 7635 The Microsoft Search service cannot be administered un

Hello and thank you for your assistance.

I have two instances of SQL Server 2000 Enterprise Edition (SP4) database running on Windows 2000 Enterprise server. The default instance is dev and a named instance for QA. Full-text search is enabled for dev and is functioning properly.

@.@.Version:

Microsoft SQL Server 2000 - 8.00.2040 (Intel X86) May 13 2005 18:33:17 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

I am trying to enable full text search in the QA instance with this command: "sp_fulltext_database 'enable' ", but I am receiving the error "Server: Msg 7635 The Microsoft Search service cannot be administered under the present user account.

I can find any reference to what account it needs to run under. Can you provide me with info on why I am getting this message?

This is a common error with SQL Server 2000 Full-text Search (FTS) and the MSSearch service and there can be a few root reasons for it.

1. Did this error occur after a service pack upgrade? If so - review the files and folders under \FTDATA (in the sql server installed instance folder) against what is on your SQL Server 2000 CD. If you find any difference - copy the missing or different file from the CD to the problem server.

2. Have you removed the BUILTIN\Administrators login? If so - either add it back in or execute the sp_grantlogin from the code below as the MSSearch service requires this level of access to the MSSQLServer service.

3. Check these:
317746 PRB: SQL Server Full-Text Search Does Not Populate Catalogs
http://support.microsoft.com/kb/317746
277549 PRB: Unable to Build Full-Text Catalog After You Modify MSSQLServer Logon Account Through Control Panel
http://support.microsoft.com/kb/277549

4. Can you run this script and post the results back?

use master
go
SELLECT @.@.version
go
-- many need to set on "show advanced options"
sp_configure 'default full-text language'
go
SELECT FullTextServiceProperty('ResourceUsage') as MSSearch_Resource_Usage
go
xp_logininfo 'BUILTIN\ADMINISTRATORS', 'members'
go

-- if you have removed the BUILTIN\Administrators login, run:

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

5. And just to cover all the bases, when you changed the MSSQLServer startup account, did you do it via Win2K's Component Services? If so, could you "re-change" it via the Enterprise Manager's server property security tab?

Filip Skakun

|||

Filip,

Thank you so much for your response. To answer your questions; No we haven't added any service packs recently. Yes, we do have the Builtin/Administer removed and the NT Authority has all the required privileges. Keep in mind that the default instance was working just fine.

Since the MSSQL$Inst2/FTData directory didn't exist; I suspect that FullText search was not installed with the second instance. None the less, I re-installed fulltext search (see http://support.microsoft.com/kb/827449). After doing this I no longer received the "Cannot be administered under the present account" error and the FTData directory was created for the second instance. But, at this point Full text search didn't work for both instances. I wasn't receiving any errors, but the catalogs were not getting populated. We later found that the switch in the KB article was incorrect for our servers. The article had us run "ftsetup.exe SQLServer$Instance 1 0 0 0" (incorrect). After we ran "ftsetup.exe SQLServer$Instance 0 1 0 0 0" (correct) FullText search began to function correctly for both instances.

To be honest, I don't think I had to reinstall everything. I believe I could have gotten away with just running ftsetup.exe for the second instance.

|||

I am glad you got it working,

Regards,
Filip

Full-Text Search Error - Server: Msg 7635 The Microsoft Search service cannot be administered un

Hello and thank you for your assistance.

I have two instances of SQL Server 2000 Enterprise Edition (SP4) database running on Windows 2000 Enterprise server. The default instance is dev and a named instance for QA. Full-text search is enabled for dev and is functioning properly.

@.@.Version:

Microsoft SQL Server 2000 - 8.00.2040 (Intel X86) May 13 2005 18:33:17 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

I am trying to enable full text search in the QA instance with this command: "sp_fulltext_database 'enable' ", but I am receiving the error "Server: Msg 7635 The Microsoft Search service cannot be administered under the present user account.

I can find any reference to what account it needs to run under. Can you provide me with info on why I am getting this message?

This is a common error with SQL Server 2000 Full-text Search (FTS) and the MSSearch service and there can be a few root reasons for it.

1. Did this error occur after a service pack upgrade? If so - review the files and folders under \FTDATA (in the sql server installed instance folder) against what is on your SQL Server 2000 CD. If you find any difference - copy the missing or different file from the CD to the problem server.

2. Have you removed the BUILTIN\Administrators login? If so - either add it back in or execute the sp_grantlogin from the code below as the MSSearch service requires this level of access to the MSSQLServer service.

3. Check these:
317746 PRB: SQL Server Full-Text Search Does Not Populate Catalogs
http://support.microsoft.com/kb/317746
277549 PRB: Unable to Build Full-Text Catalog After You Modify MSSQLServer Logon Account Through Control Panel
http://support.microsoft.com/kb/277549

4. Can you run this script and post the results back?

use master
go
SELLECT @.@.version
go
-- many need to set on "show advanced options"
sp_configure 'default full-text language'
go
SELECT FullTextServiceProperty('ResourceUsage') as MSSearch_Resource_Usage
go
xp_logininfo 'BUILTIN\ADMINISTRATORS', 'members'
go

-- if you have removed the BUILTIN\Administrators login, run:

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

5. And just to cover all the bases, when you changed the MSSQLServer startup account, did you do it via Win2K's Component Services? If so, could you "re-change" it via the Enterprise Manager's server property security tab?

Filip Skakun

|||

Filip,

Thank you so much for your response. To answer your questions; No we haven't added any service packs recently. Yes, we do have the Builtin/Administer removed and the NT Authority has all the required privileges. Keep in mind that the default instance was working just fine.

Since the MSSQL$Inst2/FTData directory didn't exist; I suspect that FullText search was not installed with the second instance. None the less, I re-installed fulltext search (see http://support.microsoft.com/kb/827449). After doing this I no longer received the "Cannot be administered under the present account" error and the FTData directory was created for the second instance. But, at this point Full text search didn't work for both instances. I wasn't receiving any errors, but the catalogs were not getting populated. We later found that the switch in the KB article was incorrect for our servers. The article had us run "ftsetup.exe SQLServer$Instance 1 0 0 0" (incorrect). After we ran "ftsetup.exe SQLServer$Instance 0 1 0 0 0" (correct) FullText search began to function correctly for both instances.

To be honest, I don't think I had to reinstall everything. I believe I could have gotten away with just running ftsetup.exe for the second instance.

|||

I am glad you got it working,

Regards,
Filip

Full-Text Search Error - Server: Msg 7635 The Microsoft Search service cannot be administere

Hello and thank you for your assistance.

I have two instances of SQL Server 2000 Enterprise Edition (SP4) database running on Windows 2000 Enterprise server. The default instance is dev and a named instance for QA. Full-text search is enabled for dev and is functioning properly.

@.@.Version:

Microsoft SQL Server 2000 - 8.00.2040 (Intel X86) May 13 2005 18:33:17 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

I am trying to enable full text search in the QA instance with this command: "sp_fulltext_database 'enable' ", but I am receiving the error "Server: Msg 7635 The Microsoft Search service cannot be administered under the present user account.

I can find any reference to what account it needs to run under. Can you provide me with info on why I am getting this message?

This is a common error with SQL Server 2000 Full-text Search (FTS) and the MSSearch service and there can be a few root reasons for it.

1. Did this error occur after a service pack upgrade? If so - review the files and folders under \FTDATA (in the sql server installed instance folder) against what is on your SQL Server 2000 CD. If you find any difference - copy the missing or different file from the CD to the problem server.

2. Have you removed the BUILTIN\Administrators login? If so - either add it back in or execute the sp_grantlogin from the code below as the MSSearch service requires this level of access to the MSSQLServer service.

3. Check these:
317746 PRB: SQL Server Full-Text Search Does Not Populate Catalogs
http://support.microsoft.com/kb/317746
277549 PRB: Unable to Build Full-Text Catalog After You Modify MSSQLServer Logon Account Through Control Panel
http://support.microsoft.com/kb/277549

4. Can you run this script and post the results back?

use master
go
SELLECT @.@.version
go
-- many need to set on "show advanced options"
sp_configure 'default full-text language'
go
SELECT FullTextServiceProperty('ResourceUsage') as MSSearch_Resource_Usage
go
xp_logininfo 'BUILTIN\ADMINISTRATORS', 'members'
go

-- if you have removed the BUILTIN\Administrators login, run:

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

5. And just to cover all the bases, when you changed the MSSQLServer startup account, did you do it via Win2K's Component Services? If so, could you "re-change" it via the Enterprise Manager's server property security tab?

Filip Skakun

|||

Filip,

Thank you so much for your response. To answer your questions; No we haven't added any service packs recently. Yes, we do have the Builtin/Administer removed and the NT Authority has all the required privileges. Keep in mind that the default instance was working just fine.

Since the MSSQL$Inst2/FTData directory didn't exist; I suspect that FullText search was not installed with the second instance. None the less, I re-installed fulltext search (see http://support.microsoft.com/kb/827449). After doing this I no longer received the "Cannot be administered under the present account" error and the FTData directory was created for the second instance. But, at this point Full text search didn't work for both instances. I wasn't receiving any errors, but the catalogs were not getting populated. We later found that the switch in the KB article was incorrect for our servers. The article had us run "ftsetup.exe SQLServer$Instance 1 0 0 0" (incorrect). After we ran "ftsetup.exe SQLServer$Instance 0 1 0 0 0" (correct) FullText search began to function correctly for both instances.

To be honest, I don't think I had to reinstall everything. I believe I could have gotten away with just running ftsetup.exe for the second instance.

|||

I am glad you got it working,

Regards,
Filip

Sunday, February 19, 2012

FullText Search & SQL Server Express Edition

Does SQL Server Express Edition with advanced Features Support Full text
Search, I am really confused because I have some resources telling that it
does support and others telling it don't
thank you
Hello yaser,
SQLExpress doesn't, SQL Express with Advanced Features does
http://msdn.microsoft.com/vstudio/express/sql/compare/default.aspx
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons

> Does SQL Server Express Edition with advanced Features Support Full
> text Search, I am really confused because I have some resources
> telling that it does support and others telling it don't
> thank you
>
|||Thank you Simon for your Reply

full-text queries with express edition

Hi,
I understand that full-text indexing is not available in the express
edition.
My situation is that we have to write an application to take advantage of
full-text-indexing when available.
Quesitions are.
1. Does "freetext" and "contains" queries works on express edition?
(by doing a full table scan or something like that)
2. If it does not, how do I write the c# that recognize the capability,
so that c# code can send/execute different queries based on
"full-text-capability" of sql-server.
any direction is deeply appreciated.
Thanks
Nalaka
1) It currently does not work on SQL FTS.
2) I believe the February issue of SQL Server pro has an article on how to
get this working using pure tsql.
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
"Nalaka" <nalaka12@.nospam.nospam> wrote in message
news:u%23h7eJNMGHA.2336@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I understand that full-text indexing is not available in the express
> edition.
> My situation is that we have to write an application to take advantage of
> full-text-indexing when available.
> Quesitions are.
> 1. Does "freetext" and "contains" queries works on express edition?
> (by doing a full table scan or something like that)
> 2. If it does not, how do I write the c# that recognize the capability,
> so that c# code can send/execute different queries based on
> "full-text-capability" of sql-server.
> any direction is deeply appreciated.
> Thanks
> Nalaka
>
|||Nalaka wrote on Mon, 13 Feb 2006 11:19:10 -0800:

> Hi,
> I understand that full-text indexing is not available in the express
> edition.
> My situation is that we have to write an application to take advantage of
> full-text-indexing when available.
> Quesitions are.
> 1. Does "freetext" and "contains" queries works on express edition?
> (by doing a full table scan or something like that)
> 2. If it does not, how do I write the c# that recognize the capability,
> so that c# code can send/execute different queries based on
> "full-text-capability" of sql-server.
> any direction is deeply appreciated.
In my code I first do the following:
select FULLTEXTCATALOGPROPERTY('STKcatalog', 'ItemCount'),
FULLTEXTCATALOGPROPERTY('STKcatalog', 'PopulateStatus')
If NULLs returned, FTS is not available for the named catalog (in my case
STKcatalog). I also use these values to double check whether the index is
being rebuilt, and to make sure that the ItemCount value is close to my
table row count. This way if there is not FTS catalog, or it's being
populated, I can switch my query to use LIKE rather than CONTAINS.
Dan