Viewing 10 posts - 1 through 10 (of 10 total)
Take the SQL statment that is taking forever to process and place it into the Query Analyzer. Execute the "estimated exection plan" and post the results.
September 13, 2006 at 9:10 pm
Check the location of the text file. If you used drive letters in the file name, the file was created from the server's perspective of where the drive letter is...
May 12, 2006 at 1:24 pm
I would be inclined to try something from the command line for something like this. It would look something like:
ISQL -SMyServer -E -Q"SELECT * FROM db.owner.MYTABLE" >> c:\temp\myfile.txt
Other options are...
May 12, 2006 at 1:18 pm
You can use an ActiveX task to build the query into a global variable and then use dynamic properties to assign it to the source side of a transformation. Using...
May 12, 2006 at 10:45 am
I agree with the other posters regarding the use of the /E option. The key to making this work is to remember the security context. In the case mentioned here,...
December 20, 2005 at 10:40 am
sounds to me like the environments in server A and server B are slightly different. Are you specifying the full filename including drive letter and path in your filename?
Do both...
February 6, 2004 at 10:10 am
If you want to do this from the command line, you can use the DTSRUN program. Set up the file name as a dynamic parameter in the package by using...
February 6, 2004 at 9:52 am
Could be a security problem. When DTS runs as a job, it runs on the server. You might open the package on the server and attempt to run it manually...
February 6, 2004 at 9:41 am
You might try turning package logging on and then run the job. The log should tell you where the package is hanging up. If it doesn't give an...
June 10, 2003 at 9:08 am
Viewing 10 posts - 1 through 10 (of 10 total)