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
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. -- 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 "dvc" wrote in message news:25EB86A7-9FEF-43E1-B404-618217B944F4@microsoft.com... >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, 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 "Hilary Cotter" wrote: > 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. > > > -- > 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 > > "dvc" wrote in message > news:25EB86A7-9FEF-43E1-B404-618217B944F4@microsoft.com... > >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 > > > > > > >
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/7c06fb365e79973f?dmode=source "dvc" wrote in message news:ACEA8514-7A7C-4F36-9F5F-C86A0C6008E6@microsoft.com... > 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 > > "Hilary Cotter" wrote: > >> 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. >> >> >> -- >> 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 >> >> "dvc" wrote in message >> news:25EB86A7-9FEF-43E1-B404-618217B944F4@microsoft.com... >> >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, thank you again for this reference. "Hilary Cotter" wrote: > 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/7c06fb365e79973f?dmode=source > > > "dvc" wrote in message > news:ACEA8514-7A7C-4F36-9F5F-C86A0C6008E6@microsoft.com... > > 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 > > > > "Hilary Cotter" wrote: > > > >> 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. > >> > >> > >> -- > >> 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 > >> > >> "dvc" wrote in message > >> news:25EB86A7-9FEF-43E1-B404-618217B944F4@microsoft.com... > >> >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 > >> > > >> > > >> > >> > >> > > >
