Job Scheduler fails and Managing Tempdb

Hello,
I have two issues, hoping someone can help.
Issue 1. I have various DTS packages that copy data from Progress
Database to Sql Data Warehouse. The ODBC Connection is stable and
packages have been auto scheduled by creating a job that is managed by
the SQL Agent service to run daily at night. The packages work fine
only in two cases, when running manually by using the DTSRun.exe
command line utility and when the job is manually run in the SQL Agent
service. Auto run is alwayz showing a status failer, I'm now using
windows scheduler and my packs are now always a success.
My question is why is SQL Agent not reliable? I'm 100% sure that there
is absolutely nothing wrong with the packets as they run error free
when manually ran.
Issue 2. My data warehouse is 28 G in size this makes the tempdb to
grow bigger everyday. To downsize it I stop and start the sql service
manually, can you please assist me with a batch command to auto start
and stop the service?
Thanking you in advance
Babalwa
1) This most likely is a permissions issue. Check that the account that SQL
Agent is running under has the appropriate permissions to execute everything
in your DTS package. It can be running under the LocalSystem account, which
doesn't have any permissions outside the local computer.
2) It's not much use shrinking tempdb, as it will grow again when you use
the server. And when tempdb auto grows that will only slow down your server.
You can check however if there are any transaction that stay open in tempdb
for a long time, cause extra space to be used, and prevent reuse of the
transaction log. Use DBCC OPENTRAN ('tempdb') to see if you have any old
transactions.
Otherwise the size of tempdb is something you have to live with, with your
current setup. Check if you can either change your applications and
databases, so tempdb is needed less, or you might have to get more harddisk
space.
Jacco Schalkwijk
SQL Server MVP
"Babalwa Magwentshu" <babalwa@.hotmail.com> wrote in message
news:5999368f.0407280128.75bd9322@.posting.google.c om...
> Hello,
> I have two issues, hoping someone can help.
> Issue 1. I have various DTS packages that copy data from Progress
> Database to Sql Data Warehouse. The ODBC Connection is stable and
> packages have been auto scheduled by creating a job that is managed by
> the SQL Agent service to run daily at night. The packages work fine
> only in two cases, when running manually by using the DTSRun.exe
> command line utility and when the job is manually run in the SQL Agent
> service. Auto run is alwayz showing a status failer, I'm now using
> windows scheduler and my packs are now always a success.
> My question is why is SQL Agent not reliable? I'm 100% sure that there
> is absolutely nothing wrong with the packets as they run error free
> when manually ran.
> Issue 2. My data warehouse is 28 G in size this makes the tempdb to
> grow bigger everyday. To downsize it I stop and start the sql service
> manually, can you please assist me with a batch command to auto start
> and stop the service?
> Thanking you in advance
> Babalwa
|||Thank you for your response Jacco,
Let me briefly expand on the issue, I am the domain administrator and
have designed the data warehouse packets and it's schedules under my
administrative password. I have checked the permissions, security
won't be the issue. Correct me if I'm wrong, this is how I understand
the security concept - for packages created under a Microsoft Windows
NT 4.0 or Microsoft Windows 2000 account, the job runs under the
security context of the account that started SQL Server Agent.
Thank you again,
babalwa@.hotmail.com (Babalwa Magwentshu) wrote in message news:<5999368f.0407280128.75bd9322@.posting.google. com>...
> Hello,
> I have two issues, hoping someone can help.
> Issue 1. I have various DTS packages that copy data from Progress
> Database to Sql Data Warehouse. The ODBC Connection is stable and
> packages have been auto scheduled by creating a job that is managed by
> the SQL Agent service to run daily at night. The packages work fine
> only in two cases, when running manually by using the DTSRun.exe
> command line utility and when the job is manually run in the SQL Agent
> service. Auto run is alwayz showing a status failer, I'm now using
> windows scheduler and my packs are now always a success.
> My question is why is SQL Agent not reliable? I'm 100% sure that there
> is absolutely nothing wrong with the packets as they run error free
> when manually ran.
> Issue 2. My data warehouse is 28 G in size this makes the tempdb to
> grow bigger everyday. To downsize it I stop and start the sql service
> manually, can you please assist me with a batch command to auto start
> and stop the service?
> Thanking you in advance
> Babalwa

Job Scheduler fails and Managing Tempdb

Hello,
I have two issues, hoping someone can help.
Issue 1. I have various DTS packages that copy data from Progress
Database to Sql Data Warehouse. The ODBC Connection is stable and
packages have been auto scheduled by creating a job that is managed by
the SQL Agent service to run daily at night. The packages work fine
only in two cases, when running manually by using the DTSRun.exe
command line utility and when the job is manually run in the SQL Agent
service. Auto run is alwayz showing a status failer, I'm now using
windows scheduler and my packs are now always a success.
My question is why is SQL Agent not reliable? I'm 100% sure that there
is absolutely nothing wrong with the packets as they run error free
when manually ran.
Issue 2. My data warehouse is 28 G in size this makes the tempdb to
grow bigger everyday. To downsize it I stop and start the sql service
manually, can you please assist me with a batch command to auto start
and stop the service?
Thanking you in advance
Babalwa1) This most likely is a permissions issue. Check that the account that SQL
Agent is running under has the appropriate permissions to execute everything
in your DTS package. It can be running under the LocalSystem account, which
doesn't have any permissions outside the local computer.
2) It's not much use shrinking tempdb, as it will grow again when you use
the server. And when tempdb auto grows that will only slow down your server.
You can check however if there are any transaction that stay open in tempdb
for a long time, cause extra space to be used, and prevent reuse of the
transaction log. Use DBCC OPENTRAN ('tempdb') to see if you have any old
transactions.
Otherwise the size of tempdb is something you have to live with, with your
current setup. Check if you can either change your applications and
databases, so tempdb is needed less, or you might have to get more harddisk
space.
Jacco Schalkwijk
SQL Server MVP
"Babalwa Magwentshu" <babalwa@.hotmail.com> wrote in message
news:5999368f.0407280128.75bd9322@.posting.google.com...
> Hello,
> I have two issues, hoping someone can help.
> Issue 1. I have various DTS packages that copy data from Progress
> Database to Sql Data Warehouse. The ODBC Connection is stable and
> packages have been auto scheduled by creating a job that is managed by
> the SQL Agent service to run daily at night. The packages work fine
> only in two cases, when running manually by using the DTSRun.exe
> command line utility and when the job is manually run in the SQL Agent
> service. Auto run is alwayz showing a status failer, I'm now using
> windows scheduler and my packs are now always a success.
> My question is why is SQL Agent not reliable? I'm 100% sure that there
> is absolutely nothing wrong with the packets as they run error free
> when manually ran.
> Issue 2. My data warehouse is 28 G in size this makes the tempdb to
> grow bigger everyday. To downsize it I stop and start the sql service
> manually, can you please assist me with a batch command to auto start
> and stop the service?
> Thanking you in advance
> Babalwa|||Thank you for your response Jacco,
Let me briefly expand on the issue, I am the domain administrator and
have designed the data warehouse packets and it's schedules under my
administrative password. I have checked the permissions, security
won't be the issue. Correct me if I'm wrong, this is how I understand
the security concept - for packages created under a Microsoft Windows
NT 4.0 or Microsoft Windows 2000 account, the job runs under the
security context of the account that started SQL Server Agent.
Thank you again,
babalwa@.hotmail.com (Babalwa Magwentshu) wrote in message news:<5999368f.0407280128.75bd9322
@.posting.google.com>...
> Hello,
> I have two issues, hoping someone can help.
> Issue 1. I have various DTS packages that copy data from Progress
> Database to Sql Data Warehouse. The ODBC Connection is stable and
> packages have been auto scheduled by creating a job that is managed by
> the SQL Agent service to run daily at night. The packages work fine
> only in two cases, when running manually by using the DTSRun.exe
> command line utility and when the job is manually run in the SQL Agent
> service. Auto run is alwayz showing a status failer, I'm now using
> windows scheduler and my packs are now always a success.
> My question is why is SQL Agent not reliable? I'm 100% sure that there
> is absolutely nothing wrong with the packets as they run error free
> when manually ran.
> Issue 2. My data warehouse is 28 G in size this makes the tempdb to
> grow bigger everyday. To downsize it I stop and start the sql service
> manually, can you please assist me with a batch command to auto start
> and stop the service?
> Thanking you in advance
> Babalwasql

Job failure cannot easily be traced

sql server ver 8... Microsoft Windows 2000
A copy of a database is made using sp_attach sp_detach and the
transaction log backup scheduled for that hour fails ...makes sense !!
There has been subsequent failures at the same time at the application
log but not at the database view history.
No idea what is going on here .....
Your ideas will be more than appreciated
Vince"Vincento Harris" <wumutek@.yahoo.com> wrote in message
news:2fa13ee7.0307110428.6b0d66a@.posting.google.com...
> sql server ver 8... Microsoft Windows 2000
> A copy of a database is made using sp_attach sp_detach and the
> transaction log backup scheduled for that hour fails ...makes sense !!
> There has been subsequent failures at the same time at the application
> log but not at the database view history.
> No idea what is going on here .....
>
> Your ideas will be more than appreciated
If you are detaching, copying and re-attaching the database, the source
database will be unavailable during that time. Possibly contributing to your
job failures.
A far better technique would involve running BACKUP and RESTORE, in that way
the source db does not have to be made unavailable.
Steve

JDBC driver for SQL Server 2000 and Java 5?

How can I get a copy of an updated JDBC driver that works with Java 5 (for
SQL Server 2000)? I need to upgrade my software to run on the latest Java
runtime soon...
Tim O'Konski wrote:
> How can I get a copy of an updated JDBC driver that works with Java 5
(for
> SQL Server 2000)? I need to upgrade my software to run on the latest
Java
> runtime soon...
Your old driver will work just fine with Java 5. Apart from a very
misterious _possible issue_ that noone knows nothing about:
http://groups-beta.google.com/group/...54c78ec924fc65
Alin.
|||Microsoft SQL Server 2000 Driver for JDBC SP3 has now been certified
against Java 1.5. We did not see any regression with the BigDecimal
issue.
-shelby
Shelby Goerlitz
Microsoft, SQL Server
"Alin Sinpalean" <alin@.earthling.net> wrote in message
news:alin@.earthling.net:
> Tim O'Konski wrote:
>
> (for
>
> Java
>
> Your old driver will work just fine with Java 5. Apart from a very
> misterious _possible issue_ that noone knows nothing about:
> http://groups-beta.google.com/group/...jdbcdriver/br
> owse_thread/thread/bc54c78ec924fc65
> Alin.