 | |
Re: Scheduling DTS job
microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Re: Scheduling DTS job -
04-01-2004
, 09:57 PM
|
-----Original Message----- Local System account has unrestricted access to the local box and cannot see off that box. The day schedule took just as long as overnight right? Would this take as long "SQL Server to SQL Server"? i.e. something in the driver setup -- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "Sam" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:f3cd01c41313$193708c0$a001280a (AT) phx (DOT) gbl... The SQL server agent is running as Local System Account. I cannot log in as this account. Is this equivalent to the local administrator? How can I simulate to run? I tried rescheduling during the day, and it took just as long. Nothing has been changed in sybase box. Thanks! -----Original Message----- OK so it can be FAST just not when scheduled. If that is the only difference then for me you have two routes of investigation 1. Accounts Log on to the server as the SQL Server Agent account and execute the package. Slow? Fast? 2. Timings Can you one day reschedule to sometime in the day? Can you manually execute at the same time as the overnight job? Is there anything going on the Sybase box -- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "Sam" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:f2e001c412fa$00bc7050$a001280a (AT) phx (DOT) gbl... hi Allan, In response to your questions: 1. System board was changed in the box 2. No.Its a job run at 7.30am, work has not started yet. 3. No one hammering the work. The fact is it is running perfectly alright and no changes has been made over the weeekend except for (1) 4. Yes, package involved data transferred from sybase to this SQL server. There are locking when the process started, which has never happened before. But i suspect it is due to the slow speed which causes the locking. 5. the part where data is transferred from sybase server to this server, sql server. Total 12 tables, about 4 tables took a long time. but these 4 tables are not big tables. 6. not known before. 7. Slow whenever i run the job. I realise that if execute from the package level (ie, not by scheduled job), it is FAST! But once i run through scheduling, it is slow. Why? Any thoughts? Thanks! -----Original Message----- There are a whole raft of things which may be affecting the performance. 1. Anything changed on the box? 2. Anybody doing something at the sme time? 3. Does the job involve the network? Anybody hammering the network 4. Does the package involve SQL Server? locking, blocking? 5. What parts of the package are taking the time 6. Resource issue? perfmon. 7. Does this only slow down at this time of the day or is it slow whenever you run it now? -- ---------------------------- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "sam" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:12f1a01c41216$191d0810$a301280a (AT) phx (DOT) gbl... hi! Recently my scheduled DTS job slowed down drastically. Normally it is a 2-3 mins job, but now it took about 1 hr. Can anyone suggest how can i do troubleshooting and where can i start from? Need advice. Thanks! Rgds, Samuel. . . . |
#2
| |||
| |||
|
|
hi! How do i see if there is any difference in the driver setup? Thanks! -----Original Message----- Local System account has unrestricted access to the local box and cannot see off that box. The day schedule took just as long as overnight right? Would this take as long "SQL Server to SQL Server"? i.e. something in the driver setup -- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "Sam" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:f3cd01c41313$193708c0$a001280a (AT) phx (DOT) gbl... The SQL server agent is running as Local System Account. I cannot log in as this account. Is this equivalent to the local administrator? How can I simulate to run? I tried rescheduling during the day, and it took just as long. Nothing has been changed in sybase box. Thanks! -----Original Message----- OK so it can be FAST just not when scheduled. If that is the only difference then for me you have two routes of investigation 1. Accounts Log on to the server as the SQL Server Agent account and execute the package. Slow? Fast? 2. Timings Can you one day reschedule to sometime in the day? Can you manually execute at the same time as the overnight job? Is there anything going on the Sybase box -- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "Sam" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:f2e001c412fa$00bc7050$a001280a (AT) phx (DOT) gbl... hi Allan, In response to your questions: 1. System board was changed in the box 2. No.Its a job run at 7.30am, work has not started yet. 3. No one hammering the work. The fact is it is running perfectly alright and no changes has been made over the weeekend except for (1) 4. Yes, package involved data transferred from sybase to this SQL server. There are locking when the process started, which has never happened before. But i suspect it is due to the slow speed which causes the locking. 5. the part where data is transferred from sybase server to this server, sql server. Total 12 tables, about 4 tables took a long time. but these 4 tables are not big tables. 6. not known before. 7. Slow whenever i run the job. I realise that if execute from the package level (ie, not by scheduled job), it is FAST! But once i run through scheduling, it is slow. Why? Any thoughts? Thanks! -----Original Message----- There are a whole raft of things which may be affecting the performance. 1. Anything changed on the box? 2. Anybody doing something at the sme time? 3. Does the job involve the network? Anybody hammering the network 4. Does the package involve SQL Server? locking, blocking? 5. What parts of the package are taking the time 6. Resource issue? perfmon. 7. Does this only slow down at this time of the day or is it slow whenever you run it now? -- ---------------------------- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "sam" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:12f1a01c41216$191d0810$a301280a (AT) phx (DOT) gbl... hi! Recently my scheduled DTS job slowed down drastically. Normally it is a 2-3 mins job, but now it took about 1 hr. Can anyone suggest how can i do troubleshooting and where can i start from? Need advice. Thanks! Rgds, Samuel. . . . |
#3
| |||
| |||
|
|
-----Original Message----- What I meant was, when you setup the sybase driver is there anything that might cause it to be less quick than it should? If you try to transfer the same rows(count) from SQL Server to SQL Server over the same network then do you experience the same problems? -- -- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "Sam" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:1462b01c4185e$3d0385d0$a601280a (AT) phx (DOT) gbl... hi! How do i see if there is any difference in the driver setup? Thanks! -----Original Message----- Local System account has unrestricted access to the local box and cannot see off that box. The day schedule took just as long as overnight right? Would this take as long "SQL Server to SQL Server"? i.e. something in the driver setup -- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "Sam" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:f3cd01c41313$193708c0$a001280a (AT) phx (DOT) gbl... The SQL server agent is running as Local System Account. I cannot log in as this account. Is this equivalent to the local administrator? How can I simulate to run? I tried rescheduling during the day, and it took just as long. Nothing has been changed in sybase box. Thanks! -----Original Message----- OK so it can be FAST just not when scheduled. If that is the only difference then for me you have two routes of investigation 1. Accounts Log on to the server as the SQL Server Agent account and execute the package. Slow? Fast? 2. Timings Can you one day reschedule to sometime in the day? Can you manually execute at the same time as the overnight job? Is there anything going on the Sybase box -- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "Sam" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:f2e001c412fa$00bc7050$a001280a (AT) phx (DOT) gbl... hi Allan, In response to your questions: 1. System board was changed in the box 2. No.Its a job run at 7.30am, work has not started yet. 3. No one hammering the work. The fact is it is running perfectly alright and no changes has been made over the weeekend except for (1) 4. Yes, package involved data transferred from sybase to this SQL server. There are locking when the process started, which has never happened before. But i suspect it is due to the slow speed which causes the locking. 5. the part where data is transferred from sybase server to this server, sql server. Total 12 tables, about 4 tables took a long time. but these 4 tables are not big tables. 6. not known before. 7. Slow whenever i run the job. I realise that if execute from the package level (ie, not by scheduled job), it is FAST! But once i run through scheduling, it is slow. Why? Any thoughts? Thanks! -----Original Message----- There are a whole raft of things which may be affecting the performance. 1. Anything changed on the box? 2. Anybody doing something at the sme time? 3. Does the job involve the network? Anybody hammering the network 4. Does the package involve SQL Server? locking, blocking? 5. What parts of the package are taking the time 6. Resource issue? perfmon. 7. Does this only slow down at this time of the day or is it slow whenever you run it now? -- ---------------------------- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "sam" <anonymous (AT) discussions (DOT) microsoft.com wrote in message news:12f1a01c41216$191d0810$a301280a (AT) phx (DOT) gbl... hi! Recently my scheduled DTS job slowed down drastically. Normally it is a 2-3 mins job, but now it took about 1 hr. Can anyone suggest how can i do troubleshooting and where can i start from? Need advice. Thanks! Rgds, Samuel. . . . . |
#4
| |||
| |||
|
|
I really can't think of any, Allan. I also have problem transferring from SQL to SQL, that is, it took just as long to run the DTS through scheduled job. Let me give you another scenario, say I run the same DTS as a scheduled job in another server, and it can be run in few seconds. But when i run on this particular server, it take ages. I must say i have no problem running the DTS (ie, execute package). But once I scheduled through a job, it took very long. Thanks for the help. Let me know if you have any clues. Sam. -----Original Message----- What I meant was, when you setup the sybase driver is there anything that might cause it to be less quick than it should? If you try to transfer the same rows(count) from SQL Server to SQL Server over the same network then do you experience the same problems? -- -- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "Sam" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:1462b01c4185e$3d0385d0$a601280a (AT) phx (DOT) gbl... hi! How do i see if there is any difference in the driver setup? Thanks! -----Original Message----- Local System account has unrestricted access to the local box and cannot see off that box. The day schedule took just as long as overnight right? Would this take as long "SQL Server to SQL Server"? i.e. something in the driver setup -- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "Sam" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:f3cd01c41313$193708c0$a001280a (AT) phx (DOT) gbl... The SQL server agent is running as Local System Account. I cannot log in as this account. Is this equivalent to the local administrator? How can I simulate to run? I tried rescheduling during the day, and it took just as long. Nothing has been changed in sybase box. Thanks! -----Original Message----- OK so it can be FAST just not when scheduled. If that is the only difference then for me you have two routes of investigation 1. Accounts Log on to the server as the SQL Server Agent account and execute the package. Slow? Fast? 2. Timings Can you one day reschedule to sometime in the day? Can you manually execute at the same time as the overnight job? Is there anything going on the Sybase box -- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "Sam" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:f2e001c412fa$00bc7050$a001280a (AT) phx (DOT) gbl... hi Allan, In response to your questions: 1. System board was changed in the box 2. No.Its a job run at 7.30am, work has not started yet. 3. No one hammering the work. The fact is it is running perfectly alright and no changes has been made over the weeekend except for (1) 4. Yes, package involved data transferred from sybase to this SQL server. There are locking when the process started, which has never happened before. But i suspect it is due to the slow speed which causes the locking. 5. the part where data is transferred from sybase server to this server, sql server. Total 12 tables, about 4 tables took a long time. but these 4 tables are not big tables. 6. not known before. 7. Slow whenever i run the job. I realise that if execute from the package level (ie, not by scheduled job), it is FAST! But once i run through scheduling, it is slow. Why? Any thoughts? Thanks! -----Original Message----- There are a whole raft of things which may be affecting the performance. 1. Anything changed on the box? 2. Anybody doing something at the sme time? 3. Does the job involve the network? Anybody hammering the network 4. Does the package involve SQL Server? locking, blocking? 5. What parts of the package are taking the time 6. Resource issue? perfmon. 7. Does this only slow down at this time of the day or is it slow whenever you run it now? -- ---------------------------- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "sam" <anonymous (AT) discussions (DOT) microsoft.com wrote in message news:12f1a01c41216$191d0810$a301280a (AT) phx (DOT) gbl... hi! Recently my scheduled DTS job slowed down drastically. Normally it is a 2-3 mins job, but now it took about 1 hr. Can anyone suggest how can i do troubleshooting and where can i start from? Need advice. Thanks! Rgds, Samuel. . . . . |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.