DTS PACKAGE NOT SCHEDULING

Hello,
Every time I schedule my DTS packages it goes back to the default. For some
reason it’s not scheduling @. all. Not receiving any error msgs. & It runs
fine manually. What can cause this?
Thanks for your help in advanced!
Thanks!
Nigel
Nigel
It looks like you create a DTS package with an account which is different
from an account that SQL Server Agent is running.
"Nigel" <Nigel@.discussions.microsoft.com> wrote in message
news:2130B2FD-76CB-4DE1-A2E5-9CE5F9A02FAA@.microsoft.com...
> Hello,
> Every time I schedule my DTS packages it goes back to the default. For
some
> reason its not scheduling @. all. Not receiving any error msgs. & It
runs
> fine manually. What can cause this?
> Thanks for your help in advanced!
> --
> Thanks!
> Nigel
|||Can it only run on the account SQL Server Agent is running on?
Cause I have admin rights to the account.
Thanks for your reply.
**********************************************
"Uri Dimant" wrote:

> Nigel
> It looks like you create a DTS package with an account which is different
> from an account that SQL Server Agent is running.
>
>
> "Nigel" <Nigel@.discussions.microsoft.com> wrote in message
> news:2130B2FD-76CB-4DE1-A2E5-9CE5F9A02FAA@.microsoft.com...
> some
> runs
>
>
|||You could just be running into a known display issue. After
you have scheduled the package, check the schedule through
the job under SQL Server Agent instead of through the
package. There is a problem where when checking the schedule
through the package, it will just always shows the default
date/time but this is just a display issue. The schedule
will be correct for the job itself.
The following article documents the issue:
BUG: DTS: Default Scheduling Information Displayed
http://support.microsoft.com/?id=221480
-Sue
On Tue, 5 Apr 2005 07:11:03 -0700, "Nigel"
<Nigel@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Can it only run on the account SQL Server Agent is running on?
>Cause I have admin rights to the account.
>Thanks for your reply.
>**********************************************
>"Uri Dimant" wrote:

DTS PACKAGE NOT SCHEDULING

Hello,
Every time I schedule my DTS packages it goes back to the default. For some
reason itâ's not scheduling @. all. Not receiving any error msgs. & It runs
fine manually. What can cause this?
Thanks for your help in advanced!
--
Thanks!
NigelNigel
It looks like you create a DTS package with an account which is different
from an account that SQL Server Agent is running.
"Nigel" <Nigel@.discussions.microsoft.com> wrote in message
news:2130B2FD-76CB-4DE1-A2E5-9CE5F9A02FAA@.microsoft.com...
> Hello,
> Every time I schedule my DTS packages it goes back to the default. For
some
> reason it?s not scheduling @. all. Not receiving any error msgs. & It
runs
> fine manually. What can cause this?
> Thanks for your help in advanced!
> --
> Thanks!
> Nigel|||Can it only run on the account SQL Server Agent is running on?
Cause I have admin rights to the account.
Thanks for your reply.
**********************************************
"Uri Dimant" wrote:
> Nigel
> It looks like you create a DTS package with an account which is different
> from an account that SQL Server Agent is running.
>
>
> "Nigel" <Nigel@.discussions.microsoft.com> wrote in message
> news:2130B2FD-76CB-4DE1-A2E5-9CE5F9A02FAA@.microsoft.com...
> > Hello,
> > Every time I schedule my DTS packages it goes back to the default. For
> some
> > reason itâ's not scheduling @. all. Not receiving any error msgs. & It
> runs
> > fine manually. What can cause this?
> >
> > Thanks for your help in advanced!
> >
> > --
> > Thanks!
> > Nigel
>
>|||You could just be running into a known display issue. After
you have scheduled the package, check the schedule through
the job under SQL Server Agent instead of through the
package. There is a problem where when checking the schedule
through the package, it will just always shows the default
date/time but this is just a display issue. The schedule
will be correct for the job itself.
The following article documents the issue:
BUG: DTS: Default Scheduling Information Displayed
http://support.microsoft.com/?id=221480
-Sue
On Tue, 5 Apr 2005 07:11:03 -0700, "Nigel"
<Nigel@.discussions.microsoft.com> wrote:
>Can it only run on the account SQL Server Agent is running on?
>Cause I have admin rights to the account.
>Thanks for your reply.
>**********************************************
>"Uri Dimant" wrote:
>> Nigel
>> It looks like you create a DTS package with an account which is different
>> from an account that SQL Server Agent is running.
>>
>>
>> "Nigel" <Nigel@.discussions.microsoft.com> wrote in message
>> news:2130B2FD-76CB-4DE1-A2E5-9CE5F9A02FAA@.microsoft.com...
>> > Hello,
>> > Every time I schedule my DTS packages it goes back to the default. For
>> some
>> > reason it?s not scheduling @. all. Not receiving any error msgs. & It
>> runs
>> > fine manually. What can cause this?
>> >
>> > Thanks for your help in advanced!
>> >
>> > --
>> > Thanks!
>> > Nigel
>>

DTS PACKAGE NOT SCHEDULING

Hello,
Every time I schedule my DTS packages it goes back to the default. For some
reason it’s not scheduling @. all. Not receiving any error msgs. & It run
s
fine manually. What can cause this?
Thanks for your help in advanced!
Thanks!
NigelNigel
It looks like you create a DTS package with an account which is different
from an account that SQL Server Agent is running.
"Nigel" <Nigel@.discussions.microsoft.com> wrote in message
news:2130B2FD-76CB-4DE1-A2E5-9CE5F9A02FAA@.microsoft.com...
> Hello,
> Every time I schedule my DTS packages it goes back to the default. For
some
> reason its not scheduling @. all. Not receiving any error msgs. & It
runs
> fine manually. What can cause this?
> Thanks for your help in advanced!
> --
> Thanks!
> Nigel|||Can it only run on the account SQL Server Agent is running on?
Cause I have admin rights to the account.
Thanks for your reply.
****************************************
******
"Uri Dimant" wrote:

> Nigel
> It looks like you create a DTS package with an account which is different
> from an account that SQL Server Agent is running.
>
>
> "Nigel" <Nigel@.discussions.microsoft.com> wrote in message
> news:2130B2FD-76CB-4DE1-A2E5-9CE5F9A02FAA@.microsoft.com...
> some
> runs
>
>|||You could just be running into a known display issue. After
you have scheduled the package, check the schedule through
the job under SQL Server Agent instead of through the
package. There is a problem where when checking the schedule
through the package, it will just always shows the default
date/time but this is just a display issue. The schedule
will be correct for the job itself.
The following article documents the issue:
BUG: DTS: Default Scheduling Information Displayed
http://support.microsoft.com/?id=221480
-Sue
On Tue, 5 Apr 2005 07:11:03 -0700, "Nigel"
<Nigel@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Can it only run on the account SQL Server Agent is running on?
>Cause I have admin rights to the account.
>Thanks for your reply.
> ****************************************
******
>"Uri Dimant" wrote:
>

DTS Looping

DTS Looping
Hi,
I have read articles on DTS looping http://www.sqldts.com/default.aspx?6,103,246,0,1 and a few others, but I still have a problem.

Trying to connect to different Interbase databases via Interbase ODBC driver.
-After connection, use a datapump to select data from db A
-Then loop, based on a global variable that holds the count/ID of the new database B to connect to.

Problem
-GLobal variable successfully getting updated with new branch details
-ODBC driver 'seems' to be switching to new branch db B
-But datapump goes to database A and tries to select the same data again it has done already.
-Loop fails. But if all steps run manually one by one the loop works i.e goes to A then goes to B.

HeeeEEEllLLLppppp !See Attached file for further details|||Hello,
Hoping somebody would have an idea on this one...
Please Help.|||Howdy

Not being a DTS coding expert, I'd suggest adding an extra step in the branch choosing VB script.

If its a timing issue, this will allow the correct value to appear where its supposed to be , ready for the next sweep of the reading program.

Cheers,

SG|||Thanks SG.
Never thought that it could be a timing issue. Will into this.
But found another article on dynamically changing connections in a DTS...
http://www.databasejournal.com/features/mssql/article.php/1461481
Maybe I have luck here.

Question:
Can one call a DTS Package from another DTS Package ?

Thanks again.

Originally posted by sqlguy7777
Howdy

Not being a DTS coding expert, I'd suggest adding an extra step in the branch choosing VB script.

If its a timing issue, this will allow the correct value to appear where its supposed to be , ready for the next sweep of the reading program.

Cheers,

SG|||Still Trying........SO GO ON Sql Experts.take a chance with this one !

Originally posted by bhandp
Thanks SG.
Never thought that it could be a timing issue. Will into this.
But found another article on dynamically changing connections in a DTS...
http://www.databasejournal.com/features/mssql/article.php/1461481
Maybe I have luck here.

Question:
Can one call a DTS Package from another DTS Package ?

Thanks again.|||Originally posted by bhandp
Still Trying........SO GO ON Sql Experts.take a chance with this one !

Are you resetting any database properties within the datapump task? This one quite often trips people up as DTS uses the fully qualified name of the table eg: database.owner.table|||Originally posted by phillcart
Are you resetting any database properties within the datapump task? This one quite often trips people up as DTS uses the fully qualified name of the table eg: database.owner.table

Hi Phill,
How can I give a fully qualified name of a table 'database.owner.table' within the datapump task when my database will change with every time it loops ?
Is there a possibility that, the first database the datapump connects to, remains stored in the datapump ? Here is the script the datapump uses, in its properties:

Function Main()
Dim oPkg, oDataPump, sSQLStatement
Dim FromDt
Dim ToDtLocal

'Assign global variable to local variable
FromDt = DTSGlobalVariables("FromDate").Value
ToDtLocal = DTSGlobalVariables("ToDtLocal").Value

' Build new SQL Statement

sSQLStatement = "SELECT all the fields here"
Where d.updDT >= '"& FromDt &"' " & _
"AND d.updDT < '"& ToDtLocal & "' "

' Get reference to the DataPump Task
Set oPkg = DTSGlobalVariables.Parent
Set oDataPump = oPkg.Tasks("DTSTask_DTSDataPumpTask_1").CustomTask

