Viewing 15 posts - 241 through 255 (of 2,488 total)
Hmmm ... ok I'm out of ideas. Looks like you've tried all the avenues I can think off.
I'd say the next step would be a support call to MS --------------------
Colt 45 - the original point and click interface ![]()
July 16, 2007 at 6:36 am
Ok, with that server setup you shouldn't run into any of the limitations imposed on the lower editions.
When you try to start them manually is this done via EM, or...
--------------------
Colt 45 - the original point and click interface ![]()
July 16, 2007 at 6:25 am
Strange.
Couple of things that should have been covered up front. What OS and SQL version are you running?
Are these jobs scheduled, or are you manually starting all of them?
--------------------
Colt 45 - the original point and click interface ![]()
July 14, 2007 at 2:36 am
Take a look at the Qn in this article about Concurrent Sql Server Agent Jobs
--------------------
Colt 45 - the original point and click interface ![]()
July 13, 2007 at 10:07 am
Don't follow contrived "best practice" if it doesn't suit your business requirements. In the document referenced by Alzdba, under the heading "Test Methodology", they basically admit to cooking the tests...
--------------------
Colt 45 - the original point and click interface ![]()
July 10, 2007 at 3:41 am
The magic number is 9.
Put this link in your favourites ![]()
--------------------
Colt 45 - the original point and click interface ![]()
July 8, 2007 at 5:16 pm
Glad you found a solution that worked for you. Just be aware that the sp_OA* procedures used in that article are notrious for memory leaks.
--------------------
Colt 45 - the original point and click interface ![]()
July 7, 2007 at 9:03 pm
Why would you be using an ExecuteSQL task? If you've defined the connections, then just add a datapump between them.
If you're stuck on using the ExecuteSQL task then you'll need...
--------------------
Colt 45 - the original point and click interface ![]()
July 5, 2007 at 6:32 pm
Another option for email is XPSMTP available from http://www.sqldev.net
--------------------
Colt 45 - the original point and click interface ![]()
July 5, 2007 at 6:24 pm
For the data driven query, have you specified both the insert and update statements?
Is there a specific reason why you can't pump the data to the source and the run...
--------------------
Colt 45 - the original point and click interface ![]()
July 5, 2007 at 6:23 pm
At a guess I'd say that the profile that the DTS package is running under doesn't contain the INI file setting in it's environment.
How about just passing the INI file...
--------------------
Colt 45 - the original point and click interface ![]()
July 5, 2007 at 6:20 pm
The SQL Statement you execute in DTS won't know about the connections defined within the package.
Best way to do this would be to have a Datapump task transfer the data...
--------------------
Colt 45 - the original point and click interface ![]()
July 4, 2007 at 6:04 pm
Execution plan would also be useful ![]()
--------------------
Colt 45 - the original point and click interface ![]()
July 2, 2007 at 11:23 pm
Why would you go to all this trouble? Just setup Database Mail instead it uses SMTP.
--------------------
Colt 45 - the original point and click interface ![]()
July 2, 2007 at 11:19 pm
You'd just compress the file before attaching it. There are a number of command-line compression tools. One we've used extensively is GZip (www.gzip.org).
--------------------
Colt 45 - the original point and click interface ![]()
July 2, 2007 at 5:24 pm
Viewing 15 posts - 241 through 255 (of 2,488 total)