sql server dts: Searching tables after DTS-job is very slow -- sql server dts

Re: Searching tables after DTS-job is very slow

Kevin3NF
9/29/2003 10:43:57 AM

sql server dts:

If you delete all the data and refill the tables, you ned to rebuild the
indexes too.

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/Newsgroups

[quoted text, click to view]

Searching tables after DTS-job is very slow

Tore Gylver
9/29/2003 5:03:00 PM

I have a couple of read-only tables that are modified once per week by a DTS
job. I delete all the records (delete <tablename>) and I use DTS datapump to
read fresh data from external sources into the tables. Then I let DTS run
several stored procedures to update the data. One table has 1,2 million
records, the other about 7000.

Searches in the tables are done from a client implemented in Microsoft
Access Project (.adp file).
The problem is that the response time is so long after the DTS-job is run.
In some cases the initial search following a DTS-job may time out after 30
seconds with no response.
Then the response time seems to improve as the client manage to run simpler
and successful searches in the tables.

Will indexes be corrupted after a DTS job?
How can I let the DTS-job fix this? Should I run "dbcc dbreindex" on my
tables?
The indexes have been created using the Profiler tool and no changes are
programmed into the DTS-job.

Regards

Tore