Viewing 13 posts - 1 through 13 (of 13 total)
I am connecting in both EM and QA using the same NT account so that is not an issue.
From EM the DTS package runs on the local machine and from...
March 18, 2004 at 9:36 am
No, I use the Pull UNC name to grab the file. It executes under the context of an SA account. One more thing it executes when executed from the Enterprise...
March 18, 2004 at 6:22 am
It is able to run dtsrun.exe as the first step in the package finishes successfully if you see the o/p I attached. The second step which copies the data from...
March 17, 2004 at 9:15 am
It works under my security context, which means there is nothing wrong with the file or the packge. I am a sa on the server. There is something else which is...
March 17, 2004 at 8:36 am
Thanks a lot stewart. This worked
March 4, 2004 at 3:16 am
Yes she has same sort of access to these resources. I have just created a similar package on her machine using the wizard and executed it successfully.
After that when I...
March 3, 2004 at 10:37 am
The CPU usage has come down to normal levels now between 20-40%.
There were a few areas which were particularly very slow and all these were using temp tables in...
October 7, 2003 at 2:33 am
quote:
quote:
From glively: If you are getting a lot of inserts and updates, make sure...
September 30, 2003 at 3:21 am
quote:
You should be able to figure out which user/sql-process is consuming cpu by looking at the cpu columns of sysprocesses. From the...
September 26, 2003 at 8:15 am
Hi,
It doesn't appear to be a I/O bottleneck currently but from the link you have sent it definitely appears to be a CPU bottle neck. Context Switches/Sec is 9089(Average) when...
September 26, 2003 at 3:37 am
Dear Ray,
Thanks for the response. Isn't only SQL2000 impacted by slammer worm. We are on SQL7 aon service pack 6.
September 26, 2003 at 2:28 am
Have you tried to upadte database statistics? Can you also look the performance in I/O? You need also start Profiler to see how queries performed in SQL Server.
No havn't updated...
September 25, 2003 at 9:27 am
It is because of the SQLServer.exe process. It is taking all the cpu.
September 25, 2003 at 8:29 am
Viewing 13 posts - 1 through 13 (of 13 total)