create fulltext index
-
Friday, May 18, 2012 5:06 PM
I generated a database script in QA and Production:
Production (SQL Server 10.50.1600) -------------------------------------
CREATE FULLTEXT CATALOG [ft] WITH ACCENT_SENSITIVITY = ON
AS DEFAULT AUTHORIZATION [TracKRSBulletinAdmin]
GOCREATE FULLTEXT INDEX ON [dbo].[Units](
[UnitName] LANGUAGE [English])
KEY INDEX [pk_units]ON ([ft], FILEGROUP [PRIMARY])
WITH (CHANGE_TRACKING = AUTO, STOPLIST = SYSTEM)
GOQA ( SQL Server 9.0.5057 )
---------------------------------------
CREATE FULLTEXT CATALOG [ft]
WITH ACCENT_SENSITIVITY = ON
AS DEFAULT
AUTHORIZATION [dbo]
GOCREATE FULLTEXT INDEX ON [dbo].[Units](
[UnitName] LANGUAGE [English])
KEY INDEX [pk_units] ON [ft]
WITH CHANGE_TRACKING AUTO
GODoes the (1)DEFAULT AUTHORIZATION [TracKRSBulletinAdmin ] vs DEFAULT AUTHORIZATION [ dbo ], (2) "filegroup" and, (3) "stoplist = system" in the fulltext-index cause the same query to have different turnaround time in production and QA?
Thanks!
- Edited by tinac99 Friday, May 18, 2012 5:25 PM
All Replies
-
Monday, May 21, 2012 5:19 AMModerator
Hi tinac99,
It cannot be guaranteed to have same time consumed with the same query issued on different servers, even with same DDL structures. The server capacity, workload, and data might differ between them. The options here are not the problem leading to different time used in full text search query.
For your reference:
Improving SQL Server full-text search performance
SQL Server Full-Text Search Performance Tuning and Optimization
Stephanie Lv
TechNet Community Support
- Marked As Answer by Stephanie LvModerator Monday, May 28, 2012 8:24 AM

