|
|
You're in the
sql server dts
group:DTS Transfer Job Fails
sql server dts:
server. Both servers are SQL Server 2000 standard. The job fails with an "unspecified error" which obviously is little help. I know it is connecting to both servers as it even shows me which jobs are already present on the destination server and allows me to check only the ones that are not. Are there any special issues that might cause this seemingly simple and straightforward transfer? I do not yet have access to SISS so has anyone had success transfering jobs with that tool? Are there any other options or third party tools that can transfer jobs from one server to another? Thanks,
If you are just transferring jobs, why not script them and run the script at
the destination, after changing any server specific info you need? -- Kevin Hill 3NF Consulting www.3nf-inc.com [quoted text, click to view] "dondraper40" <dondraper40@discussions.microsoft.com> wrote in message news:401B5369-4C82-4A6D-9F84-7C4C1C41E756@microsoft.com... >I have an SA credentialed connection for both the source and destination > server. Both servers are SQL Server 2000 standard. The job fails with an > "unspecified error" which obviously is little help. I know it is > connecting > to both servers as it even shows me which jobs are already present on the > destination server and allows me to check only the ones that are not. > > Are there any special issues that might cause this seemingly simple and > straightforward transfer? I do not yet have access to SISS so has anyone > had > success transfering jobs with that tool? Are there any other options or > third > party tools that can transfer jobs from one server to another? > > Thanks, > Don
I not aware it could be done by scripting but would actually rather do it
this way providing more documentation of the jobs. Are there any articles describing how to do this that you can point me to? Could I use something like Red Gate SQL Compare to do this? TIA Don [quoted text, click to view] "Kevin3NF" wrote:
> If you are just transferring jobs, why not script them and run the script at > the destination, after changing any server specific info you need? > > -- > Kevin Hill > 3NF Consulting > www.3nf-inc.com > > > > "dondraper40" <dondraper40@discussions.microsoft.com> wrote in message > news:401B5369-4C82-4A6D-9F84-7C4C1C41E756@microsoft.com... > >I have an SA credentialed connection for both the source and destination > > server. Both servers are SQL Server 2000 standard. The job fails with an > > "unspecified error" which obviously is little help. I know it is > > connecting > > to both servers as it even shows me which jobs are already present on the > > destination server and allows me to check only the ones that are not. > > > > Are there any special issues that might cause this seemingly simple and > > straightforward transfer? I do not yet have access to SISS so has anyone > > had > > success transfering jobs with that tool? Are there any other options or > > third > > party tools that can transfer jobs from one server to another? > > > > Thanks, > > Don > >
I don't think SQL Compare will help you, as jobs are data in a MSDB table,
not schema. Scriptin them out and re-running the script is the easiest way to do a one-time job move. Right-click the job, all tasks, generate SQL Script (or something like that...I don't have Enterprise Manager in front of me). Take the resulting .sql file, open it in a Query Analyzer session connected to the destination server and execute it. If you are needing to move the jobs regularly, this is when you would use DTS. If that is the case I would be interedted in finding out the business reason behind scheduled job moves... -- Kevin Hill 3NF Consulting www.3nf-inc.com http://kevin3nf.blogspot.com [quoted text, click to view] "dondraper40" <dondraper40@discussions.microsoft.com> wrote in message news:654F314E-F978-478F-A445-1A04488C38DF@microsoft.com... >I not aware it could be done by scripting but would actually rather do it > this way providing more documentation of the jobs. Are there any articles > describing how to do this that you can point me to? Could I use something > like Red Gate SQL Compare to do this? > > TIA > Don > > "Kevin3NF" wrote: > >> If you are just transferring jobs, why not script them and run the script >> at >> the destination, after changing any server specific info you need? >> >> -- >> Kevin Hill >> 3NF Consulting >> www.3nf-inc.com >> >> >> >> "dondraper40" <dondraper40@discussions.microsoft.com> wrote in message >> news:401B5369-4C82-4A6D-9F84-7C4C1C41E756@microsoft.com... >> >I have an SA credentialed connection for both the source and destination >> > server. Both servers are SQL Server 2000 standard. The job fails with >> > an >> > "unspecified error" which obviously is little help. I know it is >> > connecting >> > to both servers as it even shows me which jobs are already present on >> > the >> > destination server and allows me to check only the ones that are not. >> > >> > Are there any special issues that might cause this seemingly simple and >> > straightforward transfer? I do not yet have access to SISS so has >> > anyone >> > had >> > success transfering jobs with that tool? Are there any other options or >> > third >> > party tools that can transfer jobs from one server to another? >> > >> > Thanks, >> > Don >> >> >>
Thanks very much and this worked quite well. I knew I could script regular db
objects but never knew jobs could be scripted as well. Duh! BTW, I did attempt the same task that failed in DTS by using SISS in SQL Server 2005 and it also failed. However, the error information was very helpful and indicated the job owners did not match. So I checked the job owners on the source DB using the new SQL Management Studio and could see that several had an NT Auth User as the owner rather than SA. I was able to change those to SA and then the transfer completed without error. I could choose which jobs to transfer (or all) and even to overwrite where the destination job was already present. Worked like a champ. Thank again. [quoted text, click to view] "Kevin3NF" wrote:
> I don't think SQL Compare will help you, as jobs are data in a MSDB table, > not schema. > > Scriptin them out and re-running the script is the easiest way to do a > one-time job move. > > Right-click the job, all tasks, generate SQL Script (or something like > that...I don't have Enterprise Manager in front of me). > > Take the resulting .sql file, open it in a Query Analyzer session connected > to the destination server and execute it. > > If you are needing to move the jobs regularly, this is when you would use > DTS. If that is the case I would be interedted in finding out the business > reason behind scheduled job moves... > > -- > Kevin Hill > 3NF Consulting > www.3nf-inc.com > http://kevin3nf.blogspot.com > > > "dondraper40" <dondraper40@discussions.microsoft.com> wrote in message > news:654F314E-F978-478F-A445-1A04488C38DF@microsoft.com... > >I not aware it could be done by scripting but would actually rather do it > > this way providing more documentation of the jobs. Are there any articles > > describing how to do this that you can point me to? Could I use something > > like Red Gate SQL Compare to do this? > > > > TIA > > Don > > > > "Kevin3NF" wrote: > > > >> If you are just transferring jobs, why not script them and run the script > >> at > >> the destination, after changing any server specific info you need? > >> > >> -- > >> Kevin Hill > >> 3NF Consulting > >> www.3nf-inc.com > >> > >> > >> > >> "dondraper40" <dondraper40@discussions.microsoft.com> wrote in message > >> news:401B5369-4C82-4A6D-9F84-7C4C1C41E756@microsoft.com... > >> >I have an SA credentialed connection for both the source and destination > >> > server. Both servers are SQL Server 2000 standard. The job fails with > >> > an > >> > "unspecified error" which obviously is little help. I know it is > >> > connecting > >> > to both servers as it even shows me which jobs are already present on > >> > the > >> > destination server and allows me to check only the ones that are not. > >> > > >> > Are there any special issues that might cause this seemingly simple and > >> > straightforward transfer? I do not yet have access to SISS so has > >> > anyone > >> > had > >> > success transfering jobs with that tool? Are there any other options or > >> > third > >> > party tools that can transfer jobs from one server to another? > >> > > >> > Thanks, > >> > Don > >> > >> > >> > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |