显示标签为“indexing”的博文。显示所有博文
显示标签为“indexing”的博文。显示所有博文

2012年3月29日星期四

Full Text Setup

I'm trying to set up Full-text indexing. I installed the module, the
service shows up in control panel\services, but the option in EM is still
grayed out. Any suggestions?
FYI: SQL2000 on XP pro, rebooted machine...
thanks. -Rob T.http://www.indexserverfaq.com/tablenotenabled.htm
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Rob T" <RTorcellini@.DONTwalchemSPAM.com> wrote in message
news:%23vgfkinWGHA.4960@.TK2MSFTNGP05.phx.gbl...
> I'm trying to set up Full-text indexing. I installed the module, the
> service shows up in control panel\services, but the option in EM is still
> grayed out. Any suggestions?
> FYI: SQL2000 on XP pro, rebooted machine...
> thanks. -Rob T.
>|||I've also found that if this is a remote server then the options can be
disabled, I think this is because EM can't determine if FTS is installed. I
guess its a remote permissions thing. If you log on locally you should find
it enabled
Simon Sabin
SQL Server MVP
http://sqljunkies.com/weblog/simons
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23I7E5LqWGHA.3972@.TK2MSFTNGP02.phx.gbl...
> http://www.indexserverfaq.com/tablenotenabled.htm
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Rob T" <RTorcellini@.DONTwalchemSPAM.com> wrote in message
> news:%23vgfkinWGHA.4960@.TK2MSFTNGP05.phx.gbl...
>|||Not always, it seems to be a bug somewhere along the line. You can always
use the wizard from the command line to access remote SQL Servers when you
run into this problem. C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\sqlftwiz.exe /sRemoteServerName /n for trusted, or
/sRemoteServerName /usa /ppassword
You still need to be in the symin role on the server you are trying to
manage.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Simon Sabin" <ContactThroughMyBlog@.nospam.com> wrote in message
news:4438c2ac$1$33888$ed2619ec@.ptn-nntp-reader03.plus.net...
> I've also found that if this is a remote server then the options can be
> disabled, I think this is because EM can't determine if FTS is installed.
> I guess its a remote permissions thing. If you log on locally you should
> find it enabled
> --
> Simon Sabin
> SQL Server MVP
> http://sqljunkies.com/weblog/simons
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%23I7E5LqWGHA.3972@.TK2MSFTNGP02.phx.gbl...
>|||How do I know if I am in the symin role ?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OCe2ek8WGHA.3848@.TK2MSFTNGP05.phx.gbl...
> Not always, it seems to be a bug somewhere along the line. You can always
> use the wizard from the command line to access remote SQL Servers when you
> run into this problem. C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\sqlftwiz.exe /sRemoteServerName /n for trusted, or
> /sRemoteServerName /usa /ppassword
> You still need to be in the symin role on the server you are trying to
> manage.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Simon Sabin" <ContactThroughMyBlog@.nospam.com> wrote in message
> news:4438c2ac$1$33888$ed2619ec@.ptn-nntp-reader03.plus.net...
installed.
intelligence.
RelevantNoise's
>|||SELECT IS_SRVROLEMEMBER('symin')
*mike hodgson*
http://sqlnerd.blogspot.com
Alan wrote:

>How do I know if I am in the symin role ?
>"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
>news:OCe2ek8WGHA.3848@.TK2MSFTNGP05.phx.gbl...
>
>installed.
>
>intelligence.
>
>RelevantNoise's
>
>
>|||I tried and result is 1.|||It's documented in Books Online:
http://msdn.microsoft.com/library/e..._ia-iz_4f5e.asp
1 means the login is a member of the role.
0 means the login is not a member of the role.
*mike hodgson*
http://sqlnerd.blogspot.com
Alan wrote:

> I tried and result is 1.|||Hi Mike,
So that means my login has admin permission, right?
Do you have any idea why I cannot do a full-text search ?
"Mike Hodgson" <e1minst3r@.gmail.com> wrote in message news:OuKuWsUeGHA.1208@.
TK2MSFTNGP02.phx.gbl...
It's documented in Books Online:
http://msdn.microsoft.com/library/e..._ia-iz_4f5e.asp
1 means the login is a member of the role.
0 means the login is not a member of the role.
mike hodgson
http://sqlnerd.blogspot.com
Alan wrote:
I tried and result is 1.|||Alan wrote:

> So that means my login has admin permission, right?
Within the context of that SQL instance, yes.

> Do you have any idea why I cannot do a full-text search ?
No, sorry - I haven't been following the thread so I don't know what
problem you're experiencing exactly (I just saw your question about how
to determine if a login is a symin or not). But I'm not much of a
FTS expert anyway (I generally try to avoid FTS, initially (back in the
old days) because I found it to be a bit of a kludge, ie. being an
external service rather than core to the DB engine). Hilary & Simon
would be much better qualified to talk about FTS than I.

> "Mike Hodgson" <e1minst3r@.gmail.com <mailto:e1minst3r@.gmail.com>>
> wrote in message news:OuKuWsUeGHA.1208@.TK2MSFTNGP02.phx.gbl...
> It's documented in Books Online:
> http://msdn.microsoft.com/library/e..._ia-iz_4f5e.asp
> 1 means the login is a member of the role.
> 0 means the login is not a member of the role.
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> Alan wrote:
>
>
--
*mike hodgson*
http://sqlnerd.blogspot.comsql

full text searching BLOBS

Hi all,
I have an issue with full text indexing of some BLOB data (image data
type). We recently moved a SQL 2000 database to a new server with SQL
2005 installed. Everything thing went very smooth. We have full text
indexing enabled on several columns over several tables. We have a
table for attachments that are stored as BLOBs that is also indexed.
Since the migration, all of the full text searches work as before with
the exception of the binary data. We used to be able to search inside
Word, Excel, and other office documents. Now we cannot.
I believe I have located the source of the problem, but I am not sure
how to resolve. Anyone who has used this feature knows that when you
index a BLOB (image data type) you have to select a second column that
tells SQL what filetype is being stored. My column for this is called
ATTACHMENT_CONTENTTYPE. SQL compares this with a list of iFilters it
has to determine which filter it should use when searching the binary
data for text.
Here is an example of what is contained in my ATTACHMENT_CONTENTTYPE
column:
image/tiff
application/x-zip-compressed
text/richtext
image/bmp
audio/wav
application/msword
video/mpeg
video/avi
image/x-bmp
image/vnd.ms-modi
image/gif
video/mpg
application/octet-stream
application/vnd.ms-excel
All of the sql documentation I am reading is telling me that my column
should contain file extensions like:
..doc
..xls
..ppt
Here is my dilemma. This all worked perfectly with SQL 2000. It is a
big deal for me to change all of the data in this column as well as
the application that populates it. Am I not understanding how this
works, or is there some way I can get SQL 2005 to recognize the way my
column is describing the data type?
Thank you!
On Mar 12, 11:25Xam, markman...@.gmail.com wrote:
> Hi all,
> I have an issue with full text indexing of someBLOBdata (image data
> type). We recently moved aSQL2000 database to a new server withSQL2005installed. Everything thing went very smooth. We have full text
> indexing enabled on several columns over several tables. We have a
> table for attachments that are stored as BLOBs that is also indexed.
> Since the migration, all of the full text searches work as before with
> the exception of the binary data. We used to be able to search inside
> Word, Excel, and other office documents. Now we cannot.
> I believe I have located the source of the problem, but I am not sure
> how to resolve. Anyone who has used this feature knows that when you
> index aBLOB(image data type) you have to select a second column that
> tellsSQLwhat filetype is being stored. My column for this is called
> ATTACHMENT_CONTENTTYPE.SQLcompares this with a list of iFilters it
> has to determine which filter it should use when searching the binary
> data for text.
> Here is an example of what is contained in my ATTACHMENT_CONTENTTYPE
> column:
> image/tiff
> application/x-zip-compressed
> text/richtext
> image/bmp
> audio/wav
> application/msword
> video/mpeg
> video/avi
> image/x-bmp
> image/vnd.ms-modi
> image/gif
> video/mpg
> application/octet-stream
> application/vnd.ms-excel
> All of thesqldocumentation I am reading is telling me that my column
> should contain file extensions like:
> .doc
> .xls
> .ppt
> Here is my dilemma. This all worked perfectly withSQL2000. It is a
> big deal for me to change all of the data in this column as well as
> the application that populates it. Am I not understanding how this
> works, or is there some way I can getSQL2005to recognize the way my
> column is describing the data type?
> Thank you!
Also, I have no errors in the log files that I can see. Thanks all.

full text searching BLOBS

