Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Performance issue?

Status
Not open for further replies.

MeganP

Programmer
Sep 23, 2004
18
US
HI all,
We have copied DTS packages from one SQL database on one server to another. New Server is more robust and has large memory. Other applications are running pretty fast on the server, But when I execute my SQL DTS packages, they are taking noticeably much longer comapring with old server. I checked table indexes and other server parameters. They all look fine.

What could be the reason? Can some one tell me what are all the things that I need to check on SQL SERVER side, please?

Note: Server has no issues!

Any help is greatly appreciated!

Thanks!
 
It could be any number of things that could be effecting the speed. What kinds of things is the package doing? It is moving data from one table to another, is it doing it in Large Batches, small batches, record by record, updates of huge tables, etc?

Some things to look are are CPU usage, memory usage, memory configuration, drive performance, drive configuration, disk queueing, blocks, locks, page file settings, CPU config in sql. I'll leave you with to start with.

Denny

--Anything is possible. All it takes is a little research. (Me)
 
Denny,
Thanks for your quick reply. Let me give you a little bigger picture.
Old server has Windows 2000 & SQL Server 2000; New one has Windows 2003 & SQL Server 2000. Complete configuration is exactly identical, except OS. How come a DTS package (Insert & Update)process time changes to that extent? (Used to take 1 hour on old server, Now it takes 2 hr 45 min)

Thanks!
 
If you are running on the same physical hardware, and that hardware is a little older, a slowdown of some sort is not out of the question. Windows 2003 does have a larger overhead than Windows 2000.

Run profiller while the package is running. That should help narrow down where the slow down is. If you are waiting for disk or for cpu. Those are usually the two biggest things that will slow you down.

Denny

--Anything is possible. All it takes is a little research. (Me)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top