FTI population: Locking issue shutting down Full-Text Index population

We are implementing FTI on a Linguistic SQL Server Database for performance improvement. The maximum size of database is 20 GB and there are 27 million records in the table on which we are implementing FTI. When We did a small POC with 1.2 million records, the FTI worked fine. But now with 27 million records it' giving the error messages attached in the event logs below.

It looks like the system resources are insufficient for completing the FTI population, but can I pinpoint what is causing problem from the overall system? Can we make some firm conclusions by looking at the attached event logs?

FYI: the free disc space on which the FTI catalogs are kept is 55GB. The SQL Server configuration is 4 processors, 4GB RAM.

Any help in this regard is greatly appreciated. ThanksHi There,

You could always split the process by /8 or /16 different tables and then move them to the new location systematically and not all at one time.

(ISQL/W : Select percentage 25% from blah ...?)

From Query parameters slows query

I went from having no "From Query" parameters to having about twenty, should
this degrade the performance of the query... It sits and spins for quite
awhile longer now than before.. What exactly is it doing to get these
parameters populated with data...? It's taking about 15 times longer to run
the query with the parameters as opposed to running without...
Any ideas...?Not sure what you mean. Adding additional parameters to the where clause
should not increase query time, in fact it should generally decrease it. If
you are saying that you are retrieving valid value lists for 20 parameters,
then yes, overall report execution time will decrease. You are doing quite a
bit more work than before.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"alien2_51" <dan.billow"at"n.o.s.p.a.m.monacocoach.commercialversion> wrote
in message news:uox%23mLmfEHA.3320@.TK2MSFTNGP11.phx.gbl...
>I went from having no "From Query" parameters to having about twenty,
>should
> this degrade the performance of the query... It sits and spins for quite
> awhile longer now than before.. What exactly is it doing to get these
> parameters populated with data...? It's taking about 15 times longer to
> run
> the query with the parameters as opposed to running without...
> Any ideas...?
>|||In the Report->Report Parameters property page there are two types of
parameters Non-Queried and From Query. Non-Queried appears to prompt the
user for its value while the From Query parameter appears to be populated
from the query as it's name implies by assigning a column from the dataset.
I've created several of these type of parameters because I need a way to
have a page header with data from the query repeat on every page since I
cannot put Fields in the page header and using a table with the
repeatonnewpage doesn't seem to work this was my only viable solution. If
you look at my posts for the last couple days you'll get an idea of what I'm
trying to do. So my question remains why would creating From Query
parameters slow the execution of my report...? Am I using them incorrectly
is there another direction I can take to to achieve my goal...
Thanks,
Dan
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
news:OA1O%236pfEHA.3548@.TK2MSFTNGP09.phx.gbl...
> Not sure what you mean. Adding additional parameters to the where clause
> should not increase query time, in fact it should generally decrease it.
If
> you are saying that you are retrieving valid value lists for 20
parameters,
> then yes, overall report execution time will decrease. You are doing quite
a
> bit more work than before.
> --
> Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "alien2_51" <dan.billow"at"n.o.s.p.a.m.monacocoach.commercialversion>
wrote
> in message news:uox%23mLmfEHA.3320@.TK2MSFTNGP11.phx.gbl...
> >I went from having no "From Query" parameters to having about twenty,
> >should
> > this degrade the performance of the query... It sits and spins for quite
> > awhile longer now than before.. What exactly is it doing to get these
> > parameters populated with data...? It's taking about 15 times longer to
> > run
> > the query with the parameters as opposed to running without...
> >
> > Any ideas...?
> >
> >
>

freeze display in Perfmon ?

Is the freeze display in Perfmon similar to pausing or stopping and starting
again. Are there any performance issues to freezing the display or should i
close the perfmon if i dont need to.
I have some counters that i would like to store and be able to run perfmon
any time with these set of counters rather than adding them every time i
open perfmon How can i do so ?Hassan
Use this link to see lots of tips for using perfmon
including how to store settings.
http://www.sql-server-
performance.com/performance_monitor_tips.asp
Hope this helps
John