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 search on views in express edition

Hi
Is full text indexing possible on views in SQL server express edition with
advanced services? If Yes then how to do it on a view where I want to do
full text search on five different columns?
Thanks
ontario, canada
I am fairly certain that you can only have one full-text index per table or
*indexed* view. So, if your view is not indexed, you will need to create
your FT index on the underlying table(s).
"db" <db@.discussions.microsoft.com> wrote in message
news:70DFE058-91C8-4D1D-96A7-277113460FB3@.microsoft.com...
> Hi
> Is full text indexing possible on views in SQL server express edition with
> advanced services? If Yes then how to do it on a view where I want to do
> full text search on five different columns?
> Thanks
> --
> ontario, canada
|||I created a full text index on the base table. Will use base table(L.B22) and
not view using syntex:
create fulltext index on L.B22
key index ui_fts22 on B221_fulltextcatalog
with change_tracking AUTO
Now I want to
1. View details about full text index in my database/table.
2. When I created index I created it on one column. I want to use full text
search on multiple columns. Can I add more columns and if yes how.
ontario, canada
"Aaron Bertrand [SQL Server MVP]" wrote:

> I am fairly certain that you can only have one full-text index per table or
> *indexed* view. So, if your view is not indexed, you will need to create
> your FT index on the underlying table(s).
>
>
> "db" <db@.discussions.microsoft.com> wrote in message
> news:70DFE058-91C8-4D1D-96A7-277113460FB3@.microsoft.com...
>
>

full text search on views in express edition

Hi
Is full text indexing possible on views in SQL server express edition with
advanced services? If Yes then how to do it on a view where I want to do
full text search on five different columns?
Thanks
--
ontario, canadaI am fairly certain that you can only have one full-text index per table or
*indexed* view. So, if your view is not indexed, you will need to create
your FT index on the underlying table(s).
"db" <db@.discussions.microsoft.com> wrote in message
news:70DFE058-91C8-4D1D-96A7-277113460FB3@.microsoft.com...
> Hi
> Is full text indexing possible on views in SQL server express edition with
> advanced services? If Yes then how to do it on a view where I want to do
> full text search on five different columns?
> Thanks
> --
> ontario, canada|||I created a full text index on the base table. Will use base table(L.B22) and
not view using syntex:
create fulltext index on L.B22
key index ui_fts22 on B221_fulltextcatalog
with change_tracking AUTO
Now I want to
1. View details about full text index in my database/table.
2. When I created index I created it on one column. I want to use full text
search on multiple columns. Can I add more columns and if yes how.
ontario, canada
"Aaron Bertrand [SQL Server MVP]" wrote:
> I am fairly certain that you can only have one full-text index per table or
> *indexed* view. So, if your view is not indexed, you will need to create
> your FT index on the underlying table(s).
>
>
> "db" <db@.discussions.microsoft.com> wrote in message
> news:70DFE058-91C8-4D1D-96A7-277113460FB3@.microsoft.com...
> >
> > Hi
> >
> > Is full text indexing possible on views in SQL server express edition with
> > advanced services? If Yes then how to do it on a view where I want to do
> > full text search on five different columns?
> >
> > Thanks
> > --
> > ontario, canada
>
>

Full Text Search Installation doesn't work??

I installed Full Text Search on my Standard Personal
Edition following the steps in this Microsoft Link:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;827449&Product=sql2k
When I try to enable full text search, I get the following
error message. Can anyone help? :
Server: Msg 7609, Level 17, State 2, Procedure
sp_fulltext_database, Line 46
Full-Text Search is not installed, or a full-text
component cannot be loaded.
I can see Microsoft search (which I didn't before) on the
Service Manager. I have also started the service. Why
does it show grayed out in Enterprise Mananager - Tools -
Full Text Indexing - eventhough I installed it? Please
HELPPPPP. Thanks
JohnCan anybody help me with this Please. I am waiting
desperately. The installation seemed fine but I dont seem
to see the Full Text Indexing thing - it is grayed out in
Enterprise Manager and not found in suporting services.
Help!!!!
John
>--Original Message--
>I installed Full Text Search on my Standard Personal
>Edition following the steps in this Microsoft Link:
>http://support.microsoft.com/default.aspx?scid=kb;en-
>us;827449&Product=sql2k
>When I try to enable full text search, I get the
following
>error message. Can anyone help? :
>Server: Msg 7609, Level 17, State 2, Procedure
>sp_fulltext_database, Line 46
>Full-Text Search is not installed, or a full-text
>component cannot be loaded.
>I can see Microsoft search (which I didn't before) on the
>Service Manager. I have also started the service. Why
>does it show grayed out in Enterprise Mananager - Tools -
>Full Text Indexing - eventhough I installed it? Please
>HELPPPPP. Thanks
>John
>.
>|||I fixed the problem. Reapply SP3a fixed the Full Text
problem. Thx.
John
>--Original Message--
>Can anybody help me with this Please. I am waiting
>desperately. The installation seemed fine but I dont
seem
>to see the Full Text Indexing thing - it is grayed out in
>Enterprise Manager and not found in suporting services.
>Help!!!!
>John
>
>>--Original Message--
>>I installed Full Text Search on my Standard Personal
>>Edition following the steps in this Microsoft Link:
>>http://support.microsoft.com/default.aspx?scid=kb;en-
>>us;827449&Product=sql2k
>>When I try to enable full text search, I get the
>following
>>error message. Can anyone help? :
>>Server: Msg 7609, Level 17, State 2, Procedure
>>sp_fulltext_database, Line 46
>>Full-Text Search is not installed, or a full-text
>>component cannot be loaded.
>>I can see Microsoft search (which I didn't before) on
the
>>Service Manager. I have also started the service. Why
>>does it show grayed out in Enterprise Mananager - Tools -
>>Full Text Indexing - eventhough I installed it? Please
>>HELPPPPP. Thanks
>>John
>>.
>.
>

Full Text Search for Stand Alone Windows App

I am working on a stand-alone windows application in which I need to provide full text search capability. I was using SQL Express edition and was planning to deploy the database (.mdf) with the application.

Is it possible to enable Full Text search for a database which does not belong to a database server (embedded with the app)? If yes the how can you do it?

If its not possible then what are the alternatives/options of data-storage for a windows app which will allow me to enable Full Text search?

Thanks for your help.

To enable full text search your sever must be installed with this capability.

To enable this capability in the sql server 2005 express edition, you have to download the sql server 2005 express edition advanced. This will install the database server, the sql managment studio and the full text serch.

|||

Thanks for your reply. However I already have the "advanced services" installed but my full text button is still disabled in VS Server Explorer.

If I add the database on a named instance for instance MyBox\SQLExpress then i get an option of enabling the Full Text Search but I dont see any option for a stand-alone database file.

|||

Hi,

I would like to introduce some good video learning resources to you which demonstrates how to set up Full-Text within SQL Server Express.These resources demonstrate how to set up Full-Text search paying particular attention to the nuances of setting it up within SQL Server Express.

http://msdn.microsoft.com/vstudio/express/sql/learning/default.aspx#13

Hope that helps. Thanks.

|||

Thanks a lot for your reply. I found out that full text is not available for "user instances" that is why I am not able to get it to work.

I think I may just have to go with SQL Lite. Does any one know any other database solution which might be better then this? Thanks.

Full Text indexing using sql server 2005 express edition

Hi everyone,

Can someone help me out in providing guidelines towards how to do full text indexing using sql server 2005 express edition?

Thanks in advance

Regards,

Dave

Do you have the Advanced Edition of SQL Server Express ? Only this one supports the fulltext search capabilites.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

Full text indexing question

All,

I am using the standard edition of SQL Server 2005.

I have a table I want to put a full text index on but it is greyed out. What are the reasons why it would be greyed out?

Thx

jonp

Jonp,
Assuming you're using the standard edition of SQL Server 2005 RTM and that the SQL Server FullText Search (msftesql.exe) service is installed and running, there should be no reasong for the "defining full text index" content menu item to be grayed out.

Could you post the full output of @.@.version from the server where this problem exists as well as confirm that the SQL Server FullText Search (msftesql.exe) service is installed and running on this server?

Thanks,
John
SQL 2005 Full Text Search Blog
http://spaces.msn.com/members/jtkane/|||

I verified it was running on the box.

I had to do the following :

USE customer

EXEC sp_fulltext_database 'enable'

After that all seems to work. Any reason why it wouldnt be enabled initially?

|||Cool...
Is it possible that your database 'customer' was in 80 compatability mode? Could you check that via the following SQL code?

EXEC sp_dbcmptlevel 'customer'
-- should return: The current compatibility level is 90.

Thanks,
John
SQL 2005 Full Text Search Blog
http://spaces.msn.com/members/jtkane/

|||

It is 90. Does that just mean that I am using SQL Server 2005?

I assume 80 would be SQL Server 2000, right?

|||Yes, it does or specificlly, it means that the database 'customer' is in '90' or the default SQL Server 2005 database compatibility mode. If it had returned '80', that would indicate that the 'customer' database on your SQL Server 2005 server was in '80' or SQL Server 2000 compatibility mode.

However, SQL Server 2005 compatiblity mode (90) databases are FT-enabled by default and using sp_fulltext_database to FT-enable should not be necessary, unless at sometime in the past this database was specificly disabled via sp_fulltext_database. I'm not sure if you can confirm that, however, if you use standard create database scripts that may do this, please review them.

Thanks,
John|||

Not quite John. Databases created using create database have full text enabled by default. However databases created through management studio you have to explictly check the full text box to enable full text.

I raised this and got a half hearted response. Basically the default setting in management studio is the opposite of that stated in BOL.

http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=24d1edf0-3e4c-4bac-bc6e-51b143ca5322

To correct the issue, go to the database properties and on the files section check the full tec check box.

Full text indexing parentheses and special characters

select @.@.version
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
How you tell the indexer (SQL 2K with WIN2K) to include () , /, - and all other special characters while generating the index? These characters aren't in the noise.eng file and I can't seem to figure out how to index them.
The reason we need these characters indexed is because of searches like "4 (1 1/2)" where only records with the exact phrase should be returned. Currently records with 4 1/2 and 4 1 1/2 are being returned as well and we need to eliminate them.
Naresh
Naresh,
First of all, thanks for providing your SQL Server and OS platform version
info as the latter is especially important for this issue.
Unfortunately, the means to control the use of punctuation (all the special
characters) is not accessible, nor controllable via any registry key/value,
dbcc or trace flag as this is a big issue for many SQL FTS customers that is
not addressed in SQL Server 2000 with the MSSearch service.
There is some improvement via the OS-supplied wordbreaker in Win2003
(langwrbk.dll) over the Win2K supplied wordbreaker (infosoft.dll), however,
neither OS provides any means to control how the MSSearch service handles
these use of punctuation in the FT indexing process. Note, this may or may
not change in the next release of SQL Server 2005 (codename Yukon) that will
ship with its own wordbreaker (langwrbk.dll).
You may also want to experiment with using FREETEXT vs. CONTAINS on Win2K
and Win2003 to get the best results possible in your environment.
Regards,
John
PS: If I had my way this and the noise word file would be at the table level
and not at the OS level, but then that's just wishful thinking after many
years of having to answer this question... :-)
"Naresh Rajpal" <RajpalN@.sullcrom.com> wrote in message
news:97E163D6-1CB6-4947-B9AA-096FC28FC631@.microsoft.com...
> select @.@.version
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> How you tell the indexer (SQL 2K with WIN2K) to include () , /, - and all
other special characters while generating the index? These characters
aren't in the noise.eng file and I can't seem to figure out how to index
them.
> The reason we need these characters indexed is because of searches like "4
(1 1/2)" where only records with the exact phrase should be returned.
Currently records with 4 1/2 and 4 1 1/2 are being returned as well and we
need to eliminate them.
> Naresh
>
>

Full Text Indexing on Microsoft SQL Server 2000 with Windows XP Pro

I am wondering if FUll Text Indexing is suported with MS SQL Server 2000
Developer Edition on XP Pro SP2 . I have the service installed and setup. I
have created several catalogs with data but when they are done populating
they show up with an Item Count of 0 and a Unique Index of 1 despite the
fact that there are 10+ records with extremely different data in the 3
columns that are being indexed.
I am not seeing any unusual messages in the Event Viewer also. I have
uninstalled and reinstalled already and the Server is running under an
Administrator User
Hi,
Thanks for your post.
From your descriptions, I understood that you would like to know whether
Full-Text Search is support in SQL Server Dev Edition and how to implement
it. Have I understood you? Correct me if I was wrong.
Based on my scope, Full-Text Search is supported in SQL Server 2000 Dev
Edition on Windows XP Pro. See more deatiled descritption about this in the
following links
Features Supported by the Editions of SQL Server 2000
http://msdn.microsoft.com/library/de...us/architec/8_
ar_ts_1cdv.asp
For the second question, I am not sure your detailed steps on how to
implement the Full-Text Search for the Table, would you please give me more
detail information about doing so? Here is an sample doing this with SQL
Server Enterprise Manager.
1. enable a table for full-text indexing
- Expand Databases, expand the database in which the table belongs, and
then click Tables.
- In the details pane, right-click the table, click Full-Text Index Table,
and then click Define Full-Text Indexing on a Table.
2. To create a full-text catalog
- right-click the database where you want the full-text catalog.
- Click New, and then click New Full-Text Catalog.
- Complete the New Full-Text Catalog dialog box.
3. Make a Full Populating
- expand the database that contains the full-text catalog to rebuild.
- Click Full-Text Catalogs, and then right-click the specific catalog to
populate.
- Click Start Full Population
4. See whether the data had been updated
- right-click the specific catalog to review.
- Click Properties, and then click the Status, Tables, and Schedules tabs,
as appropriate.
See the following chapter in Books Online or MSDN Online for more detailed
information
Creating and Maintaining Databases -> Full-Text Indexes ->
Administering Full-Text Features Using SQL Enterprise Manager
Hope this helps and please feel free to let me know whether it works or you
need furhter help. Thank you for your patience and corporation.
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Full Text Indexing on Microsoft SQL Server 2000 with Windows XP Pro

I am wondering if FUll Text Indexing is suported with MS SQL Server 2000
Developer Edition on XP Pro SP2 . I have the service installed and setup. I
have created several catalogs with data but when they are done populating
they show up with an Item Count of 0 and a Unique Index of 1 despite the
fact that there are 10+ records with extremely different data in the 3
columns that are being indexed.
I am not seeing any unusual messages in the Event Viewer also. I have
uninstalled and reinstalled already and the Server is running under an
Administrator UserHi,
Thanks for your post.
From your descriptions, I understood that you would like to know whether
Full-Text Search is support in SQL Server Dev Edition and how to implement
it. Have I understood you? Correct me if I was wrong.
Based on my scope, Full-Text Search is supported in SQL Server 2000 Dev
Edition on Windows XP Pro. See more deatiled descritption about this in the
following links
Features Supported by the Editions of SQL Server 2000
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_
ar_ts_1cdv.asp
For the second question, I am not sure your detailed steps on how to
implement the Full-Text Search for the Table, would you please give me more
detail information about doing so? Here is an sample doing this with SQL
Server Enterprise Manager.
1. enable a table for full-text indexing
- Expand Databases, expand the database in which the table belongs, and
then click Tables.
- In the details pane, right-click the table, click Full-Text Index Table,
and then click Define Full-Text Indexing on a Table.
2. To create a full-text catalog
- right-click the database where you want the full-text catalog.
- Click New, and then click New Full-Text Catalog.
- Complete the New Full-Text Catalog dialog box.
3. Make a Full Populating
- expand the database that contains the full-text catalog to rebuild.
- Click Full-Text Catalogs, and then right-click the specific catalog to
populate.
- Click Start Full Population
4. See whether the data had been updated
- right-click the specific catalog to review.
- Click Properties, and then click the Status, Tables, and Schedules tabs,
as appropriate.
See the following chapter in Books Online or MSDN Online for more detailed
information
Creating and Maintaining Databases -> Full-Text Indexes ->
Administering Full-Text Features Using SQL Enterprise Manager
Hope this helps and please feel free to let me know whether it works or you
need furhter help. Thank you for your patience and corporation.
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I reposted the question in news:microsoft.public.sqlserver.programming and
received a reply from Mr. Kane who point dme to a KB that while completely
unrelated showed me where to find the Auditiong options for SQL Server which
I used to pinpoint the real problem. The problem has been resolved.
""Michael Cheng [MSFT]"" wrote:
> Hi,
> Thanks for your post.
> From your descriptions, I understood that you would like to know whether
> Full-Text Search is support in SQL Server Dev Edition and how to implement
> it. Have I understood you? Correct me if I was wrong.
> Based on my scope, Full-Text Search is supported in SQL Server 2000 Dev
> Edition on Windows XP Pro. See more deatiled descritption about this in the
> following links
> Features Supported by the Editions of SQL Server 2000
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_
> ar_ts_1cdv.asp
> For the second question, I am not sure your detailed steps on how to
> implement the Full-Text Search for the Table, would you please give me more
> detail information about doing so? Here is an sample doing this with SQL
> Server Enterprise Manager.
> 1. enable a table for full-text indexing
> - Expand Databases, expand the database in which the table belongs, and
> then click Tables.
> - In the details pane, right-click the table, click Full-Text Index Table,
> and then click Define Full-Text Indexing on a Table.
> 2. To create a full-text catalog
> - right-click the database where you want the full-text catalog.
> - Click New, and then click New Full-Text Catalog.
> - Complete the New Full-Text Catalog dialog box.
> 3. Make a Full Populating
> - expand the database that contains the full-text catalog to rebuild.
> - Click Full-Text Catalogs, and then right-click the specific catalog to
> populate.
> - Click Start Full Population
> 4. See whether the data had been updated
> - right-click the specific catalog to review.
> - Click Properties, and then click the Status, Tables, and Schedules tabs,
> as appropriate.
> See the following chapter in Books Online or MSDN Online for more detailed
> information
> Creating and Maintaining Databases -> Full-Text Indexes ->
> Administering Full-Text Features Using SQL Enterprise Manager
> Hope this helps and please feel free to let me know whether it works or you
> need furhter help. Thank you for your patience and corporation.
>
> Sincerely yours,
> Michael Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Get Secure! - http://www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>|||Hi,
I have noticed that thread, it's great to hear that it was resolved and
thanks for letting me know about that:)
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Full Text Indexing on Microsoft SQL Server 2000 with Windows XP Pro

I am wondering if FUll Text Indexing is suported with MS SQL Server 2000
Developer Edition on XP Pro SP2 . I have the service installed and setup. I
have created several catalogs with data but when they are done populating
they show up with an Item Count of 0 and a Unique Index of 1 despite the
fact that there are 10+ records with extremely different data in the 3
columns that are being indexed.
I am not seeing any unusual messages in the Event Viewer also. I have
uninstalled and reinstalled already and the Server is running under an
Administrator UserHi,
Thanks for your post.
From your descriptions, I understood that you would like to know whether
Full-Text Search is support in SQL Server Dev Edition and how to implement
it. Have I understood you? Correct me if I was wrong.
Based on my scope, Full-Text Search is supported in SQL Server 2000 Dev
Edition on Windows XP Pro. See more deatiled descritption about this in the
following links
Features Supported by the Editions of SQL Server 2000
http://msdn.microsoft.com/library/d...-us/architec/8_
ar_ts_1cdv.asp
For the second question, I am not sure your detailed steps on how to
implement the Full-Text Search for the Table, would you please give me more
detail information about doing so? Here is an sample doing this with SQL
Server Enterprise Manager.
1. enable a table for full-text indexing
- Expand Databases, expand the database in which the table belongs, and
then click Tables.
- In the details pane, right-click the table, click Full-Text Index Table,
and then click Define Full-Text Indexing on a Table.
2. To create a full-text catalog
- right-click the database where you want the full-text catalog.
- Click New, and then click New Full-Text Catalog.
- Complete the New Full-Text Catalog dialog box.
3. Make a Full Populating
- expand the database that contains the full-text catalog to rebuild.
- Click Full-Text Catalogs, and then right-click the specific catalog to
populate.
- Click Start Full Population
4. See whether the data had been updated
- right-click the specific catalog to review.
- Click Properties, and then click the Status, Tables, and Schedules tabs,
as appropriate.
See the following chapter in Books Online or MSDN Online for more detailed
information
Creating and Maintaining Databases -> Full-Text Indexes ->
Administering Full-Text Features Using SQL Enterprise Manager
Hope this helps and please feel free to let me know whether it works or you
need furhter help. Thank you for your patience and corporation.
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

full text indexing

is there a way to enable full text indexing on SQL Server 2005 Express?

i know that the advanced edition can do so, but i am wondering if there is a registry hack or something that i can use instead of reinstalling.

any ideas?

thanks

No. SQL Express 2005 is missing several full-text files and a service. There is no quick hack to get it to work. The best way is to save your databases and simply upgrade.|||yes, you needs the SQL Server 2005 Express Edition with Advanced Services from 12.04.2006, it contains the service for the full-text search.

Full text 4Gb memory

I have a server run std edition 2000 with FTS. The server has 4Gb of memory
is there any benefit in setting the 3Gb switch?
The /3GB switch refers to the Virtual Address Space for any process, not
just SQL Server. Whether or not that space is backed by physical ram is
dependent on the configuration of the server and other applications running
at any particular time. Let's say you have 2 GB of ram and a 4 GB swap
file. Then, it is possible for an application to have, say 1 GB of physical
ram for kernel mode processing, 1 GB of physical ram for a portion of the
user mode processing, then the application could use of to 2 GB of swap
space. The allocation of that swap space would be dependent on the /3GB
switch being enabled or not.
The same goes for physical ram. If you have 4 GB, then it is possible that
one application could be allocated 1 GB for kernel mode, and 3 GB for user
mode. The problem is that this is not the only application on the server.
If anything, the OS has to be running, mostly from critical sections of
physical ram.
Now, SQL Server 2K Standard Edition will only allocate a MAXIMUM of 2 GB for
the Buffer Pool. As SS2K SE is an application, it could use 1 GB to 2 GB
for the kernel mode requests, but the Buffer Pool is not the ONLY space SS
uses. So, by using the /3GB switch, you could dedicate a 2 GB Buffer Pool
and still allow up to 1 GB for kernel mode requests and 1 GB for MEM TO
LEAVE sections of memory, all backed by physical ram. To the extent that
other applications and the OS itself requires physical ram, you could still
maintain a 2 GB Buffer Pool backed by physical ram and allow the kernel mode
and MEM TO LEAVE regions to be swapped out to the page file.
So, yes, there could be benefits to using the /3GB switch.
However, you never said what OS version you were running on. Neither Win2K
SE nor Win2K3 SE support the /3GB boot.ini parameter. You have to be
running Win2K AS or Win2K3 EE or either of the Data Center Editions.
Sincerely,
Anthony Thomas

"Simon" <Simon@.cmg.noemail> wrote in message
news:07DDD724-0C42-4748-A82F-5C41DE2AD5D4@.microsoft.com...
I have a server run std edition 2000 with FTS. The server has 4Gb of memory
is there any benefit in setting the 3Gb switch?

Full text 4Gb memory

I have a server run std edition 2000 with FTS. The server has 4Gb of memory
is there any benefit in setting the 3Gb switch?The /3GB switch refers to the Virtual Address Space for any process, not
just SQL Server. Whether or not that space is backed by physical ram is
dependent on the configuration of the server and other applications running
at any particular time. Let's say you have 2 GB of ram and a 4 GB swap
file. Then, it is possible for an application to have, say 1 GB of physical
ram for kernel mode processing, 1 GB of physical ram for a portion of the
user mode processing, then the application could use of to 2 GB of swap
space. The allocation of that swap space would be dependent on the /3GB
switch being enabled or not.
The same goes for physical ram. If you have 4 GB, then it is possible that
one application could be allocated 1 GB for kernel mode, and 3 GB for user
mode. The problem is that this is not the only application on the server.
If anything, the OS has to be running, mostly from critical sections of
physical ram.
Now, SQL Server 2K Standard Edition will only allocate a MAXIMUM of 2 GB for
the Buffer Pool. As SS2K SE is an application, it could use 1 GB to 2 GB
for the kernel mode requests, but the Buffer Pool is not the ONLY space SS
uses. So, by using the /3GB switch, you could dedicate a 2 GB Buffer Pool
and still allow up to 1 GB for kernel mode requests and 1 GB for MEM TO
LEAVE sections of memory, all backed by physical ram. To the extent that
other applications and the OS itself requires physical ram, you could still
maintain a 2 GB Buffer Pool backed by physical ram and allow the kernel mode
and MEM TO LEAVE regions to be swapped out to the page file.
So, yes, there could be benefits to using the /3GB switch.
However, you never said what OS version you were running on. Neither Win2K
SE nor Win2K3 SE support the /3GB boot.ini parameter. You have to be
running Win2K AS or Win2K3 EE or either of the Data Center Editions.
Sincerely,
Anthony Thomas
"Simon" <Simon@.cmg.noemail> wrote in message
news:07DDD724-0C42-4748-A82F-5C41DE2AD5D4@.microsoft.com...
I have a server run std edition 2000 with FTS. The server has 4Gb of memory
is there any benefit in setting the 3Gb switch?

Full text 4Gb memory

I have a server run std edition 2000 with FTS. The server has 4Gb of memory
is there any benefit in setting the 3Gb switch?The /3GB switch refers to the Virtual Address Space for any process, not
just SQL Server. Whether or not that space is backed by physical ram is
dependent on the configuration of the server and other applications running
at any particular time. Let's say you have 2 GB of ram and a 4 GB swap
file. Then, it is possible for an application to have, say 1 GB of physical
ram for kernel mode processing, 1 GB of physical ram for a portion of the
user mode processing, then the application could use of to 2 GB of swap
space. The allocation of that swap space would be dependent on the /3GB
switch being enabled or not.
The same goes for physical ram. If you have 4 GB, then it is possible that
one application could be allocated 1 GB for kernel mode, and 3 GB for user
mode. The problem is that this is not the only application on the server.
If anything, the OS has to be running, mostly from critical sections of
physical ram.
Now, SQL Server 2K Standard Edition will only allocate a MAXIMUM of 2 GB for
the Buffer Pool. As SS2K SE is an application, it could use 1 GB to 2 GB
for the kernel mode requests, but the Buffer Pool is not the ONLY space SS
uses. So, by using the /3GB switch, you could dedicate a 2 GB Buffer Pool
and still allow up to 1 GB for kernel mode requests and 1 GB for MEM TO
LEAVE sections of memory, all backed by physical ram. To the extent that
other applications and the OS itself requires physical ram, you could still
maintain a 2 GB Buffer Pool backed by physical ram and allow the kernel mode
and MEM TO LEAVE regions to be swapped out to the page file.
So, yes, there could be benefits to using the /3GB switch.
However, you never said what OS version you were running on. Neither Win2K
SE nor Win2K3 SE support the /3GB boot.ini parameter. You have to be
running Win2K AS or Win2K3 EE or either of the Data Center Editions.
Sincerely,
Anthony Thomas
"Simon" <Simon@.cmg.noemail> wrote in message
news:07DDD724-0C42-4748-A82F-5C41DE2AD5D4@.microsoft.com...
I have a server run std edition 2000 with FTS. The server has 4Gb of memory
is there any benefit in setting the 3Gb switch?

Full population very slow

I've got SQL2000 Enterprise edition running on windows 2000 advanced server,
we've recently upgraded from SQL sp2 to sp3a, this caused a catalog rebuild
but full population is taking forever. The column with Full text search
enabled is of image type, there are 2.5 million record in the table, about
7GB in size.
I've started full population 2 days ago and it's still showing "Population
in progress", when I view the property page of the catalog, I can see ~
2300000 items, catalog size: 190MB, unique key count: 362586. It appears to
be processing 1000 items per minute.
The server has 8 CPUs, 8GB RAM with /PAE and /3GB enabled, heavy duty SAN
disks.
mssdmn.exe is the most active process, it's using between 30-40 CPU on one
processor only, disk utilization is minimal and plenty of physical memory
available for use. This process is using 6 threads, 10MB RAM, mssearch.exe is
using 50MB RAM and 16 threads.
Is there any way of speeding up population?
Thanks,
Ad
set sp_fulltext_service 'resource_usage', 5
"Ad" <Ad@.discussions.microsoft.com> wrote in message
news:B94E0F3A-7655-4D8A-8605-EA1BC43E6329@.microsoft.com...
> I've got SQL2000 Enterprise edition running on windows 2000 advanced
> server,
> we've recently upgraded from SQL sp2 to sp3a, this caused a catalog
> rebuild
> but full population is taking forever. The column with Full text search
> enabled is of image type, there are 2.5 million record in the table, about
> 7GB in size.
> I've started full population 2 days ago and it's still showing "Population
> in progress", when I view the property page of the catalog, I can see ~
> 2300000 items, catalog size: 190MB, unique key count: 362586. It appears
> to
> be processing 1000 items per minute.
> The server has 8 CPUs, 8GB RAM with /PAE and /3GB enabled, heavy duty SAN
> disks.
> mssdmn.exe is the most active process, it's using between 30-40 CPU on one
> processor only, disk utilization is minimal and plenty of physical memory
> available for use. This process is using 6 threads, 10MB RAM, mssearch.exe
> is
> using 50MB RAM and 16 threads.
> Is there any way of speeding up population?
> Thanks,
> Ad
>
|||Ad,
There are a couple of thing you can do to improve the FT Indexing
performance without stopping & re-locating the FT Catalog. You can set the
MSSearch service's to use one CPU and then use sp_configure to set the
affinity of SQL Server to that cpu to avoid cpu contention during heavy
MSSearch CPU usage via the following method - launch the Tskmgr.exe from the
AT command on the multi-proc server where sql server resides, as follows:
at <current_time+1min> /interactive taskmgr.exe
when it launches, you can then set "cpu affinity" for the MSSearch service
to a cpu or set of cpu's not being used by SQL Server. Then you would use
sp_configure to set SQL Server's cpu affinity to the other cpu's, thus
preventing the cpu usage of mssearch from affecting your sql server
processing. Note, this only works on multi-processor servers and is a
secured method for achieving this feature.
Additionally, as your 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.
Finally, I'd highly recommend that you review all the resources "SQL Server
2000 Full-Text Search Resources and Links" at:
http://spaces.msn.com/members/jtkane/Blog/cns!1pWDBCiDX1uvH5ATJmNCVLPQ!305.entry
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Ad" <Ad@.discussions.microsoft.com> wrote in message
news:B94E0F3A-7655-4D8A-8605-EA1BC43E6329@.microsoft.com...
> I've got SQL2000 Enterprise edition running on windows 2000 advanced
server,
> we've recently upgraded from SQL sp2 to sp3a, this caused a catalog
rebuild
> but full population is taking forever. The column with Full text search
> enabled is of image type, there are 2.5 million record in the table, about
> 7GB in size.
> I've started full population 2 days ago and it's still showing
"Population
> in progress", when I view the property page of the catalog, I can see ~
> 2300000 items, catalog size: 190MB, unique key count: 362586. It appears
to
> be processing 1000 items per minute.
> The server has 8 CPUs, 8GB RAM with /PAE and /3GB enabled, heavy duty SAN
> disks.
> mssdmn.exe is the most active process, it's using between 30-40 CPU on one
> processor only, disk utilization is minimal and plenty of physical memory
> available for use. This process is using 6 threads, 10MB RAM, mssearch.exe
is
> using 50MB RAM and 16 threads.
> Is there any way of speeding up population?
> Thanks,
> Ad
>
|||sp_fulltext_service 'resource_usage', 5 , did not make any difference, does
it need stop and re-start of MSSearch service?
Thanks,
Ad
|||Ad,
I didn't think it would make much difference. However, where you get the
biggest bang for your buck, is ensuring that the FT Catalog is on a separate
disk drive from your database files. Can you stop the Full Population, drop
and re-create the FT Catalog on separate disk array or better yet, on a
separate disk controller? See SQL 2000 BOL title "Full-text Search
Recommendations" for more info on this.
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Ad" <Ad@.discussions.microsoft.com> wrote in message
news:B72E38AF-4FFF-4F60-9F84-BF56213AC220@.microsoft.com...
> sp_fulltext_service 'resource_usage', 5 , did not make any difference,
does
> it need stop and re-start of MSSearch service?
> Thanks,
> Ad
>
>
|||The FT Catalog is on a dedicated SAN disk which is almost idle, in fact the
whole disk is cached. So there are plenty of resources on the server that FT
can't utilize, this leads me to believe FT has scalability issues.
Regards,
Ad
"John Kane" wrote:

> Ad,
> I didn't think it would make much difference. However, where you get the
> biggest bang for your buck, is ensuring that the FT Catalog is on a separate
> disk drive from your database files. Can you stop the Full Population, drop
> and re-create the FT Catalog on separate disk array or better yet, on a
> separate disk controller? See SQL 2000 BOL title "Full-text Search
> Recommendations" for more info on this.
> Regards,
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
> "Ad" <Ad@.discussions.microsoft.com> wrote in message
> news:B72E38AF-4FFF-4F60-9F84-BF56213AC220@.microsoft.com...
> does
>
>

fts SQL Server Personal on XP Pro

Hi,
I have SQL Server 2000 Personal edition installed on XP
Pro and am trying to implement the full-text search
facility. There doesn't seem to be any option to install
fts on my SQL Server CD so I assumed it should be
installed by default.
However, when I try
EXEC sp_fulltext_database @.action = 'Enable'
I get the following error
erver: Msg 7609, Level 17, State 2, Procedure
sp_fulltext_database, Line 46
Full-Text Search is not installed, or a full-text
component cannot be loaded.
Is FTS possible with this version of SQLServer?
thanks
Maracatu
maracatu,
No, the SQL Server 2000 "Full-Text Search" components are not supported with
the Personal Edition. See SQL 2000 BOL title "Features Supported by the
Editions of SQL Server 2000" for editions that support SQL FTS.
Regards,
John
"maracatu" <jarrod@.dovelight.com> wrote in message
news:1ccfa01c42241$c5b48fe0$a101280a@.phx.gbl...
> Hi,
> I have SQL Server 2000 Personal edition installed on XP
> Pro and am trying to implement the full-text search
> facility. There doesn't seem to be any option to install
> fts on my SQL Server CD so I assumed it should be
> installed by default.
> However, when I try
> EXEC sp_fulltext_database @.action = 'Enable'
> I get the following error
> erver: Msg 7609, Level 17, State 2, Procedure
> sp_fulltext_database, Line 46
> Full-Text Search is not installed, or a full-text
> component cannot be loaded.
> Is FTS possible with this version of SQLServer?
> thanks
> Maracatu
|||Hmmmm.... This article on MSDN says that Full Text IS supported on Personal Edition...
http://msdn.microsoft.com/library/de...ar_ts_1cdv.asp
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
|||SqlJunkies User,
Hmmm is right... Actually we both referenced the same doc (your MSDN
reference is the same info that is in the SQL BOL reference I quoted...
However, the initial poster may need to specifically install the SQL FTS
components via the SQL CD's "custom installation" and select the "Full-text
Search" components in order to install it. I've not tested this myself as I
don't use the Personal Edition of SQL Server on WinXP as I use the Developer
Edition. If you have the Personal Edition, perhaps you could test this
yourself and post the results here... ;-)
Regards,
John
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:#W##QXpREHA.1276@.TK2MSFTNGP11.phx.gbl...
> Hmmmm.... This article on MSDN says that Full Text IS supported on
Personal Edition...
>
http://msdn.microsoft.com/library/de...ar_ts_1cdv.asp
>
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.
|||I had the exact same problem. I found and posted the article mentioned in the last post. I then found article Q827449 that tells how to reinstall Full Text by running some stuff on the SQL CD. I followed all the instructions, but didn't seem to make it
work. Something still missing. Then, when running the Setup for SQL 2000 Personal Edition again (Not uninstalling my first one), and choosing a Custom Install to Add/Remove components, the option for Full Text was already checked. It would not let me
uncheck it (Setup didn't recognize that I had changed anything and wouldn't continue). Finally, had to uninstall, whack all SQL related registry keys, and reinstall. On the reinstall, chose Custom Install. Full Text is NOT checked by default. Checked
it, and finished the install. Full Text is now available and usable on my SQL 2000 Personal Edition on XP Professional. If you haven't "damaged" you SQL install by following Q827449, you might be able to add it by running Setup again and choosing Custo
m Install to Add/Remove Components...
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
|||Hi,
In order to un-check the option for Full Text Search that was already
checked, you must delete or rename the following Tracking Key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\<Instance_Name>\Tracking\
{E07FDDA7-5A21-11d2-9DAD-00C04F79D434}
Note, if your SQL Server 2000 is not a named instance, remove
"<Instance_Name>\" and be sure to be logged on to the server as either
Administrator or as a member of the server's Admin Group.
Once you've done removed (renamed) the above tracking key, then delete the
MSSearch directory from either:
drive_letter:\Program Files\Common Files\Microsoft Shared\
or
drive_letter::\Program Files\Common Files\System\
Then using your SQL Server 2000 installation CD re-install via "Custom
Installation" the Full-Text Search component (it should be un-checked). When
this completes find and save these files: SearchSetup.log (usually under
\windows or \winnt folders) and sqlsp.log. If any problems, you should post
these files.
I'm not sure why the procedures in Q827449 failed for you, but if you follow
the above procedures, it will always work as I've posted the above methods
many, many times in this newsgroup (microsoft.public.sqlserver.fulltext) and
always with successful results.
Regards,
John
<CSaalfeld@.-NOSPAM-Earthlink.net> wrote in message
news:OEdOfICSEHA.3052@.TK2MSFTNGP12.phx.gbl...
> I had the exact same problem. I found and posted the article mentioned in
the last post. I then found article Q827449 that tells how to reinstall
Full Text by running some stuff on the SQL CD. I followed all the
instructions, but didn't seem to make it work. Something still missing.
Then, when running the Setup for SQL 2000 Personal Edition again (Not
uninstalling my first one), and choosing a Custom Install to Add/Remove
components, the option for Full Text was already checked. It would not let
me uncheck it (Setup didn't recognize that I had changed anything and
wouldn't continue). Finally, had to uninstall, whack all SQL related
registry keys, and reinstall. On the reinstall, chose Custom Install. Full
Text is NOT checked by default. Checked it, and finished the install. Full
Text is now available and usable on my SQL 2000 Personal Edition on XP
Professional. If you haven't "damaged" you SQL install by following
Q827449, you might be able to add it by running Setup again and choosing
Custom Install to Add/Remove Components...
>
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.

FTS Over SQL Personal Edition

I have several instances of SQL Server 2000 Personal Edition running on 2000
Pro and XP Pro.
Are there any issues with installing Full-Text Search on these machines?
Thanks
hi ray!
"Binder" <rgondzur@.NO_SPAM_aicsoft.com> wrote in message
news:%23k4Erl4XEHA.3044@.TK2MSFTNGP09.phx.gbl...
> I have several instances of SQL Server 2000 Personal Edition running on
2000
> Pro and XP Pro.
> Are there any issues with installing Full-Text Search on these machines?
> Thanks
>
|||Binder,
If you review SQL 2000 BOL title "Features Supported by the Editions of SQL
Server 2000", it states that for the Personal Edition that Full-Text Search
is "Supported (except on Windows 98)". However, and while I've not tested
this with the Personal Edition (as I have with the Developer Edition), to
install FTS you must select "custom installation" from your SQL CD and under
the Server components, select the "Full-text Search" components and it
*should* install SQL FTS. No, to the best of my knowledge, there should not
be any installation issue with installing Full-Text Search on those
machines. However, I'd recommend that you be logged on as either Admin or as
a member of the Admin Group when you do the custom installation.
Regards,
John
"Binder" <rgondzur@.NO_SPAM_aicsoft.com> wrote in message
news:#k4Erl4XEHA.3044@.TK2MSFTNGP09.phx.gbl...
> I have several instances of SQL Server 2000 Personal Edition running on
2000
> Pro and XP Pro.
> Are there any issues with installing Full-Text Search on these machines?
> Thanks
>