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

SQL Server Forum / Other Technologies / Full-Text Search / April 2008

Tip: Looking for answers? Try searching our database.

Special Characters

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
dvc - 15 Apr 2008 17:34 GMT
A very simple question about the difference in behaviour between 2000 and
2005 fti:

the following search in a parts catalog works in SQLServer 2000

select count(1)
from dbo.partsdescription
where contains(*,'15"')

but returns Msg 7630 syntax error near '"' in the full-text search condition
'15"'

What exactly has changed to cause this error and is there a workaround?

Thank you for your help
Hilary Cotter - 17 Apr 2008 10:48 GMT
The parser was less strict in SQL 2000. It seems you have stumbled across a
sequence that works. The work around would be strip non-alphanumeric
characters from the end of your search string.

Signature

Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

>A very simple question about the difference in behaviour between 2000 and
> 2005 fti:
[quoted text clipped - 12 lines]
>
> Thank you for your help
dvc - 17 Apr 2008 11:39 GMT
Hilary, thank you for the reply - we already implement your suggested
workaround for most of our full-text searches and so will extend this to the
parts catalog. I guess I was also angling for a slightly more technical
account of how and where parser functionality has changed between 2000 and
2005, but thank you anyway!

dvc

> The parser was less strict in SQL 2000. It seems you have stumbled across a
> sequence that works. The work around would be strip non-alphanumeric
[quoted text clipped - 16 lines]
> >
> > Thank you for your help
Hilary Cotter - 17 Apr 2008 13:37 GMT
I don't have one unfortunately, however see this post for a reference to
other parser anomalies in SQL 2000:

http://groups.google.com/group/microsoft.public.sqlserver.fulltext/msg/7c06fb365
e79973f?dmode=source


> Hilary, thank you for the reply - we already implement your suggested
> workaround for most of our full-text searches and so will extend this to
[quoted text clipped - 27 lines]
>> >
>> > Thank you for your help
dvc - 17 Apr 2008 16:38 GMT
Hilary, thank you again for this reference.

> I don't have one unfortunately, however see this post for a reference to
> other parser anomalies in SQL 2000:
[quoted text clipped - 32 lines]
> >> >
> >> > Thank you for your help
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.