' Assign SQL Statement to Source of DataPump
oDataPump.SourceSQLStatement = sSQLStatement

' Clean Up
Set oDataPump = Nothing
Set oPkg = Nothing

Main = DTSStepScriptResult_ExecuteTask
End Function

Let me know what you think.
Thanks in advance. Thanks so muchly !
-Parul

DTS Looping

DTS Looping
Hi,
I have read articles on DTS looping http://www.sqldts.com/default.aspx?6,103,246,0,1 and a few others, but I still have a problem.

Trying to connect to different Interbase databases via Interbase ODBC driver.
-After connection, use a datapump to select data from db A
-Then loop, based on a global variable that holds the count/ID of the new database B to connect to.

Problem
-GLobal variable successfully getting updated with new branch details
-ODBC driver 'seems' to be switching to new branch db B
-But datapump goes to database A and tries to select the same data again it has done already.
-Loop fails. But if all steps run manually one by one the loop works i.e goes to A then goes to B.

HeeeEEEllLLLppppp !Hi,
Looks like I have had no luck in this, and nor has anybody else.
Calling all SQL server experts to take a look :)

DTS in SQL 2005

Not sure why Microsoft would remove from SQL 2005 DTS import data
sources all the default drivers available to ODBC but they did. In SQL
2000 the drivers available to ODBC were by default available to DTS
import. How does one go about getting DTS to recognize these drivers
so simple data import can be accomplished.
To import from a DBF file you now have to create an ODBC data source
Every time you want to add a new file and then to add insult to injury
they make you key in all the ODBC information for the import source
instead of giving you a simple drop down.
Seems like a huge step backwards as far as user interface goes.Hi
If I understood you correctly , you can run DTS (SS2000) from SS2005. There
is a folder called Legacy under Management folder.
<jmirsky@.hotmail.com> wrote in message
news:1139956308.785445.51930@.g43g2000cwa.googlegroups.com...
> Not sure why Microsoft would remove from SQL 2005 DTS import data
> sources all the default drivers available to ODBC but they did. In SQL
> 2000 the drivers available to ODBC were by default available to DTS
> import. How does one go about getting DTS to recognize these drivers
> so simple data import can be accomplished.
> To import from a DBF file you now have to create an ODBC data source
> Every time you want to add a new file and then to add insult to injury
> they make you key in all the ODBC information for the import source
> instead of giving you a simple drop down.
> Seems like a huge step backwards as far as user interface goes.
>

DTS in SQL 2005

Not sure why Microsoft would remove from SQL 2005 DTS import data
sources all the default drivers available to ODBC but they did. In SQL
2000 the drivers available to ODBC were by default available to DTS
import. How does one go about getting DTS to recognize these drivers
so simple data import can be accomplished.
To import from a DBF file you now have to create an ODBC data source
Every time you want to add a new file and then to add insult to injury
they make you key in all the ODBC information for the import source
instead of giving you a simple drop down.
Seems like a huge step backwards as far as user interface goes.
Hi
If I understood you correctly , you can run DTS (SS2000) from SS2005. There
is a folder called Legacy under Management folder.
<jmirsky@.hotmail.com> wrote in message
news:1139956308.785445.51930@.g43g2000cwa.googlegro ups.com...
> Not sure why Microsoft would remove from SQL 2005 DTS import data
> sources all the default drivers available to ODBC but they did. In SQL
> 2000 the drivers available to ODBC were by default available to DTS
> import. How does one go about getting DTS to recognize these drivers
> so simple data import can be accomplished.
> To import from a DBF file you now have to create an ODBC data source
> Every time you want to add a new file and then to add insult to injury
> they make you key in all the ODBC information for the import source
> instead of giving you a simple drop down.
> Seems like a huge step backwards as far as user interface goes.
>

DTS in SQL 2005

Not sure why Microsoft would remove from SQL 2005 DTS import data
sources all the default drivers available to ODBC but they did. In SQL
2000 the drivers available to ODBC were by default available to DTS
import. How does one go about getting DTS to recognize these drivers
so simple data import can be accomplished.
To import from a DBF file you now have to create an ODBC data source
Every time you want to add a new file and then to add insult to injury
they make you key in all the ODBC information for the import source
instead of giving you a simple drop down.
Seems like a huge step backwards as far as user interface goes.Hi
If I understood you correctly , you can run DTS (SS2000) from SS2005. There
is a folder called Legacy under Management folder.
<jmirsky@.hotmail.com> wrote in message
news:1139956308.785445.51930@.g43g2000cwa.googlegroups.com...
> Not sure why Microsoft would remove from SQL 2005 DTS import data
> sources all the default drivers available to ODBC but they did. In SQL
> 2000 the drivers available to ODBC were by default available to DTS
> import. How does one go about getting DTS to recognize these drivers
> so simple data import can be accomplished.
> To import from a DBF file you now have to create an ODBC data source
> Every time you want to add a new file and then to add insult to injury
> they make you key in all the ODBC information for the import source
> instead of giving you a simple drop down.
> Seems like a huge step backwards as far as user interface goes.
>