April 28, 2008 at 1:05 pm
we have a database that we dump security logs into and i have some sp's on it for reporting purposes
made a new one today and it takes seconds to return a few rows when running it on the server through terminal services. 10 minutes later the same procedure is slow on the server and via management studio and reporting services.
noticed this before when i do a full text query. sometimes it flies, and other times the same query is like watching grass grow
May 1, 2008 at 9:12 pm
I have also run into something strange - not attributing it to the full-text indexing but now wondering ...
I addes new statistical columns and new indices as recommended by DTA and checked to make sure they were ok. Last two night there is a process in a batch job that normally takes 12 minuest to complete - now blows it out by 5 hrs!
I have restored the dbs concerned and tried to replicate the problem on another machine without having full-text indexing the th epoint between running the job before making the changes and after the difference is only less than a minute - worse after I have added the new stuuf - which I expected as the new stats and indices are geared for dayligh operations.
Tonight I am going to remove what I have done 3 nights ago - hoping to return the batch job back.
Now because I wondering about the full text indexing - will doing this make any difference?
I also know that there is a process - killed about a month ago - which is still in rollback status which was doing a full text index update.
Would this be affecting this batch job?
Comments>?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply