Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
FiveDollarYoBet
Starting Member
2 Posts |
 Posted - 2007-10-17 : 15:31:57
|
| We're trying to import data via ODBC from a Progress DB running on our LINUX box. Our original SQL server is on Win 2k Server and works fine. We're trying to migrate our SQL to a new server on Win 2k3 Server. Our SQLServer is 2000 with SP3.I've recreated one of the DTS jobs on the new server and it runs fine when I run it manually but when I try to schedule the job it just runs forever (over 3+ hours for a 30 min job). I'm a SQLServer newb but I've gone through every setting on both server to make sure they're setup the same (ODBC, logins, permissions, etc).Any ideas?-J |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2007-10-17 : 16:22:55
|
| When you schedule the job the DTS is going to run under the context of the user that SQLAgent starts as. By default this is going to be the localsystem account, which is not going to have the same access that your domain account has. The first thing that I would look at is to make sure that both the SQL Agent and as well as SQL Server are running under domain accounts. Most shops have these services running under the same domain account as well as granting that account localadmin on the box SQL is running on. The 2nd thing is to make sure that this domain account has the proper access to the data you are pointing them at. The user has to have datareader access in the SQL2K database you are connecting to for example. Or if you are pointing at an access datbase or flatfile of some kind, this user needs to have access to the fileshare that the files are located on.-ec |
 |
|
|
FiveDollarYoBet
Starting Member
2 Posts |
Posted - 2007-10-18 : 12:09:05
|
| Everything's setup to run from the domain Administrator login. I've given that login full access to the sql2k DB.One weird thing... I created another job to import a table from the LINUX db that only contains 10 records and the DTS job works fine and when I set it up as a scheduled job it works! The original job will still work when run as a DTS job but still doesn't work as a scheduled job. Both jobs do the same thing.... connect to the LINUX db and do a select * from a table. |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-10-20 : 01:30:36
|
| Tried set job in windows scheduler to run the package with dtsrun? |
|
|
|
|
|
|
DTS Runs Manually but not from Scheduler