Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 Import/Export (DTS) and Replication (2000)
 Dialog Box really, really, really slow

Author  Topic 

TexDec
Starting Member

22 Posts

Posted - 2002-06-19 : 18:18:41
In DTS I am trying to build a transformation to load data from a view into a table.
In the "Transform Data TAsk Properties" dialog boxeveything goes fine until I get to the "Trasformation" tab, then the whole thing grinds to a screeching halt. It eventually gets there, but I get the feeling that it is trying to scan evey row in my view, or some other crazyness.

Anyone seen this type of behaviour before? It's probably something stupid I've done in my setup. I'm still new to SQl Server

Declan K


The only Keane we need is Robbie

efelito
Constraint Violating Yak Guru

478 Posts

Posted - 2002-06-24 : 10:56:40
The transformation tab is generally slow to come up. It depends a lot on the number of fields in the source and destination tables. SQL Server is doing quite a few things to bring up the information on this tab. If it's the first time the tab is being brought up the server is getting metadata about both tables and I think it's even pulling some sample data from the source table. Then it makes assumptions on how you want things transformed. If you've already set transformations, it still pulls the metadata for both tables and verifies that all of the transformations are still valid.

Jeff Banschbach
Consultant, MCDBA
Go to Top of Page

MakeYourDaddyProud

184 Posts

Posted - 2002-06-24 : 11:18:50
DTS has a very large dynamic memory footprint for which there isn't much room for manoevre. One thing you might want to try is to set trace logs, profiler and try to pinpoint what is happening in SQL detail. DTS runs certain SPs to determine the workflow of your DTS application and draws a memory surge as a result. You might want to limit SQL servers memory usage although that is better as final resort.

I would bet there isn't much you can do about it if your queries run fine QA.

Dan

Go to Top of Page
   

- Advertisement -