Hi all,
I am having problems querying a full-indexed table because of the sql list of noise words e.i "a","b","and", "take"...
People sugest that I should clean the txt file that contains the noise words. To me this isn't an option becasue I want to...
Hi there,
thanks for the sufggestion. I am currently using the table indexing and the transact predicates CONTAINS...
I also created a field in my table called "timestamp" and i gave it the timestamp datatype. I know this field will be required when an incremental indexing is done on...
Hi,
i have a large database and manuy fields I am searching through contain large chunks of text. Searching for specific words or set of words in these fields slows down my response time considerably despite the fact that all these fields are already indexed in my database. I also scheduled an...
Hi Jay,
ok, it took me a while to discover the check box which enables the job history details but thank you for putting me on the right track.
The reason the job is not running is that the path to source file is not found when i call it from a web application. Very tricky as it finds this...
Hi,
We have a large table and several fields are indexed. We also created a field called 'timestamp' used by the SQL database to refernce its indexing process.
We created a 'timestamp' field after the table had been already populated with a large volume of data.
Because I set the database to do...
Hi there,
I have a stored procedure that calls a DTS package.
I have designed the DTS package and its data source is a text file locaed on a map drive.
When I created the package a job with the same name has been created under the SQL Server Agent. I removed the scheduler for this job as I onl...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.