Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Wirusiux
Starting Member
1 Post |
 Posted - 2011-11-21 : 02:27:20
|
| Hi everyone, first time poster here.in our company we have moved from SQL server 2005 to SQL server 2008 and Full text search is'nt working correctly anymore.There is text in table: "Vilniaus m. 4 PK".I search for this : "Vilniaus m. 4 PK" and in sql 2008 it doesn't find anything, while in 2005 there are no problems.How to make it work, that if i search for "Vilniaus m. 4 PK" in sql 2008 it would return "Vilniaus m. 4 PK" ?If i search only for "Vilniaus" then it is ok.I think there might be problems with "." and "4"I would be glad for any answers or hints. |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2011-11-21 : 03:04:58
|
| was it a migration? did you populate the full text catalog after migrating it?------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
 |
|
|
johntech
Yak Posting Veteran
51 Posts |
Posted - 2011-11-23 : 13:03:06
|
| Before 2008, full text search wasn’t inside the database – it wasn’t subject to things like transactions. Heck, it was more like Lucene where it lived outside on its own. Now, it’s stored inside data files and it’s subject to transactions. From what im hearing, blocking and locking is a completely new issue in 2008 FTS. There’s a big overhead involved with making it subject to transactions. In most environments, you don’t see full text being used for transactions. At StackOverflow, you’re doing heavy transactional activity on the same fields that you’re doing analytical, many-record selects. If you do a full text search on Revisions and you include a common keyword like, say, SQL, you’re going to match tens of thousands of records. When I look at the query plans for these, I’m seeing 50-100k reads. Doing that inside a table that’s also getting heavy inserts – boom, transactional disaster. We rely heavily on full-text search on stackoverflow.com, which worked amazingly well for us under SQL Server 2005. Looks like that’s no longer the case for SQL Server 2008, unfortunately.http://blog.stackoverflow.com/2008/11/sql-2008-full-text-search-problems/ |
|
|
|
|
|
|
|
|
Full text search works in 2008 sql differently