Re: Job Scheduler fails and Managing Tempdb
From: Jacco Schalkwijk (jacco.please.reply_at_to.newsgroups.mvps.org.invalid)
Date: 07/28/04
- Next message: balkii: "MAX(ISNULL([Sequence],0))+1"
- Previous message: Ilya Margolin: "Re: urgent- simple query"
- In reply to: Richard Jolly: "Re: Job Scheduler fails and Managing Tempdb"
- Next in thread: Richard Jolly: "Re: Job Scheduler fails and Managing Tempdb"
- Reply: Richard Jolly: "Re: Job Scheduler fails and Managing Tempdb"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 28 Jul 2004 15:10:59 +0100
Can you give an exact description of the problems you encounter with DTS.
You can turn logging on on both the job and the DTS Package to get some more
information about what goes wrong.
As I said in my previous post, shrinking tempdb is not very useful. It is
just that your server needs that much tempdb space, and eventually it will
have enough and not grow anymore. If it keeps growing, there is a problem
somewhere in one of your applications, maybe that transactions are kept open
indefinitely, and you will have to fix this problem. Cycling SQL Server on a
regular basis is not a good solution for any problem.
The commands you need btw are:
net start sqlserver
net stop sqlserver
-- Jacco Schalkwijk SQL Server MVP "Richard Jolly" <rjolly@crgroup.com> wrote in message news:Oe5UsOKdEHA.644@tk2msftngp13.phx.gbl... > Hi, > > I don't think its the permissions, as we are running as the domain > administrator, which has been set to have access throughout everything > including SQL Server.The failure of the job usually entails a few tables > not being populated in a DTS package, however if the job is run manually > or the DTS package is run the tables populate, we have no problems with > Windows scheduler, which leads me to believe there is a general fault > with SQL Server's SQL agent when it comes to automated runs. Other > people seem to have the same problem. > > Is there away around this, as microsoft don't seem to have done anything > about it in service pack3! > > The Tempdb growth, we can shrink it by stopping and starting the SQL > service, we just need the command to do this "I think its net stop and > net start, I'm not sure however". > > Thanks for your posting > > Regards, > > Richard Jolly > > *** Sent via Developersdex http://www.developersdex.com *** > Don't just participate in USENET...get rewarded for it!
- Next message: balkii: "MAX(ISNULL([Sequence],0))+1"
- Previous message: Ilya Margolin: "Re: urgent- simple query"
- In reply to: Richard Jolly: "Re: Job Scheduler fails and Managing Tempdb"
- Next in thread: Richard Jolly: "Re: Job Scheduler fails and Managing Tempdb"
- Reply: Richard Jolly: "Re: Job Scheduler fails and Managing Tempdb"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|