Hi all gurus
If I create a package and schedule it for jobs and then if i delete the
package and create a new package with same name. Then my job for old package
will run on new package which has name of old deleted package?
In my case my old job runs new package.
will it make any problem?
Thanks
AMHuh?
"AM" <anonymous@.codecomments.com> wrote in message
news:Or0wyERRFHA.3544@.TK2MSFTNGP12.phx.gbl...
> Hi all gurus
> If I create a package and schedule it for jobs and then if i delete the
> package and create a new package with same name. Then my job for old
> package
> will run on new package which has name of old deleted package?
> In my case my old job runs new package.
> will it make any problem?
> Thanks
> AM
>
>|||AM,
If you create a DTS package, then schedule it, then delete the package, and
create a new one with the EXACT same name, your scheduled job will still wor
k.
Hope that answers your question.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602_.html
"AM" wrote:
> Hi all gurus
> If I create a package and schedule it for jobs and then if i delete the
> package and create a new package with same name. Then my job for old packa
ge
> will run on new package which has name of old deleted package?
> In my case my old job runs new package.
> will it make any problem?
> Thanks
> AM
>
>sql
Showing posts with label thepackage. Show all posts
Showing posts with label thepackage. Show all posts
Wednesday, March 28, 2012
scheduling package- Urgent
Hi all gurus
If I create a package and schedule it for jobs and then if i delete the
package and create a new package with same name. Then my job for old package
will run on new package which has name of old deleted package?
In my case my old job runs new package.
will it make any problem?
Thanks
AM
Huh?
"AM" <anonymous@.codecomments.com> wrote in message
news:Or0wyERRFHA.3544@.TK2MSFTNGP12.phx.gbl...
> Hi all gurus
> If I create a package and schedule it for jobs and then if i delete the
> package and create a new package with same name. Then my job for old
> package
> will run on new package which has name of old deleted package?
> In my case my old job runs new package.
> will it make any problem?
> Thanks
> AM
>
>
|||AM,
If you create a DTS package, then schedule it, then delete the package, and
create a new one with the EXACT same name, your scheduled job will still work.
Hope that answers your question.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602X.html
"AM" wrote:
> Hi all gurus
> If I create a package and schedule it for jobs and then if i delete the
> package and create a new package with same name. Then my job for old package
> will run on new package which has name of old deleted package?
> In my case my old job runs new package.
> will it make any problem?
> Thanks
> AM
>
>
If I create a package and schedule it for jobs and then if i delete the
package and create a new package with same name. Then my job for old package
will run on new package which has name of old deleted package?
In my case my old job runs new package.
will it make any problem?
Thanks
AM
Huh?
"AM" <anonymous@.codecomments.com> wrote in message
news:Or0wyERRFHA.3544@.TK2MSFTNGP12.phx.gbl...
> Hi all gurus
> If I create a package and schedule it for jobs and then if i delete the
> package and create a new package with same name. Then my job for old
> package
> will run on new package which has name of old deleted package?
> In my case my old job runs new package.
> will it make any problem?
> Thanks
> AM
>
>
|||AM,
If you create a DTS package, then schedule it, then delete the package, and
create a new one with the EXACT same name, your scheduled job will still work.
Hope that answers your question.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602X.html
"AM" wrote:
> Hi all gurus
> If I create a package and schedule it for jobs and then if i delete the
> package and create a new package with same name. Then my job for old package
> will run on new package which has name of old deleted package?
> In my case my old job runs new package.
> will it make any problem?
> Thanks
> AM
>
>
Scheduling DTS Package in SQL 2005
We have an issue scheduling a DTS package we have created... We can run the
package manually in SSIS with NO PROBLEMS... but when we attempt to
schedule the package we receive the following error:
Date 5/9/2007 6:12:57 PM
Log SQL Agent (Current - 5/9/2007 6:12:00 PM)
Message
[LOG] Unable to read local eventlog (reason: The parameter is incorrect)
What configuration or settings are we missing to cause this to happen when
scheduled... If we execute it manually it runs fine.
Job is created
Credentials are setup
Proxies is setup under SSIS Package Execution
Using ASP, SQL2005 and DW8Hi Daniel
"Daniel" wrote:
> We have an issue scheduling a DTS package we have created... We can run th
e
> package manually in SSIS with NO PROBLEMS... but when we attempt to
> schedule the package we receive the following error:
> Date 5/9/2007 6:12:57 PM
> Log SQL Agent (Current - 5/9/2007 6:12:00 PM)
> Message
> [LOG] Unable to read local eventlog (reason: The parameter is incorrec
t)
> What configuration or settings are we missing to cause this to happen when
> scheduled... If we execute it manually it runs fine.
> Job is created
> Credentials are setup
> Proxies is setup under SSIS Package Execution
>
> --
> Using ASP, SQL2005 and DW8
>
What version of SQL 2005 are you using? According to
http://forums.microsoft.com/MSDN/Sh...137778&SiteID=1 SP1
fixed something that caused this!
John
package manually in SSIS with NO PROBLEMS... but when we attempt to
schedule the package we receive the following error:
Date 5/9/2007 6:12:57 PM
Log SQL Agent (Current - 5/9/2007 6:12:00 PM)
Message
[LOG] Unable to read local eventlog (reason: The parameter is incorrect)
What configuration or settings are we missing to cause this to happen when
scheduled... If we execute it manually it runs fine.
Job is created
Credentials are setup
Proxies is setup under SSIS Package Execution
Using ASP, SQL2005 and DW8Hi Daniel
"Daniel" wrote:
> We have an issue scheduling a DTS package we have created... We can run th
e
> package manually in SSIS with NO PROBLEMS... but when we attempt to
> schedule the package we receive the following error:
> Date 5/9/2007 6:12:57 PM
> Log SQL Agent (Current - 5/9/2007 6:12:00 PM)
> Message
> [LOG] Unable to read local eventlog (reason: The parameter is incorrec
t)
> What configuration or settings are we missing to cause this to happen when
> scheduled... If we execute it manually it runs fine.
> Job is created
> Credentials are setup
> Proxies is setup under SSIS Package Execution
>
> --
> Using ASP, SQL2005 and DW8
>
What version of SQL 2005 are you using? According to
http://forums.microsoft.com/MSDN/Sh...137778&SiteID=1 SP1
fixed something that caused this!
John
Scheduling DTS Package in SQL 2005
We have an issue scheduling a DTS package we have created... We can run the
package manually in SSIS with NO PROBLEMS... but when we attempt to
schedule the package we receive the following error:
Date 5/9/2007 6:12:57 PM
Log SQL Agent (Current - 5/9/2007 6:12:00 PM)
Message
[LOG] Unable to read local eventlog (reason: The parameter is incorrect)
What configuration or settings are we missing to cause this to happen when
scheduled... If we execute it manually it runs fine.
Job is created
Credentials are setup
Proxies is setup under SSIS Package Execution
Using ASP, SQL2005 and DW8
Hi Daniel
"Daniel" wrote:
> We have an issue scheduling a DTS package we have created... We can run the
> package manually in SSIS with NO PROBLEMS... but when we attempt to
> schedule the package we receive the following error:
> Date 5/9/2007 6:12:57 PM
> Log SQL Agent (Current - 5/9/2007 6:12:00 PM)
> Message
> [LOG] Unable to read local eventlog (reason: The parameter is incorrect)
> What configuration or settings are we missing to cause this to happen when
> scheduled... If we execute it manually it runs fine.
> Job is created
> Credentials are setup
> Proxies is setup under SSIS Package Execution
>
> --
> Using ASP, SQL2005 and DW8
>
What version of SQL 2005 are you using? According to
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=137778&SiteID=1 SP1
fixed something that caused this!
John
sql
package manually in SSIS with NO PROBLEMS... but when we attempt to
schedule the package we receive the following error:
Date 5/9/2007 6:12:57 PM
Log SQL Agent (Current - 5/9/2007 6:12:00 PM)
Message
[LOG] Unable to read local eventlog (reason: The parameter is incorrect)
What configuration or settings are we missing to cause this to happen when
scheduled... If we execute it manually it runs fine.
Job is created
Credentials are setup
Proxies is setup under SSIS Package Execution
Using ASP, SQL2005 and DW8
Hi Daniel
"Daniel" wrote:
> We have an issue scheduling a DTS package we have created... We can run the
> package manually in SSIS with NO PROBLEMS... but when we attempt to
> schedule the package we receive the following error:
> Date 5/9/2007 6:12:57 PM
> Log SQL Agent (Current - 5/9/2007 6:12:00 PM)
> Message
> [LOG] Unable to read local eventlog (reason: The parameter is incorrect)
> What configuration or settings are we missing to cause this to happen when
> scheduled... If we execute it manually it runs fine.
> Job is created
> Credentials are setup
> Proxies is setup under SSIS Package Execution
>
> --
> Using ASP, SQL2005 and DW8
>
What version of SQL 2005 are you using? According to
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=137778&SiteID=1 SP1
fixed something that caused this!
John
sql
Subscribe to:
Posts (Atom)