Hi all,
I have an issue with full text indexing of some BLOB data (image data
type). We recently moved a SQL 2000 database to a new server with SQL
2005 installed. Everything thing went very smooth. We have full text
indexing enabled on several columns over several tables. We have a
table for attachments that are stored as BLOBs that is also indexed.
Since the migration, all of the full text searches work as before with
the exception of the binary data. We used to be able to search inside
Word, Excel, and other office documents. Now we cannot.
I believe I have located the source of the problem, but I am not sure
how to resolve. Anyone who has used this feature knows that when you
index a BLOB (image data type) you have to select a second column that
tells SQL what filetype is being stored. My column for this is called
ATTACHMENT_CONTENTTYPE. SQL compares this with a list of iFilters it
has to determine which filter it should use when searching the binary
data for text.
Here is an example of what is contained in my ATTACHMENT_CONTENTTYPE
column:
image/tiff
application/x-zip-compressed
text/richtext
image/bmp
audio/wav
application/msword
video/mpeg
video/avi
image/x-bmp
image/vnd.ms-modi
image/gif
video/mpg
application/octet-stream
application/vnd.ms-excel
All of the sql documentation I am reading is telling me that my column
should contain file extensions like:
.doc
.xls
.ppt
Here is my dilemma. This all worked perfectly with SQL 2000. It is a
big deal for me to change all of the data in this column as well as
the application that populates it. Am I not understanding how this
works, or is there some way I can get SQL 2005 to recognize the way my
column is describing the data type?
Thank you!On Mar 12, 11:25=A0am, markman...@.gmail.com wrote:
> Hi all,
> I have an issue with full text indexing of someBLOBdata (image data
> type). We recently moved aSQL2000 database to a new server withSQL2005inst=alled. Everything thing went very smooth. We have full text
> indexing enabled on several columns over several tables. We have a
> table for attachments that are stored as BLOBs that is also indexed.
> Since the migration, all of the full text searches work as before with
> the exception of the binary data. We used to be able to search inside
> Word, Excel, and other office documents. Now we cannot.
> I believe I have located the source of the problem, but I am not sure
> how to resolve. Anyone who has used this feature knows that when you
> index aBLOB(image data type) you have to select a second column that
> tellsSQLwhat filetype is being stored. My column for this is called
> ATTACHMENT_CONTENTTYPE.SQLcompares this with a list of iFilters it
> has to determine which filter it should use when searching the binary
> data for text.
> Here is an example of what is contained in my ATTACHMENT_CONTENTTYPE
> column:
> image/tiff
> application/x-zip-compressed
> text/richtext
> image/bmp
> audio/wav
> application/msword
> video/mpeg
> video/avi
> image/x-bmp
> image/vnd.ms-modi
> image/gif
> video/mpg
> application/octet-stream
> application/vnd.ms-excel
> All of thesqldocumentation I am reading is telling me that my column
> should contain file extensions like:
> .doc
> .xls
> .ppt
> Here is my dilemma. This all worked perfectly withSQL2000. It is a
> big deal for me to change all of the data in this column as well as
> the application that populates it. Am I not understanding how this
> works, or is there some way I can getSQL2005to recognize the way my
> column is describing the data type?
> Thank you!
Also, I have no errors in the log files that I can see. Thanks all.

2012年3月27日星期二

Full Text Searching

I want to use full text indexing. I have read you need to leave 50MB spare
on the server. Is this per index,database or instance of SQL Server and does
it increase with the size of the table or is just a static amount virtual
memory to be put aside. Regards.Where did you read? Could you show us a link? Is that RAM or hard disk
space?
Full-Text search service, indexes the data in your tables, in its own index
files outside SQL Server. So, the bigger your tables, the bigger the full
text catalog file size.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Chris Kennedy" <nospam@.microsoft.com> wrote in message
news:uzfFfzq3DHA.2888@.tk2msftngp13.phx.gbl...
I want to use full text indexing. I have read you need to leave 50MB spare
on the server. Is this per index,database or instance of SQL Server and does
it increase with the size of the table or is just a static amount virtual
memory to be put aside. Regards.|||I read it in Inside SQL Server. I may have got it wrong. I read 5O MB plus
about 30% of the table size.
"Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
news:#FAAcBs3DHA.484@.TK2MSFTNGP10.phx.gbl...
| Where did you read? Could you show us a link? Is that RAM or hard disk
| space?
|
| Full-Text search service, indexes the data in your tables, in its own
index
| files outside SQL Server. So, the bigger your tables, the bigger the full
| text catalog file size.
| --
| HTH,
| Vyas, MVP (SQL Server)
| http://vyaskn.tripod.com/
| Is .NET important for a database professional?
| http://vyaskn.tripod.com/poll.htm
|
|
|
|
| "Chris Kennedy" <nospam@.microsoft.com> wrote in message
| news:uzfFfzq3DHA.2888@.tk2msftngp13.phx.gbl...
| I want to use full text indexing. I have read you need to leave 50MB spare
| on the server. Is this per index,database or instance of SQL Server and
does
| it increase with the size of the table or is just a static amount virtual
| memory to be put aside. Regards.
|
|
|
||||Chris, you are referencing Kalen's "Inside SQL Server 2000" book on page583
as she states that at least 50MB of hard drive space must be available to
create a FT Catalog on the disk drive. I don't have disk small enough to
test this <g>, but if you are FT Indexing via the FT Wizard and placing the
FT Catalog on a disk drive of less that 50MB, you will get an error.
Although, I found no reference to 30% of anything. Could you clarify more
what your concerns are?
Note, you can also post FTS related questions to the newsgroup:
microsoft.public.sqlserver.fulltext
Regards,
John
"Chris Kennedy" <nospam@.microsoft.com> wrote in message
news:#$7LI#33DHA.2544@.TK2MSFTNGP10.phx.gbl...
quote:

> I read it in Inside SQL Server. I may have got it wrong. I read 5O MB plus
> about 30% of the table size.
> "Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
> news:#FAAcBs3DHA.484@.TK2MSFTNGP10.phx.gbl...
> | Where did you read? Could you show us a link? Is that RAM or hard disk
> | space?
> |
> | Full-Text search service, indexes the data in your tables, in its own
> index
> | files outside SQL Server. So, the bigger your tables, the bigger the

full
quote:

> | text catalog file size.
> | --
> | HTH,
> | Vyas, MVP (SQL Server)
> | http://vyaskn.tripod.com/
> | Is .NET important for a database professional?
> | http://vyaskn.tripod.com/poll.htm
> |
> |
> |
> |
> | "Chris Kennedy" <nospam@.microsoft.com> wrote in message
> | news:uzfFfzq3DHA.2888@.tk2msftngp13.phx.gbl...
> | I want to use full text indexing. I have read you need to leave 50MB

spare
quote:

> | on the server. Is this per index,database or instance of SQL Server and
> does
> | it increase with the size of the table or is just a static amount

virtual
quote:

> | memory to be put aside. Regards.
> |
> |
> |
> |
>
|||What amount of space will a full text index take in e. g. a 10 MB table.
"John Kane" <jt-kane@.comcast.net> wrote in message
news:OBnfOx53DHA.2460@.TK2MSFTNGP10.phx.gbl...
| Chris, you are referencing Kalen's "Inside SQL Server 2000" book on
page583
| as she states that at least 50MB of hard drive space must be available to
| create a FT Catalog on the disk drive. I don't have disk small enough to
| test this <g>, but if you are FT Indexing via the FT Wizard and placing
the
| FT Catalog on a disk drive of less that 50MB, you will get an error.
| Although, I found no reference to 30% of anything. Could you clarify more
| what your concerns are?
|
| Note, you can also post FTS related questions to the newsgroup:
| microsoft.public.sqlserver.fulltext
| Regards,
| John
|
|
|
| "Chris Kennedy" <nospam@.microsoft.com> wrote in message
| news:#$7LI#33DHA.2544@.TK2MSFTNGP10.phx.gbl...
| > I read it in Inside SQL Server. I may have got it wrong. I read 5O MB
plus
| > about 30% of the table size.
| >
| > "Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
| > news:#FAAcBs3DHA.484@.TK2MSFTNGP10.phx.gbl...
| > | Where did you read? Could you show us a link? Is that RAM or hard disk
| > | space?
| > |
| > | Full-Text search service, indexes the data in your tables, in its own
| > index
| > | files outside SQL Server. So, the bigger your tables, the bigger the
| full
| > | text catalog file size.
| > | --
| > | HTH,
| > | Vyas, MVP (SQL Server)
| > | http://vyaskn.tripod.com/
| > | Is .NET important for a database professional?
| > | http://vyaskn.tripod.com/poll.htm
| > |
| > |
| > |
| > |
| > | "Chris Kennedy" <nospam@.microsoft.com> wrote in message
| > | news:uzfFfzq3DHA.2888@.tk2msftngp13.phx.gbl...
| > | I want to use full text indexing. I have read you need to leave 50MB
| spare
| > | on the server. Is this per index,database or instance of SQL Server
and
| > does
| > | it increase with the size of the table or is just a static amount
| virtual
| > | memory to be put aside. Regards.
| > |
| > |
| > |
| > |
| >
| >
|
|

Full Text Searching

I want to use full text indexing. I have read you need to leave 50MB spare
on the server. Is this per index,database or instance of SQL Server and does
it increase with the size of the table or is just a static amount virtual
memory to be put aside. Regards.Where did you read? Could you show us a link? Is that RAM or hard disk
space?
Full-Text search service, indexes the data in your tables, in its own index
files outside SQL Server. So, the bigger your tables, the bigger the full
text catalog file size.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Chris Kennedy" <nospam@.microsoft.com> wrote in message
news:uzfFfzq3DHA.2888@.tk2msftngp13.phx.gbl...
I want to use full text indexing. I have read you need to leave 50MB spare
on the server. Is this per index,database or instance of SQL Server and does
it increase with the size of the table or is just a static amount virtual
memory to be put aside. Regards.|||I read it in Inside SQL Server. I may have got it wrong. I read 5O MB plus
about 30% of the table size.
"Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
news:#FAAcBs3DHA.484@.TK2MSFTNGP10.phx.gbl...
| Where did you read? Could you show us a link? Is that RAM or hard disk
| space?
|
| Full-Text search service, indexes the data in your tables, in its own
index
| files outside SQL Server. So, the bigger your tables, the bigger the full
| text catalog file size.
| --
| HTH,
| Vyas, MVP (SQL Server)
| http://vyaskn.tripod.com/
| Is .NET important for a database professional?
| http://vyaskn.tripod.com/poll.htm
|
|
|
|
| "Chris Kennedy" <nospam@.microsoft.com> wrote in message
| news:uzfFfzq3DHA.2888@.tk2msftngp13.phx.gbl...
| I want to use full text indexing. I have read you need to leave 50MB spare
| on the server. Is this per index,database or instance of SQL Server and
does
| it increase with the size of the table or is just a static amount virtual
| memory to be put aside. Regards.
|
|
|
||||Chris, you are referencing Kalen's "Inside SQL Server 2000" book on page583
as she states that at least 50MB of hard drive space must be available to
create a FT Catalog on the disk drive. I don't have disk small enough to
test this <g>, but if you are FT Indexing via the FT Wizard and placing the
FT Catalog on a disk drive of less that 50MB, you will get an error.
Although, I found no reference to 30% of anything. Could you clarify more
what your concerns are?
Note, you can also post FTS related questions to the newsgroup:
microsoft.public.sqlserver.fulltext
Regards,
John
"Chris Kennedy" <nospam@.microsoft.com> wrote in message
news:#$7LI#33DHA.2544@.TK2MSFTNGP10.phx.gbl...
> I read it in Inside SQL Server. I may have got it wrong. I read 5O MB plus
> about 30% of the table size.
> "Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
> news:#FAAcBs3DHA.484@.TK2MSFTNGP10.phx.gbl...
> | Where did you read? Could you show us a link? Is that RAM or hard disk
> | space?
> |
> | Full-Text search service, indexes the data in your tables, in its own
> index
> | files outside SQL Server. So, the bigger your tables, the bigger the
full
> | text catalog file size.
> | --
> | HTH,
> | Vyas, MVP (SQL Server)
> | http://vyaskn.tripod.com/
> | Is .NET important for a database professional?
> | http://vyaskn.tripod.com/poll.htm
> |
> |
> |
> |
> | "Chris Kennedy" <nospam@.microsoft.com> wrote in message
> | news:uzfFfzq3DHA.2888@.tk2msftngp13.phx.gbl...
> | I want to use full text indexing. I have read you need to leave 50MB
spare
> | on the server. Is this per index,database or instance of SQL Server and
> does
> | it increase with the size of the table or is just a static amount
virtual
> | memory to be put aside. Regards.
> |
> |
> |
> |
>|||What amount of space will a full text index take in e. g. a 10 MB table.
"John Kane" <jt-kane@.comcast.net> wrote in message
news:OBnfOx53DHA.2460@.TK2MSFTNGP10.phx.gbl...
| Chris, you are referencing Kalen's "Inside SQL Server 2000" book on
page583
| as she states that at least 50MB of hard drive space must be available to
| create a FT Catalog on the disk drive. I don't have disk small enough to
| test this <g>, but if you are FT Indexing via the FT Wizard and placing
the
| FT Catalog on a disk drive of less that 50MB, you will get an error.
| Although, I found no reference to 30% of anything. Could you clarify more
| what your concerns are?
|
| Note, you can also post FTS related questions to the newsgroup:
| microsoft.public.sqlserver.fulltext
| Regards,
| John
|
|
|
| "Chris Kennedy" <nospam@.microsoft.com> wrote in message
| news:#$7LI#33DHA.2544@.TK2MSFTNGP10.phx.gbl...
| > I read it in Inside SQL Server. I may have got it wrong. I read 5O MB
plus
| > about 30% of the table size.
| >
| > "Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
| > news:#FAAcBs3DHA.484@.TK2MSFTNGP10.phx.gbl...
| > | Where did you read? Could you show us a link? Is that RAM or hard disk
| > | space?
| > |
| > | Full-Text search service, indexes the data in your tables, in its own
| > index
| > | files outside SQL Server. So, the bigger your tables, the bigger the
| full
| > | text catalog file size.
| > | --
| > | HTH,
| > | Vyas, MVP (SQL Server)
| > | http://vyaskn.tripod.com/
| > | Is .NET important for a database professional?
| > | http://vyaskn.tripod.com/poll.htm
| > |
| > |
| > |
| > |
| > | "Chris Kennedy" <nospam@.microsoft.com> wrote in message
| > | news:uzfFfzq3DHA.2888@.tk2msftngp13.phx.gbl...
| > | I want to use full text indexing. I have read you need to leave 50MB
| spare
| > | on the server. Is this per index,database or instance of SQL Server
and
| > does
| > | it increase with the size of the table or is just a static amount
| virtual
| > | memory to be put aside. Regards.
| > |
| > |
| > |
| > |
| >
| >
|
|

Full Text Search without any result

Dear all,
I've build a FullText Indexing at Enterprise Manager. However, when I run
the following query, it does not have any result return:
select u_documenttype, u_document, u_filename from doclib where
freetext(u_document, ' "category" or "eis" ')
Does anyone have any idea about my situation?
Thanks
Best Regards,
Eilsa
One more thing, the "u_document" is an image type
thanks
"Eilsa" <asd@.asd.asd> wrote in message
news:OYvWvh1eEHA.2352@.TK2MSFTNGP09.phx.gbl...
> Dear all,
> I've build a FullText Indexing at Enterprise Manager. However, when I run
> the following query, it does not have any result return:
> select u_documenttype, u_document, u_filename from doclib where
> freetext(u_document, ' "category" or "eis" ')
> Does anyone have any idea about my situation?
>
> Thanks
> Best Regards,
> Eilsa
>
|||Eilsa,
Yes, I do... Could you post the full output of the following SQL code?
use <your_database_name_here>
go
SELECT @.@.language
SELECT @.@.version
EXEC sp_help doclib
go
Additionally, what is the language of the text in the documents (MS Word
files) that you are storing in column "u_document" and how did you import or
upload these files to SQL Server? Both questions as well as the datatype and
size of the file extension column in your table doclib will provide clues to
answer your question.
Regards,
John
"Eilsa" <asd@.asd.asd> wrote in message
news:OTAVJx1eEHA.2352@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> One more thing, the "u_document" is an image type
> thanks
> "Eilsa" <asd@.asd.asd> wrote in message
> news:OYvWvh1eEHA.2352@.TK2MSFTNGP09.phx.gbl...
run
>
|||us_english
(1 row(s) affected)
Microsoft SQL Server 2000-8.00.194(IntelX86)
Aug620000:57:48
Copyright(c)1988-2000 Microsoft Corporation
DeveloperEditionon Windows NT5 (Build2195:00:00 Service Pack 4)
(1 row(s) affected)
NameOwnerTypeCreated_datetime
DocFiledbouser table8/9/2004 06:23.5
Column_nameTypeComputedLengthPrecScaleNullableTrimTrailingBlanksFixedLenNullInSourceCollation
------
File_IDintno4100no(n/a)(n/a)NULL
Fileimageno16yes(n/a)(n/a)NULL
FileTypecharno3yesnoyesSQL_Latin1_General_CP1_CI_AS
IdentitySeedIncrementNot ForReplication
No identity column defined.NULLNULLNULL
RowGuidCol
No rowguidcol column defined.
Data_located_on_filegroup
PRIMARY
index_nameindex_descriptionindex_keys
-----
PK_File clustered, unique,primary key located on PRIMARYFile_ID
constraint_typeconstraint_namedelete_actionupdate_actionstatus_enabledstatus_for_replicationconstraint_keys
------
PRIMARYKEY(clustered)PK_File(n/a)(n/a)(n/a)(n/a)File_ID
No foreign keysreference this table.
Table is referenced by views
"John Kane" <jt-kane@.comcast.net> wrote in message news:<OcV90A2eEHA.3016@.tk2msftngp13.phx.gbl>...[vbcol=seagreen]
> Eilsa,
> Yes, I do... Could you post the full output of the following SQL code?
> use <your_database_name_here>
> go
> SELECT @.@.language
> SELECT @.@.version
> EXEC sp_help doclib
> go
> Additionally, what is the language of the text in the documents (MS Word
> files) that you are storing in column "u_document" and how did you import or
> upload these files to SQL Server? Both questions as well as the datatype and
> size of the file extension column in your table doclib will provide clues to
> answer your question.
> Regards,
> John
>
> "Eilsa" <asd@.asd.asd> wrote in message
> news:OTAVJx1eEHA.2352@.TK2MSFTNGP09.phx.gbl...
> run
|||Thanks, Bob,
You're using SQL Server 2000 (RTM) Developer Edition on Windows 2000. You're
table DocFile and your file extension column is FileType char(3) and
Nullable. However, I still need additional info, specifically what is the
language of the text in the documents (MS Word files) that you are storing
in column "u_document" and how did you import or upload these files to SQL
Server?
I've attached a SQL script file (Import_FTS_Images.sql) that uses TextCopy
to import documents as well as html pages into a test table FTSTable that
also has a file extension column (ExtCol) defined as char(3) and Nullable
and this configuration as worked for years with US_English documents. Test
your document upload into this configuration and then run a Full Population
and test FTS queries. If you still have a problem getting the expected
results, please post the exact SQL query as well as the exact sample data
contained in the document/html pages.
Thanks,
John
"Bob" <kcsc1@.hotpop.com> wrote in message
news:ef3b388e.0408100822.603f67f2@.posting.google.c om...
> us_english
> (1 row(s) affected)
> Microsoft SQL Server 2000-8.00.194 (Intel X86)
> Aug 6 2000 0:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Developer Edition on Windows NT5 (Build 2195:00:00 Service Pack 4)
> (1 row(s) affected)
> Name Owner Type Created_datetime
> DocFile dbo user table 8/9/2004 06:23.5
>
> Column_name Type Computed Length Prec Scale Nullable TrimTrailingBlanks
FixedLenNullInSource Collation
> ----

> File_ID int no 4 10 0 no (n/a) (n/a) NULL
> File image no 16 yes (n/a) (n/a) NULL
> FileType char no 3 yes no yes SQL_Latin1_General_CP1_CI_AS
>
> Identity Seed Increment Not For Replication
> ----
--
> No identity column defined. NULL NULL NULL
>
> RowGuidCol
> --
> No rowguidcol column defined.
>
> Data_located_on_filegroup
> --
> PRIMARY
>
> index_name index_description index_keys
> ----
--
> PK_File clustered, unique,primary key located on PRIMARY File_ID
>
> constraint_type constraint_name delete_action update_action status_enabled
status_for_replication constraint_keys
> ----

> PRIMARY KEY (clustered) PK_File (n/a) (n/a) (n/a) (n/a) File_ID
>
> No foreign keys reference this table.
> Table is referenced by views
>
> "John Kane" <jt-kane@.comcast.net> wrote in message
news:<OcV90A2eEHA.3016@.tk2msftngp13.phx.gbl>...[vbcol=seagreen]
import or[vbcol=seagreen]
and[vbcol=seagreen]
clues to[vbcol=seagreen]
I[vbcol=seagreen]
begin 666 Import_FTS_Images.sql
M#0IU<V4@.<'5B<PT*9V\-"FEF(&5X:7-T<R H<V5L96-T("H@.9G)O;2!S>7-O
M8FIE8W1S('=H97)E(&ED(#T@.;V)J96-T7VED*"=&5%-486)L92<I*0T*("!D
M<F]P('1A8FQE($944U1A8FQE#0IG;PT*#0I#4D5!5$4@.5$%"3$4@.1 E135&%B
M;&4@.* T*("!+97E#;VP):6YT($E$14Y42519("@.Q+#$I($Y/5"!.54Q,( T*
M(" @.($-/3E-44D%)3E0@.1E135&%B;&5?2418(%!224U!4ED@.2T59($-,55-4
M15)%1"P-"B @.5&5X=$-O; ET97AT($Y53$PL#0H@.($EM86=E0V]L"6EM86=E
M($Y53$PL#0H@.($5X=$-O; EC:&%R*#,I($Y53$PL("TM(&-A;B!B92!E:71H
M97(@.<WES;F%M92!O<B!C:&%R*#,I#0H@.(%1I;653=&%M<$-O; ET:6UE<W1A
M;7 @.3E5,3" -"BD@.3TX@.6U!224U!4EE=#0IG;PT*#0H-"BTM($EN<V5R="!D
M871A+BXN("A.;W1E.B!);FET86QI>FEN9R!)34%'12!C;VQU; 6X@.=VET:" P
M>$9&1D9&1D9&(&9O<B!U<V4@.=VET:"!497AT0V]P>2YE>&4I#0I)3E-%4E0@.
M1E135&%B;&4@.=F%L=65S*"=497-T(%1%6%0@.1&%T82!F;W(@.<F]W(#$G+" P
M>$9&1D9&1D9&+" G9&]C)RP@.3E5,3"D-"DE.4T525"!&5%-486)L92!V86QU
M97,H)U1E<W0@.5$585"!$871A(&9O<B!R;W<@.,B<L(#!X1D9&1 D9&1D8L("=X
M;',G+"!.54Q,*0T*24Y315)4($944U1A8FQE('9A;'5E<R@.G5 &5S="!415A4
M($1A=&$@.9F]R(')O=R S)RP@.,'A&1D9&1D9&1BP@.)W!P="<L($Y53$PI#0I)
M3E-%4E0@.1E135&%B;&4@.=F%L=65S*"=497-T(%1%6%0@.1&%T82!F;W(@.<F]W
M(#0G+" P>$9&1D9&1D9&+" G='AT)RP@.3E5,3"D-"DE.4T525"!&5%-486)L
M92!V86QU97,H)U1E<W0@.5$585"!$871A(&9O<B!R;W<@.-2<L(#!X1D9&1D9&
M1D8L("=H=&TG+"!.54Q,*0T*24Y315)4($944U1A8FQE('9A; '5E<R@.G5&5S
M="!415A4($1A=&$@.9F]R(')O=R V)RP@.,'A&1D9&1D9&1BP@.)W!D9B<L($Y5
M3$PI#0I)3E-%4E0@.1E135&%B;&4@.=F%L=65S*"=497-T(%1%6%0@.1&%T82!F
M;W(@.<F]W(#<G+" P>$9&1D9&1D9&+" G>&UL)RP@.3E5,3"D-"F=O#0H-"@.T*
M+2T@.4V5L96-T(&1A=&$-"E-%3$5#5" J(&9R;VT@.1E135&%B;&4-"F=O#0H-
M"@.T*9&5C;&%R92! <75E<GD@.=F%R8VAA<B@.R,# I#0HM+2!);G-E<G0@.2%1-
M3%]F:6QE+FAT;2!I;G1O(%)O=R U("$A#0HM+2!.3U1%.B!%;G-U<F4@.=&AE
M(&-O<G)E8W0@.<&%T:"!F;W(@.=&5X=&-O<'DN97AE(2$-"G-E="! <75E<GD@.
M/2 G1#I<35-344PX,%Q-4U-13"1344PX,%Q":6YN7'1E>'1C;W!Y("]S("<K
M0$!S97)V97)N86UE*R<@.+W4@.<V$@.+W @.+V0@.<'5B<R O="!&5%-486)L92 O
M8R!);6%G94-O;" O9B!$.EQ344Q&:6QE<UQ3:&EL;VA</$A434Q?9FEL93XN
M:'1M("]I("]K(#4P,# @.+W<@.(G=H97)E($ME>4-O;#TU(B<-"G!R:6YT($!Q
M=65R>0T*97AE8R!M87-T97(N+GAP7V-M9'-H96QL($!Q=65R>0T*9V\-"@.T*
M9&5C;&%R92! <75E<GD@.=F%R8VAA<B@.R,# I#0HM+2!);G-E<G0@.35-?5V]R
M9"YD;V,@.:6YT;R!2;W<@.,2 A(0T*<V5T($!Q=65R>2 ]("=$.EQ-4U-13#@.P
M7$U34U%,)%-13#@.P7$)I;FY<=&5X=&-O<'D@.+W,@.)RM 0'-E<G9E<FYA;64K
M)R O=2!S82 O<" O9"!P=6)S("]T($944U1A8FQE("]C($EM86=E0V]L("]F
M($0Z7$I+86YE7$1O8W-</$U37U=O<F0^+F1O8R O:2 O:R U,# P("]W(")W
M:&5R92!+97E#;VP],2(G#0IP<FEN="! <75E<GD-"F5X96,@.;6%S=&5R+BYX
M<%]C;61S:&5L;"! <75E<GD-"F=O#0H-"BTM(%-E;&5C="!D871A#0I314Q%
M0U0@.*B!F<F]M($944U1A8FQE#0IG;PT*#0H-"BTM($9422 -"G5S92!P=6)S
M#0IG;PT*97AE8R!S<%]F=6QL=&5X=%]D871A8F%S92 G96YA8FQE)R -"F=O
M#0IE>&5C('-P7V9U;&QT97AT7W-E<G9I8V4@.)V-L96%N7W5P)PT*#0HM+2!$
M<F]P($9422P@.:68@.;F5C97-S87)Y+BXN#0IE>&5C('-P7V9U;&QT97AT7W1A
M8FQE("=&5%-486)L92<L)V1R;W G#0IE>&5C('-P7V9U;&QT97AT7T-A=&%L
M;V<@.)T944T-A=&%L;V<G+"=D<F]P)PT*#0H-"F5X96,@.<W!?9G5L;'1E>'1?
M8V%T86QO9R G1E130V%T86QO9R<L)V-R96%T92<-"F5X96,@.<W!?9G5L;'1E
M>'1?=&%B;&4@.)T944U1A8FQE)RPG8W)E871E)RPG1E130V%T8 6QO9R<L)T94
M4U1A8FQE7TE$6"<-"F5X96,@.<W!?9G5L;'1E>'1?8V]L=6UN("=&5%-486)L
M92<L)TEM86=E0V]L)RPG861D)RP@.,'@.P-# Y+" G17AT0V]L)R -"F5X96,@.
M<W!?9G5L;'1E>'1?8V]L=6UN("=&5%-486)L92<L)U1E>'1#;VPG+"=A9&0G
M( T*97AE8R!S<%]F=6QL=&5X=%]T86)L92 G1E135&%B;&4G+" G86-T:79A
M=&4G(" -"F=O#0H-"BTM(%-T87)T($94($EN9&5X:6YG+BXN#0IE>&5C('-P
M7V9U;&QT97AT7V-A=&%L;V<@.)T944T-A=&%L;V<G+"=S=&%R=%]F=6QL)PT*
M9V\-"BTM(%=A:70@.9F]R($94($EN9&5X:6YG('1O(&-O;7!L971E(&%N9"!C
M:&5C:R!.5"]7:6XR2R!!<'!L:6-A=&EO;B!L;V<@.9F]R('-U8V-E<W,O97)R
M;W)S+BX-"@.T*#0IS96QE8W0@.*B!F<F]M($944U1A8FQE#0IG;PT*+2T@.4V5A
M<F-H(&9O<B!S96%R8VA?=V]R9%]H97)E(&EN($A434P@.9FEL92XN#0IS96QE
M8W0@.2V5Y0V]L+"!);6%G94-O;" @.9G)O;2!&5%-486)L92!W:&5R92!C;VYT
M86EN<R@.J+"<\<V5A<F-H7W=O<F1?:&5R93XG*2!O<F1E<B!B>2!+97E#;VP@.
M#0IG;PT*+2T@.4V5A<F-H(&9O<B!S96%R8VA?=V]R9%]H97)E(&EN("Y$3T,@.
M9FEL92XN+@.T*<V5L96-T($ME>4-O;"P@.26UA9V5#;VP@.9G)O;2!&5%-486)L
M92!W:&5R92!C;VYT86EN<R@.J+"<\<V5A<F-H7W=O<F1?:&5R93XG*2!O<F1E
M<B!B>2!+97E#;VP@.#0IG;PT*#0H-"BTM($-O;F9I<FT@.1E0@.4')O<&5R=&EE
M<RXN+@.T*=7-E('!U8G,-"F=O#0IS<%]H96QP7V9U;&QT97AT7V-A=&%L;V=S
M("=&5%-#871A;&]G)R -"F=O#0IS<%]H96QP7V9U;&QT97AT7W1A8FQE<R G
M1E130V%T86QO9R<@.( T*9V\-"G-P7VAE;'!?9G5L;'1E>'1?8V]L=6UN<R G
M1E135&%B;&4G#0IG;PT*4T5,14-4(&9U;&QT97AT8V%T86QO9W!R;W!E<G1Y
M*"=&5%-#871A;&]G)RP@.)U!O<'5L871E4W1A='5S)RD@.#0IG;PT*#0HM+2!2
M96UO=F4@.1E0@.26YD97AE<R F($-A=&%L;V<@.)B!T86)L92XN#0H-"F5X96,@.
M<W!?9G5L;'1E>'1?=&%B;&4@.)T944U1A8FQE)RPG9')O<"<-"@.T*97AE8R!S
M<%]F=6QL=&5X=%]#871A;&]G("=&5%-#871A;&]G)RPG9')O<"<-"@.T*9')O
4<"!T86)L92!&5%-486)L90T*#0H`
`
end

2012年3月26日星期一

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 know which row has error in indexing

Hello everybody,
I have installed SQLServer 2005 for take advantage of full text seach
features.
When I start full population, there are some rows that cause error and not
are indexed.
I see the log in C:\Programmi\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\SQLFT0000700005.LOG. In this file there are seven
rows that have error and for everyone a line that say:
"Error '0x8004fd01: The IFilter::Init() function call failed.' ...
full-text key value 0x495532303045594154504B55. Attempt will be made to
reindex it. The component 'pdffilt.dll' reported error while indexing.
Component path 'C:\Programmi\Foxit Software\Foxit PDF IFilter\pdffilt.dll'."
With different full-text key value for every line.
My question is:
1) Start from a full-text key (ie. 0x495532303045594154504B55), how I arrive
to the record in the source table for understand which is the
problem?Otherwise how can I examine the problem if I don't know the row that
cause the error?
2) What is the error 0x8004fd01?
3) Could be that the PDF filter of Foxit is better than Adobe? With Adobe
filter (version 6) my full pupulation is endless!
Thanks!
OK resolved !!!
1)The hexadecimal value must to be converted to decimal and then to ASCII
(http://www.vortex.prodigynet.co.uk/misc/ascii_conv.html)
2) Probably due to the incorrect format because changing the type column
value from ".pdf" to ".txt" the problem has been resolved!!!
3) Wait your opinions :-)
NicolaZap
"NicolaZap" wrote:

> Hello everybody,
> I have installed SQLServer 2005 for take advantage of full text seach
> features.
> When I start full population, there are some rows that cause error and not
> are indexed.
> I see the log in C:\Programmi\Microsoft SQL
> Server\MSSQL.1\MSSQL\LOG\SQLFT0000700005.LOG. In this file there are seven
> rows that have error and for everyone a line that say:
> "Error '0x8004fd01: The IFilter::Init() function call failed.' ...
> full-text key value 0x495532303045594154504B55. Attempt will be made to
> reindex it. The component 'pdffilt.dll' reported error while indexing.
> Component path 'C:\Programmi\Foxit Software\Foxit PDF IFilter\pdffilt.dll'."
> With different full-text key value for every line.
>
> My question is:
> 1) Start from a full-text key (ie. 0x495532303045594154504B55), how I arrive
> to the record in the source table for understand which is the
> problem?Otherwise how can I examine the problem if I don't know the row that
> cause the error?
> 2) What is the error 0x8004fd01?
> 3) Could be that the PDF filter of Foxit is better than Adobe? With Adobe
> filter (version 6) my full pupulation is endless!
>
> Thanks!
>
|||Is this the 64 bit version of SQL server? If so you should be using Foxit.
"NicolaZap" <NicolaZap@.discussions.microsoft.com> wrote in message
news:091F34B8-1140-4A74-9D2A-03F02B00DB8A@.microsoft.com...[vbcol=seagreen]
> OK resolved !!!
> 1)The hexadecimal value must to be converted to decimal and then to ASCII
> (http://www.vortex.prodigynet.co.uk/misc/ascii_conv.html)
> 2) Probably due to the incorrect format because changing the type column
> value from ".pdf" to ".txt" the problem has been resolved!!!
> 3) Wait your opinions :-)
>
> NicolaZap
>
> "NicolaZap" wrote:
|||NO, it is the 32 bit versione of SQLServer2005.
"Hilary Cotter" wrote:

> Is this the 64 bit version of SQL server? If so you should be using Foxit.
> "NicolaZap" <NicolaZap@.discussions.microsoft.com> wrote in message
> news:091F34B8-1140-4A74-9D2A-03F02B00DB8A@.microsoft.com...
>
>

Full Text Search know which row has error in indexing

Hello everybody,

I have installed SQLServer 2005 for take advantage of full text seach features.

When I start full population, there are some rows that cause error and not are indexed.

I see the log in C:\Programmi\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLFT0000700005.LOG. In this file there are seven rows that have error and for everyone a line that say:

"Error '0x8004fd01: The IFilter::Init() function call failed.' ... full-text key value 0x495532303045594154504B55. Attempt will be made to reindex it. The component 'pdffilt.dll' reported error while indexing. Component path 'C:\Programmi\Foxit Software\Foxit PDF IFilter\pdffilt.dll'."

With different full-text key value for every line.

My question is:

1) Start from a full-text key (ie. 0x495532303045594154504B55), how I arrive to the record in the source table for understand which is the problem?Otherwise how can I examine the problem if I don't know the row that cause the error?

2) What is the error 0x8004fd01?

3) Could be that the PDF filter of Foxit is better than Adobe? With Adobe filter (version 6) my full pupulation is endless!

Thanks!

OK resolved

1)The hexadecimal value must to be converted to decimal and then to ASCII (http://www.vortex.prodigynet.co.uk/misc/ascii_conv.html)

2) Probably due to the incorrect format because changing the type column value from ".pdf" to ".txt" the problem has been resolved!!!

3) Wait your opinions :-)

NicolaZap

Full Text Search Indexing HTML - does the filter expect certain tags to be present as standard?

Hi, I was wondering if any SQL Server gurus out there could help me...

I have a table which contains text resources for my application. The text resources are multi-lingual so I've read that if I add a html language indicator meta tag e.g.
<META NAME="MS.LOCALE" CONTENT="ES">
and store the text in a varbinary column with a supporting Document Type column containing ".html" of varchar(5) then the full text index service should be intelligent about the language word breakers it applies when indexing the text. (I hope this is correct technique for best multi-lingual support in a single table?)

However, when I come to query this data the results always return 0 rows (no errors are encountered). e.g.
DECLARE @.SearchWord nvarchar(256)
SET @.SearchWord = 'search' -- Yes, this word is definitely present in my resources.
SELECT * FROM Resource WHERE CONTAINS(Document, @.SearchWord)

I'm a little puzzled as Full Text search is working fine on another table that employs an nvarchar column (just plain text, no html).

Does the filter used for full text indexing of html expect certain tags to be present as standard? E.g. <html> and <body> tags? At present the data I have stored might look like this (no html or body wrapping tags):

Example record 1 data: <META NAME="MS.LOCALE" CONTENT="EN">Search for keywords:

Example record 2 data: <META NAME="MS.LOCALE" CONTENT="EN">Sorry no results were found for your search.

etc.

Any pointers / suggestions would be greatly appreciated. Cheers,
Gavin.

UPDATE:
I have tried wrapping the text in more usual html tags and re-built the full text index but I still never get any rows returned for my query results. Example of content wrapping tried - <HTML><HEAD><META NAME="MS.LOCALE" CONTENT="EN"></HEAD><BODY>Test text.</BODY></HTML>

I've also tried stripping all html tags from the content and set the Document Type column = .txt but I still get no rows returned?!?I've further isolated what the problem is and have started a new thread to request more specific help...
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1844786&SiteID=17

2012年3月19日星期一

Full Text not working

I cannot get fulltext indexing to work, nor can I get any error messages to
indicate whats wrong. Here's what I did (for the pubs database)
1. From the top menu, select Tools, Full Text Indexing.
2. Click next on the opening screen.
3. On the "Select a Database" screen, choose pubs.
4. For the next screen, select "titles" as the table and click next.
5. Keep the default unique index; there is only one on the pubs table.
6. In the next screen, select Title and Notes as the fields to be indexed.
7. On the "Select a Catalog" screen, because this is the first Catalog on
the server, we are prompted for a name. In this example, "demo" is used as
the Catalog name.
8. Click next.
9. Click Finish.
10. From Enterprise Manager, expand Full-Text Catalogs
11. Right click and select "Start Full Population."
12. The catalog is now complete.
If I type sp_help_fulltext_catalogs everything looks ok.
If I type Select DATABASEPROPERTY('Pubs', 'IsFulltextEnabled')
I get a 1 which means ok.
If I type
SELECT title, notes FROM titles WHERE CONTAINS (notes, ' "quick easy" ')
I get 0 rows
Same if I enter
SELECT title, notes
FROM titles
--where notes like '%quick%'
WHERE CONTAINS (notes, ' quick ')
of course entering
SELECT title, notes
FROM titles
where notes like '%quick%'
gets me the record I want. Anyone have any ideas what I can check?
BTW I did this on another server and it works. The server is works is using
SQL Server developer edition. The server that doesn't work is my production
box using SQL Server standard edition
Thanks for the help.
Francis,
Shot in the dark...QUOTED IDENTIFIER setting...might check the spacing for
the item listed...might compare with CONTAINS in SQL BOL...same SP?
HTH
Jerry
"Francis" <Francis@.discussions.microsoft.com> wrote in message
news:1899D25D-7325-4501-9B55-691C7C053686@.microsoft.com...
>I cannot get fulltext indexing to work, nor can I get any error messages to
> indicate whats wrong. Here's what I did (for the pubs database)
> 1. From the top menu, select Tools, Full Text Indexing.
> 2. Click next on the opening screen.
> 3. On the "Select a Database" screen, choose pubs.
> 4. For the next screen, select "titles" as the table and click next.
> 5. Keep the default unique index; there is only one on the pubs table.
> 6. In the next screen, select Title and Notes as the fields to be
> indexed.
> 7. On the "Select a Catalog" screen, because this is the first Catalog on
> the server, we are prompted for a name. In this example, "demo" is used as
> the Catalog name.
> 8. Click next.
> 9. Click Finish.
> 10. From Enterprise Manager, expand Full-Text Catalogs
> 11. Right click and select "Start Full Population."
> 12. The catalog is now complete.
> If I type sp_help_fulltext_catalogs everything looks ok.
> If I type Select DATABASEPROPERTY('Pubs', 'IsFulltextEnabled')
> I get a 1 which means ok.
> If I type
> SELECT title, notes FROM titles WHERE CONTAINS (notes, ' "quick easy" ')
> I get 0 rows
> Same if I enter
>
> SELECT title, notes
> FROM titles
> --where notes like '%quick%'
> WHERE CONTAINS (notes, ' quick ')
>
> of course entering
>
> SELECT title, notes
> FROM titles
> where notes like '%quick%'
>
> gets me the record I want. Anyone have any ideas what I can check?
>
> BTW I did this on another server and it works. The server is works is
> using
> SQL Server developer edition. The server that doesn't work is my
> production
> box using SQL Server standard edition
> Thanks for the help.
>
>
>
|||Thanks Jerry. I have tried various combinations like
SELECT title, notes
FROM titles
WHERE CONTAINS (notes, 'quick')
or using double quotes with spaces in front of and behind the work quick.
I have also set up other full text indexes on this and other tables and other
databases on this server and it doesn't seem to work.
"Jerry Spivey" wrote:

> Francis,
> Shot in the dark...QUOTED IDENTIFIER setting...might check the spacing for
> the item listed...might compare with CONTAINS in SQL BOL...same SP?
> HTH
> Jerry
> "Francis" <Francis@.discussions.microsoft.com> wrote in message
> news:1899D25D-7325-4501-9B55-691C7C053686@.microsoft.com...
>
>
|||Thanks for the help. I found the problem in KB317746;
I executed the workaround described:
EXEC sp_grantlogin [NT Authority\System]
EXEC sp_addsrvrolemember @.loginame = [NT Authority\System]
, @.rolename = 'sysadmin'
and all is well now.
"Francis" wrote:
[vbcol=seagreen]
> Thanks Jerry. I have tried various combinations like
> SELECT title, notes
> FROM titles
> WHERE CONTAINS (notes, 'quick')
> or using double quotes with spaces in front of and behind the work quick.
> I have also set up other full text indexes on this and other tables and other
> databases on this server and it doesn't seem to work.
>
> "Jerry Spivey" wrote:

Full Text not working

I cannot get fulltext indexing to work, nor can I get any error messages to
indicate whats wrong. Here's what I did (for the pubs database)
1. From the top menu, select Tools, Full Text Indexing.
2. Click next on the opening screen.
3. On the "Select a Database" screen, choose pubs.
4. For the next screen, select "titles" as the table and click next.
5. Keep the default unique index; there is only one on the pubs table.
6. In the next screen, select Title and Notes as the fields to be indexed.
7. On the "Select a Catalog" screen, because this is the first Catalog on
the server, we are prompted for a name. In this example, "demo" is used as
the Catalog name.
8. Click next.
9. Click Finish.
10. From Enterprise Manager, expand Full-Text Catalogs
11. Right click and select "Start Full Population."
12. The catalog is now complete.
If I type sp_help_fulltext_catalogs everything looks ok.
If I type Select DATABASEPROPERTY('Pubs', 'IsFulltextEnabled')
I get a 1 which means ok.
If I type
SELECT title, notes FROM titles WHERE CONTAINS (notes, ' "quick easy" ')
I get 0 rows
Same if I enter
SELECT title, notes
FROM titles
--where notes like '%quick%'
WHERE CONTAINS (notes, ' quick ')
of course entering
SELECT title, notes
FROM titles
where notes like '%quick%'
gets me the record I want. Anyone have any ideas what I can check?
BTW I did this on another server and it works. The server is works is using
SQL Server developer edition. The server that doesn't work is my production
box using SQL Server standard edition
Thanks for the help.Francis,
Shot in the dark...QUOTED IDENTIFIER setting...might check the spacing for
the item listed...might compare with CONTAINS in SQL BOL...same SP?
HTH
Jerry
"Francis" <Francis@.discussions.microsoft.com> wrote in message
news:1899D25D-7325-4501-9B55-691C7C053686@.microsoft.com...
>I cannot get fulltext indexing to work, nor can I get any error messages to
> indicate whats wrong. Here's what I did (for the pubs database)
> 1. From the top menu, select Tools, Full Text Indexing.
> 2. Click next on the opening screen.
> 3. On the "Select a Database" screen, choose pubs.
> 4. For the next screen, select "titles" as the table and click next.
> 5. Keep the default unique index; there is only one on the pubs table.
> 6. In the next screen, select Title and Notes as the fields to be
> indexed.
> 7. On the "Select a Catalog" screen, because this is the first Catalog on
> the server, we are prompted for a name. In this example, "demo" is used as
> the Catalog name.
> 8. Click next.
> 9. Click Finish.
> 10. From Enterprise Manager, expand Full-Text Catalogs
> 11. Right click and select "Start Full Population."
> 12. The catalog is now complete.
> If I type sp_help_fulltext_catalogs everything looks ok.
> If I type Select DATABASEPROPERTY('Pubs', 'IsFulltextEnabled')
> I get a 1 which means ok.
> If I type
> SELECT title, notes FROM titles WHERE CONTAINS (notes, ' "quick easy" ')
> I get 0 rows
> Same if I enter
>
> SELECT title, notes
> FROM titles
> --where notes like '%quick%'
> WHERE CONTAINS (notes, ' quick ')
>
> of course entering
>
> SELECT title, notes
> FROM titles
> where notes like '%quick%'
>
> gets me the record I want. Anyone have any ideas what I can check?
>
> BTW I did this on another server and it works. The server is works is
> using
> SQL Server developer edition. The server that doesn't work is my
> production
> box using SQL Server standard edition
> Thanks for the help.
>
>
>|||Thanks Jerry. I have tried various combinations like
SELECT title, notes
FROM titles
WHERE CONTAINS (notes, 'quick')
or using double quotes with spaces in front of and behind the work quick.
I have also set up other full text indexes on this and other tables and othe
r
databases on this server and it doesn't seem to work.
"Jerry Spivey" wrote:

> Francis,
> Shot in the dark...QUOTED IDENTIFIER setting...might check the spacing for
> the item listed...might compare with CONTAINS in SQL BOL...same SP?
> HTH
> Jerry
> "Francis" <Francis@.discussions.microsoft.com> wrote in message
> news:1899D25D-7325-4501-9B55-691C7C053686@.microsoft.com...
>
>|||Thanks for the help. I found the problem in KB317746;
I executed the workaround described:
EXEC sp_grantlogin [NT Authority\System]
EXEC sp_addsrvrolemember @.loginame = [NT Authority\System]
, @.rolename = 'sysadmin'
and all is well now.
"Francis" wrote:
[vbcol=seagreen]
> Thanks Jerry. I have tried various combinations like
> SELECT title, notes
> FROM titles
> WHERE CONTAINS (notes, 'quick')
> or using double quotes with spaces in front of and behind the work quick.
> I have also set up other full text indexes on this and other tables and ot
her
> databases on this server and it doesn't seem to work.
>
> "Jerry Spivey" wrote:
>

Full Text not working

I cannot get fulltext indexing to work, nor can I get any error messages to
indicate whats wrong. Here's what I did (for the pubs database)
1. From the top menu, select Tools, Full Text Indexing.
2. Click next on the opening screen.
3. On the "Select a Database" screen, choose pubs.
4. For the next screen, select "titles" as the table and click next.
5. Keep the default unique index; there is only one on the pubs table.
6. In the next screen, select Title and Notes as the fields to be indexed.
7. On the "Select a Catalog" screen, because this is the first Catalog on
the server, we are prompted for a name. In this example, "demo" is used as
the Catalog name.
8. Click next.
9. Click Finish.
10. From Enterprise Manager, expand Full-Text Catalogs
11. Right click and select "Start Full Population."
12. The catalog is now complete.
If I type sp_help_fulltext_catalogs everything looks ok.
If I type Select DATABASEPROPERTY('Pubs', 'IsFulltextEnabled')
I get a 1 which means ok.
If I type
SELECT title, notes FROM titles WHERE CONTAINS (notes, ' "quick easy" ')
I get 0 rows
Same if I enter
SELECT title, notes
FROM titles
--where notes like '%quick%'
WHERE CONTAINS (notes, ' quick ')
of course entering
SELECT title, notes
FROM titles
where notes like '%quick%'
gets me the record I want. Anyone have any ideas what I can check?
BTW I did this on another server and it works. The server is works is using
SQL Server developer edition. The server that doesn't work is my production
box using SQL Server standard edition
Thanks for the help.Francis,
Shot in the dark...QUOTED IDENTIFIER setting...might check the spacing for
the item listed...might compare with CONTAINS in SQL BOL...same SP?
HTH
Jerry
"Francis" <Francis@.discussions.microsoft.com> wrote in message
news:1899D25D-7325-4501-9B55-691C7C053686@.microsoft.com...
>I cannot get fulltext indexing to work, nor can I get any error messages to
> indicate whats wrong. Here's what I did (for the pubs database)
> 1. From the top menu, select Tools, Full Text Indexing.
> 2. Click next on the opening screen.
> 3. On the "Select a Database" screen, choose pubs.
> 4. For the next screen, select "titles" as the table and click next.
> 5. Keep the default unique index; there is only one on the pubs table.
> 6. In the next screen, select Title and Notes as the fields to be
> indexed.
> 7. On the "Select a Catalog" screen, because this is the first Catalog on
> the server, we are prompted for a name. In this example, "demo" is used as
> the Catalog name.
> 8. Click next.
> 9. Click Finish.
> 10. From Enterprise Manager, expand Full-Text Catalogs
> 11. Right click and select "Start Full Population."
> 12. The catalog is now complete.
> If I type sp_help_fulltext_catalogs everything looks ok.
> If I type Select DATABASEPROPERTY('Pubs', 'IsFulltextEnabled')
> I get a 1 which means ok.
> If I type
> SELECT title, notes FROM titles WHERE CONTAINS (notes, ' "quick easy" ')
> I get 0 rows
> Same if I enter
>
> SELECT title, notes
> FROM titles
> --where notes like '%quick%'
> WHERE CONTAINS (notes, ' quick ')
>
> of course entering
>
> SELECT title, notes
> FROM titles
> where notes like '%quick%'
>
> gets me the record I want. Anyone have any ideas what I can check?
>
> BTW I did this on another server and it works. The server is works is
> using
> SQL Server developer edition. The server that doesn't work is my
> production
> box using SQL Server standard edition
> Thanks for the help.
>
>
>|||Thanks Jerry. I have tried various combinations like
SELECT title, notes
FROM titles
WHERE CONTAINS (notes, 'quick')
or using double quotes with spaces in front of and behind the work quick.
I have also set up other full text indexes on this and other tables and other
databases on this server and it doesn't seem to work.
"Jerry Spivey" wrote:
> Francis,
> Shot in the dark...QUOTED IDENTIFIER setting...might check the spacing for
> the item listed...might compare with CONTAINS in SQL BOL...same SP?
> HTH
> Jerry
> "Francis" <Francis@.discussions.microsoft.com> wrote in message
> news:1899D25D-7325-4501-9B55-691C7C053686@.microsoft.com...
> >I cannot get fulltext indexing to work, nor can I get any error messages to
> > indicate whats wrong. Here's what I did (for the pubs database)
> >
> > 1. From the top menu, select Tools, Full Text Indexing.
> >
> > 2. Click next on the opening screen.
> >
> > 3. On the "Select a Database" screen, choose pubs.
> >
> > 4. For the next screen, select "titles" as the table and click next.
> >
> > 5. Keep the default unique index; there is only one on the pubs table.
> >
> > 6. In the next screen, select Title and Notes as the fields to be
> > indexed.
> >
> > 7. On the "Select a Catalog" screen, because this is the first Catalog on
> > the server, we are prompted for a name. In this example, "demo" is used as
> > the Catalog name.
> >
> > 8. Click next.
> >
> > 9. Click Finish.
> >
> > 10. From Enterprise Manager, expand Full-Text Catalogs
> >
> > 11. Right click and select "Start Full Population."
> >
> > 12. The catalog is now complete.
> >
> > If I type sp_help_fulltext_catalogs everything looks ok.
> >
> > If I type Select DATABASEPROPERTY('Pubs', 'IsFulltextEnabled')
> > I get a 1 which means ok.
> >
> > If I type
> >
> > SELECT title, notes FROM titles WHERE CONTAINS (notes, ' "quick easy" ')
> > I get 0 rows
> >
> > Same if I enter
> >
> >
> > SELECT title, notes
> > FROM titles
> > --where notes like '%quick%'
> > WHERE CONTAINS (notes, ' quick ')
> >
> >
> >
> > of course entering
> >
> >
> > SELECT title, notes
> > FROM titles
> > where notes like '%quick%'
> >
> >
> >
> > gets me the record I want. Anyone have any ideas what I can check?
> >
> >
> > BTW I did this on another server and it works. The server is works is
> > using
> > SQL Server developer edition. The server that doesn't work is my
> > production
> > box using SQL Server standard edition
> >
> > Thanks for the help.
> >
> >
> >
> >
> >
>
>|||Thanks for the help. I found the problem in KB317746;
I executed the workaround described:
EXEC sp_grantlogin [NT Authority\System]
EXEC sp_addsrvrolemember @.loginame = [NT Authority\System]
, @.rolename = 'sysadmin'
and all is well now.
"Francis" wrote:
> Thanks Jerry. I have tried various combinations like
> SELECT title, notes
> FROM titles
> WHERE CONTAINS (notes, 'quick')
> or using double quotes with spaces in front of and behind the work quick.
> I have also set up other full text indexes on this and other tables and other
> databases on this server and it doesn't seem to work.
>
> "Jerry Spivey" wrote:
> > Francis,
> >
> > Shot in the dark...QUOTED IDENTIFIER setting...might check the spacing for
> > the item listed...might compare with CONTAINS in SQL BOL...same SP?
> >
> > HTH
> >
> > Jerry
> > "Francis" <Francis@.discussions.microsoft.com> wrote in message
> > news:1899D25D-7325-4501-9B55-691C7C053686@.microsoft.com...
> > >I cannot get fulltext indexing to work, nor can I get any error messages to
> > > indicate whats wrong. Here's what I did (for the pubs database)
> > >
> > > 1. From the top menu, select Tools, Full Text Indexing.
> > >
> > > 2. Click next on the opening screen.
> > >
> > > 3. On the "Select a Database" screen, choose pubs.
> > >
> > > 4. For the next screen, select "titles" as the table and click next.
> > >
> > > 5. Keep the default unique index; there is only one on the pubs table.
> > >
> > > 6. In the next screen, select Title and Notes as the fields to be
> > > indexed.
> > >
> > > 7. On the "Select a Catalog" screen, because this is the first Catalog on
> > > the server, we are prompted for a name. In this example, "demo" is used as
> > > the Catalog name.
> > >
> > > 8. Click next.
> > >
> > > 9. Click Finish.
> > >
> > > 10. From Enterprise Manager, expand Full-Text Catalogs
> > >
> > > 11. Right click and select "Start Full Population."
> > >
> > > 12. The catalog is now complete.
> > >
> > > If I type sp_help_fulltext_catalogs everything looks ok.
> > >
> > > If I type Select DATABASEPROPERTY('Pubs', 'IsFulltextEnabled')
> > > I get a 1 which means ok.
> > >
> > > If I type
> > >
> > > SELECT title, notes FROM titles WHERE CONTAINS (notes, ' "quick easy" ')
> > > I get 0 rows
> > >
> > > Same if I enter
> > >
> > >
> > > SELECT title, notes
> > > FROM titles
> > > --where notes like '%quick%'
> > > WHERE CONTAINS (notes, ' quick ')
> > >
> > >
> > >
> > > of course entering
> > >
> > >
> > > SELECT title, notes
> > > FROM titles
> > > where notes like '%quick%'
> > >
> > >
> > >
> > > gets me the record I want. Anyone have any ideas what I can check?
> > >
> > >
> > > BTW I did this on another server and it works. The server is works is
> > > using
> > > SQL Server developer edition. The server that doesn't work is my
> > > production
> > > box using SQL Server standard edition
> > >
> > > Thanks for the help.
> > >
> > >
> > >
> > >
> > >
> >
> >
> >

Full text indexing with Japanese characters problem

Hi all,
I am quite experimented with SQL Server, but not that much with full
text indexing. After some successful attempts with english fields, I've
decided to try it with Japanese characters. I don't know why, but it
seems to have a strange behaviour.
As in this screenshot
(http://img65.imageshack.us/img65/980/jap3xt.gif), the CONTAINS
function does not seem to return only fields with an exact word match
of the given "word" (query), but also strange results which does not
even correspond to the query. Can anybody help me with that one?
Thanks!
ibiza
I'm not sure about your problem, but could I have a copy of your DB?
That looks amazingly interesting I love japanese ^_^
|||well, if you can help me with that problem, I'd be glad to consider it

(be warned though, it's more than 500MB in size...)
But seriously, I really don't understand why is the full-text indexing
service getting me those "almost random" rows where the dic_kana column
does not contain an exact match...yes, both the query and most of the
returned rows stard with "=E3=81=8A=E3=82=82", but that's the only resembla=
nce I
can find...
please help!
thanks
ibiza
|||well, if you can help me with that problem, I'd be glad to consider it

(be warned though, it's more than 500MB in size...)
But seriously, I really don't understand why is the full-text indexing
service getting me those "almost random" rows where the dic_kana column
does not contain an exact match...yes, both the query and most of the
returned rows stard with "=E3=81=8A=E3=82=82", but that's the only resembla=
nce I
can find...
someone please help!
thanks
ibiza
|||Does text indexing support non-latin characters?
|||Hi again,
I did some other tests with english this time, and they all seemed
successful...until this one :
http://img155.imageshack.us/img155/2001/untitled1tx.gif
Why is the CONTAINS returning no row at all? ;_;
This makes me doubt about the validity of all the previous succesful
queries I made...Could there be missing words, if some queries like the
one with 'now' isn't returning any at all?
What's the problem with full text indexing? :S
And yes I did repopulate all the indexes before running this query...
help would be greatly appreciated!
thanks
ibiza

Full text indexing with Japanese characters problem

Hi all,
I am quite experimented with SQL Server, but not that much with full
text indexing. After some successful attempts with english fields, I've
decided to try it with Japanese characters. I don't know why, but it
seems to have a strange behaviour.
As in this screenshot
(http://img65.imageshack.us/img65/980/jap3xt.gif), the CONTAINS
function does not seem to return only fields with an exact word match
of the given "word" (query), but also strange results which does not
even correspond to the query. Can anybody help me with that one?
Thanks!
ibiza
This is probably due to the way the Japanese characters are broken by the
word breakers at index time and stored in the full text index. For example
Japanese consists of 5 different character sets. Japanese "words" are
largely syllables, so when you search on a "word" what it matches to are a
variety of sub tokens/syllables.
What you need to do is have someone who is fluent in Japanese verify that
your search application is actually finding what you are looking for. My
knowledge of Japanese is limited to a few phrases.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"ibiza" <lambertb@.gmail.com> wrote in message
news:1143825609.907248.76110@.t31g2000cwb.googlegro ups.com...
> Hi all,
> I am quite experimented with SQL Server, but not that much with full
> text indexing. After some successful attempts with english fields, I've
> decided to try it with Japanese characters. I don't know why, but it
> seems to have a strange behaviour.
>
> As in this screenshot
> (http://img65.imageshack.us/img65/980/jap3xt.gif), the CONTAINS
> function does not seem to return only fields with an exact word match
> of the given "word" (query), but also strange results which does not
> even correspond to the query. Can anybody help me with that one?
>
> Thanks!
>
> ibiza
>
|||Hi,
thanks a lot for your reply
Well, even if I am not "fluent" in Japanese, I can still read japanese
"hiragana" characters, that is, what my query is about.
Each symbol can be translated as a syllable, so =E3=81=8A=E3=82=82=E3=81=97=
=E3=82=8D (the
query) would be "omoshiro", "o-mo-shi-ro".
The three first rows are translated as "omoni", "omo" and "omoi". So
I'm wondering why these results are showing, because they only partly
contains the query word (the =E3=81=8A=E3=82=82 ("omo") part)
As far as I know Japanese and full text indexing, the query should only
return results where the full and comple quey is found (=E3=81=8A=E3=82=82=
=E3=81=97=E3=82=8D),
as I did a CONTAINS search with a whole word.
Can you help me a little more with that information?
thanks again
ibiza
|||This could be by design. For example in German a word like wanderlust is
broken as wardern, lust and wanderlist. So if you were to do a contains
query for wanderlust you would get hits to any of these words. It looks like
it is doing something similar.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"ibiza" <lambertb@.gmail.com> wrote in message
news:1143922571.663177.238920@.i39g2000cwa.googlegr oups.com...
Hi,
thanks a lot for your reply
Well, even if I am not "fluent" in Japanese, I can still read japanese
"hiragana" characters, that is, what my query is about.
Each symbol can be translated as a syllable, so ? (the
query) would be "omoshiro", "o-mo-shi-ro".
The three first rows are translated as "omoni", "omo" and "omoi". So
I'm wondering why these results are showing, because they only partly
contains the query word (the ? ("omo") part)
As far as I know Japanese and full text indexing, the query should only
return results where the full and comple quey is found (?),
as I did a CONTAINS search with a whole word.
Can you help me a little more with that information?
thanks again
ibiza
|||Hi there,
thanks again for your reply.
I did some other tests with english and they all seemed successful
until this one :
http://img155.imageshack.us/img155/2001/untitled1tx.gif
Why is the CONTAINS returning no row at all? ;_;
This makes me doubt about the validity of all the previous succesful
queries I made...Could there be missing words, if some queries like the
one with 'now' isn't returning any at all?
What's the problem with full text indexing? :S
And yes I did repopulate all the indexes before running this query...
thanks for your help!
ibiza

Full text indexing with Japanese characters problem

Hi all,
I am quite experimented with SQL Server, but not that much with full
text indexing. After some successful attempts with english fields, I've
decided to try it with Japanese characters. I don't know why, but it
seems to have a strange behaviour.
As in this screenshot
(http://img65.imageshack.us/img65/980/jap3xt.gif), the CONTAINS
function does not seem to return only fields with an exact word match
of the given "word" (query), but also strange results which does not
even correspond to the query. Can anybody help me with that one?
Thanks!
ibizaI'm not sure about your problem, but could I have a copy of your DB?
That looks amazingly interesting I love japanese ^_^|||well, if you can help me with that problem, I'd be glad to consider it

(be warned though, it's more than 500MB in size...)
But seriously, I really don't understand why is the full-text indexing
service getting me those "almost random" rows where the dic_kana column
does not contain an exact match...yes, both the query and most of the
returned rows stard with "=E3=81=8A=E3=82=82", but that's the only resembla=
nce I
can find...
please help!
thanks
ibiza|||well, if you can help me with that problem, I'd be glad to consider it

(be warned though, it's more than 500MB in size...)
But seriously, I really don't understand why is the full-text indexing
service getting me those "almost random" rows where the dic_kana column
does not contain an exact match...yes, both the query and most of the
returned rows stard with "=E3=81=8A=E3=82=82", but that's the only resembla=
nce I
can find...
someone please help!
thanks
ibiza|||Does text indexing support non-latin characters?|||Hi again,
I did some other tests with english this time, and they all seemed
successful...until this one :
http://img155.imageshack.us/img155/2001/untitled1tx.gif
Why is the CONTAINS returning no row at all' ;_;
This makes me doubt about the validity of all the previous succesful
queries I made...Could there be missing words, if some queries like the
one with 'now' isn't returning any at all?
What's the problem with full text indexing? :S
And yes I did repopulate all the indexes before running this query...
help would be greatly appreciated!
thanks
ibiza

Full text indexing with Japanese characters problem

Hi all,
I am quite experimented with SQL Server, but not that much with full
text indexing. After some successful attempts with english fields, I've
decided to try it with Japanese characters. I don't know why, but it
seems to have a strange behaviour.
As in this screenshot
(http://img65.imageshack.us/img65/980/jap3xt.gif), the CONTAINS
function does not seem to return only fields with an exact word match
of the given "word" (query), but also strange results which does not
even correspond to the query. Can anybody help me with that one?
Thanks! :)
ibizaI'm not sure about your problem, but could I have a copy of your DB?
That looks amazingly interesting :) I love japanese ^_^|||well, if you can help me with that problem, I'd be glad to consider it
:)
(be warned though, it's more than 500MB in size...)
But seriously, I really don't understand why is the full-text indexing
service getting me those "almost random" rows where the dic_kana column
does not contain an exact match...yes, both the query and most of the
returned rows stard with "=E3=81=8A=E3=82=82", but that's the only resembla=nce I
can find...
please help!
thanks :)
ibiza|||well, if you can help me with that problem, I'd be glad to consider it
:)
(be warned though, it's more than 500MB in size...)
But seriously, I really don't understand why is the full-text indexing
service getting me those "almost random" rows where the dic_kana column
does not contain an exact match...yes, both the query and most of the
returned rows stard with "=E3=81=8A=E3=82=82", but that's the only resembla=nce I
can find...
someone please help!
thanks :)
ibiza|||Does text indexing support non-latin characters?|||Hi again,
I did some other tests with english this time, and they all seemed
successful...until this one :
http://img155.imageshack.us/img155/2001/untitled1tx.gif
Why is the CONTAINS returning no row at all' ;_;
This makes me doubt about the validity of all the previous succesful
queries I made...Could there be missing words, if some queries like the
one with 'now' isn't returning any at all?
What's the problem with full text indexing? :S
And yes I did repopulate all the indexes before running this query...
help would be greatly appreciated!
thanks
ibiza

Full text indexing with Japanese characters problem

Hi all,
I am quite experimented with SQL Server, but not that much with full
text indexing. After some successful attempts with english fields, I've
decided to try it with Japanese characters. I don't know why, but it
seems to have a strange behaviour.
As in this screenshot
(http://img65.imageshack.us/img65/980/jap3xt.gif), the CONTAINS
function does not seem to return only fields with an exact word match
of the given "word" (query), but also strange results which does not
even correspond to the query. Can anybody help me with that one?
Thanks! :)
ibizaHi again,
I did some other tests with english this time, and they all seemed
successful...until this one :
http://img155.imageshack.us/img155/2001/untitled1tx.gif
Why is the CONTAINS returning no row at all' ;_;
This makes me doubt about the validity of all the previous succesful
queries I made...Could there be missing words, if some queries like the
one with 'now' isn't returning any at all?
What's the problem with full text indexing? :S
And yes I did repopulate all the indexes before running this query...
help would be greatly appreciated!
thanks
ibiza

Full text indexing with Japanese characters problem

Hi all,

I am quite experimented with SQL Server, but not that much with full
text indexing. After some successful attempts with english fields, I've
decided to try it with Japanese characters. I don't know why, but it
seems to have a strange behaviour.

As in this screenshot
(http://img65.imageshack.us/img65/980/jap3xt.gif), the CONTAINS
function does not seem to return only fields with an exact word match
of the given "word" (query), but also strange results which does not
even correspond to the query. Can anybody help me with that one?

Thanks! :)

ibizaI'm not sure about your problem, but could I have a copy of your DB?
That looks amazingly interesting :) I love japanese ^_^|||well, if you can help me with that problem, I'd be glad to consider it
:)
(be warned though, it's more than 500MB in size...)

But seriously, I really don't understand why is the full-text indexing
service getting me those "almost random" rows where the dic_kana column
does not contain an exact match...yes, both the query and most of the
returned rows stard with "おも", but that's the only resemblance I
can find...

please help!

thanks :)
ibiza|||well, if you can help me with that problem, I'd be glad to consider it
:)
(be warned though, it's more than 500MB in size...)

But seriously, I really don't understand why is the full-text indexing
service getting me those "almost random" rows where the dic_kana column
does not contain an exact match...yes, both the query and most of the
returned rows stard with "おも", but that's the only resemblance I
can find...

someone please help!

thanks :)
ibiza|||Does text indexing support non-latin characters?|||Hi again,

I did some other tests with english this time, and they all seemed
successful...until this one :
http://img155.imageshack.us/img155/2001/untitled1tx.gif

Why is the CONTAINS returning no row at all?? ;_;
This makes me doubt about the validity of all the previous succesful
queries I made...Could there be missing words, if some queries like the
one with 'now' isn't returning any at all?

What's the problem with full text indexing? :S

And yes I did repopulate all the indexes before running this query...

help would be greatly appreciated!
thanks

ibiza