|
|
You're in the
sql server full text search
group:performance problem...
sql server full text search:
Could you post the full output of the below SQL code as this information is very helpful in troubleshooting SQL FTS issues? use <your_database_name> select @@version select @@language select count(*) from your_FT-enabled_table_name If you're are using SQL Server 2000, does your FT-enable table have "Change Tracking" with "Update Index in Background" enabled or are you using a frequently scheduled Incremental Population? Depending upon the size of your table and if you're using SQL 2000, it might be best to use CT with UIiB. Also, could you provide information on where your FT Catalog folder is (what drive and type of drive, i.e., RAID level) relative to your database files (*.mdf & *.ldf)? Thanks, John -- SQL Full Text Search Blog http://spaces.msn.com/members/jtkane/ [quoted text, click to view] "Simon Steiner" <anybody@anonymous.com> wrote in message news:egYJaMdFFHA.228@TK2MSFTNGP15.phx.gbl... > hello ng > > i've got a problem with my fulltext-index, or with the performance of the > sql-server. > in one database i've installed a fulltext-index. this index based on a often > scheduled job, because it's nessessary to find the entrys directly after the > insert. the schedule has a frequence of 1 minute... > > on the same sql-server i've got an other database. in this db i like to > insert many entrys on the same time. > > the index works and the other db works too. but the inserts are very slow > when i start the index-job. the sql-server runs on a 4 processor system with > 2gb of memory, and the processor has more capacity than i use (max 20%). the > harddisk is also very fast (scsi). > > inserts per second: up to 300 > inserts per secon with index running: up to 40 > > what can i do to run both things on same time? > do i have to change some settings for the index-job? > > thanx. simon > >
hello ng
i've got a problem with my fulltext-index, or with the performance of the sql-server. in one database i've installed a fulltext-index. this index based on a often scheduled job, because it's nessessary to find the entrys directly after the insert. the schedule has a frequence of 1 minute... on the same sql-server i've got an other database. in this db i like to insert many entrys on the same time. the index works and the other db works too. but the inserts are very slow when i start the index-job. the sql-server runs on a 4 processor system with 2gb of memory, and the processor has more capacity than i use (max 20%). the harddisk is also very fast (scsi). inserts per second: up to 300 inserts per secon with index running: up to 40 what can i do to run both things on same time? do i have to change some settings for the index-job? thanx. simon
Here's the Output from SQL:
version: Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: ) language: us_english row_count: 10137 The catalog is placed on "D:\Program Files\Microsoft SQL Server\MSSQL\FTDATA" on the same disk like the Server is running... The size of the catalog is 6MB I'm using a frequently scheduled Incremental Population. Could that be a reason to switch to "Update Index in Background"? Simon "John Kane" <jt-kane@comcast.net> schrieb im Newsbeitrag news:ucYBJXdFFHA.2832@TK2MSFTNGP14.phx.gbl... [quoted text, click to view] > Simon, > Could you post the full output of the below SQL code as this information is > very helpful in troubleshooting SQL FTS issues? > > use <your_database_name> > select @@version > select @@language > select count(*) from your_FT-enabled_table_name > > If you're are using SQL Server 2000, does your FT-enable table have "Change > Tracking" with "Update Index in Background" enabled or are you using a > frequently scheduled Incremental Population? Depending upon the size of your > table and if you're using SQL 2000, it might be best to use CT with UIiB. > Also, could you provide information on where your FT Catalog folder is (what > drive and type of drive, i.e., RAID level) relative to your database files > (*.mdf & *.ldf)? > > Thanks, > John > -- > SQL Full Text Search Blog > http://spaces.msn.com/members/jtkane/ > > > > "Simon Steiner" <anybody@anonymous.com> wrote in message > news:egYJaMdFFHA.228@TK2MSFTNGP15.phx.gbl... > > hello ng > > > > i've got a problem with my fulltext-index, or with the performance of the > > sql-server. > > in one database i've installed a fulltext-index. this index based on a > often > > scheduled job, because it's nessessary to find the entrys directly after > the > > insert. the schedule has a frequence of 1 minute... > > > > on the same sql-server i've got an other database. in this db i like to > > insert many entrys on the same time. > > > > the index works and the other db works too. but the inserts are very slow > > when i start the index-job. the sql-server runs on a 4 processor system > with > > 2gb of memory, and the processor has more capacity than i use (max 20%). > the > > harddisk is also very fast (scsi). > > > > inserts per second: up to 300 > > inserts per secon with index running: up to 40 > > > > what can i do to run both things on same time? > > do i have to change some settings for the index-job? > > > > thanx. simon > > > > > >
uups.
The Size of the *.ldf-file ist: 235MB and the *.mdf has 27.9MB The HD-Type is a seagate scsi drive and there is a RAID0 installed... so there are 2 disks. simon "John Kane" <jt-kane@comcast.net> schrieb im Newsbeitrag news:ucYBJXdFFHA.2832@TK2MSFTNGP14.phx.gbl... [quoted text, click to view] > Simon, > Could you post the full output of the below SQL code as this information is > very helpful in troubleshooting SQL FTS issues? > > use <your_database_name> > select @@version > select @@language > select count(*) from your_FT-enabled_table_name > > If you're are using SQL Server 2000, does your FT-enable table have "Change > Tracking" with "Update Index in Background" enabled or are you using a > frequently scheduled Incremental Population? Depending upon the size of your > table and if you're using SQL 2000, it might be best to use CT with UIiB. > Also, could you provide information on where your FT Catalog folder is (what > drive and type of drive, i.e., RAID level) relative to your database files > (*.mdf & *.ldf)? > > Thanks, > John > -- > SQL Full Text Search Blog > http://spaces.msn.com/members/jtkane/ > > > > "Simon Steiner" <anybody@anonymous.com> wrote in message > news:egYJaMdFFHA.228@TK2MSFTNGP15.phx.gbl... > > hello ng > > > > i've got a problem with my fulltext-index, or with the performance of the > > sql-server. > > in one database i've installed a fulltext-index. this index based on a > often > > scheduled job, because it's nessessary to find the entrys directly after > the > > insert. the schedule has a frequence of 1 minute... > > > > on the same sql-server i've got an other database. in this db i like to > > insert many entrys on the same time. > > > > the index works and the other db works too. but the inserts are very slow > > when i start the index-job. the sql-server runs on a 4 processor system > with > > 2gb of memory, and the processor has more capacity than i use (max 20%). > the > > harddisk is also very fast (scsi). > > > > inserts per second: up to 300 > > inserts per secon with index running: up to 40 > > > > what can i do to run both things on same time? > > do i have to change some settings for the index-job? > > > > thanx. simon > > > > > >
Thanks, Simon,
Q. Could that be a reason to switch to "Update Index in Background"? A. Yes! As you're using SQL 2000 SP3 on Win2003, you can enable CT with UIiB and disenable or delete your frequently running Incremental Population job and I'd highly recommend this. Additionally, you should drop and re-create the FT Catalog and re-create it on your server's non-system disk drive (usually c:\) and separate from your database files. So, if you have another drive, say the E:\ and your databases are on the D:\ (where SQL Server is installed), I'd put the FT Catalog on the E:\ drive assuming it is the RAID0 drive. The primary reason for this is to avoid the read/write I/O contention between the FT Catalog and the database files during FT Indexing. Hope that helps, John -- SQL Full Text Search Blog http://spaces.msn.com/members/jtkane/ [quoted text, click to view] "Simon Steiner" <anybody@anonymous.com> wrote in message news:OI9NUqdFFHA.3908@TK2MSFTNGP12.phx.gbl... > uups. > The Size of the *.ldf-file ist: 235MB and the *.mdf has 27.9MB > > The HD-Type is a seagate scsi drive and there is a RAID0 installed... so > there are 2 disks. > > simon > > > "John Kane" <jt-kane@comcast.net> schrieb im Newsbeitrag > news:ucYBJXdFFHA.2832@TK2MSFTNGP14.phx.gbl... > > Simon, > > Could you post the full output of the below SQL code as this information > is > > very helpful in troubleshooting SQL FTS issues? > > > > use <your_database_name> > > select @@version > > select @@language > > select count(*) from your_FT-enabled_table_name > > > > If you're are using SQL Server 2000, does your FT-enable table have > "Change > > Tracking" with "Update Index in Background" enabled or are you using a > > frequently scheduled Incremental Population? Depending upon the size of > your > > table and if you're using SQL 2000, it might be best to use CT with UIiB. > > Also, could you provide information on where your FT Catalog folder is > (what > > drive and type of drive, i.e., RAID level) relative to your database files > > (*.mdf & *.ldf)? > > > > Thanks, > > John > > -- > > SQL Full Text Search Blog > > http://spaces.msn.com/members/jtkane/ > > > > > > > > "Simon Steiner" <anybody@anonymous.com> wrote in message > > news:egYJaMdFFHA.228@TK2MSFTNGP15.phx.gbl... > > > hello ng > > > > > > i've got a problem with my fulltext-index, or with the performance of > the > > > sql-server. > > > in one database i've installed a fulltext-index. this index based on a > > often > > > scheduled job, because it's nessessary to find the entrys directly after > > the > > > insert. the schedule has a frequence of 1 minute... > > > > > > on the same sql-server i've got an other database. in this db i like to > > > insert many entrys on the same time. > > > > > > the index works and the other db works too. but the inserts are very > slow > > > when i start the index-job. the sql-server runs on a 4 processor system > > with > > > 2gb of memory, and the processor has more capacity than i use (max 20%). > > the > > > harddisk is also very fast (scsi). > > > > > > inserts per second: up to 300 > > > inserts per secon with index running: up to 40 > > > > > > what can i do to run both things on same time? > > > do i have to change some settings for the index-job? > > > > > > thanx. simon > > > > > > > > > > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |