Hi,
I have couple of questions about the scheduler:
I'd like my packages to run only on weekdays and disable a package if one of the first two packages fail. is it possible to do it?
Thanks
Gulden
i have a package scheduled in sql server.....
if i change something in the package and save the change...
will the scheduled job then reflect that change? or does the scheduled job have to be deleted and the package re-scheduled in order for the change to take affect?
(for example....i have a scheduled package which pulls some data from an oracle server and populates a sql server tabel. well....the oracle server has changed. so if i open my package and change the oracle server connection and save it, will the scheduled job have this change?)
Ray writes "Hi,
I tried to ask the NT admin to login the SQL server and setup a scheduled job to "Shrink the db" for testing purpose.
I tried my ID even I'm not the NT admin, but setup as SQL server as sysadmin, setupadmin, processadmin.
Then the job start and got the error.
[298] SQLServer Error: 15404, Could not obtain information about Windows NT group/user 'DOMAINMYNAME', error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)
I have no idea why that happen to NT admin. then I check the Services for SQL Agent under the control panel- admin tools- services.
It shows using the LOCALSYSTEM as login for the SQL Agent service.
Any one have any idea. what security requirement to run a job other than use 'sa' account, since we are using on Windows authenciation mode only.
I must be something is missing? hope some experts here to answer my question.
Thanks!"
I've tried finding an answer to this on this website but I don't see any. I'm running SQL Enterprise Manager v8.0 and have a job in the SQL server agent folder that won't run as scheduled nor will it run manually if I Right-Click and choose Start Job.
It's designed to run a DTS. I can run the DTS manually without errors but the job won't run it for me. I will try to provide as many details in this post as I can in hopes that someone who is more experienced at this can help me.
DTS DETAILS
The DTS is designed to transfer data from a table on one server and transfer it through a firewall to another server into a table on that server. Then delete the entries from the originating table. This works very well if I run it manually. The purpose of deleting entries from the web server is for security. Once the data in on the other side of the firewall it's safe.
The job however will not run either manually or from it's schedule. I've tried creating a new job and setting up a very simple schedule that runs daily every 2 minutes for example. I've played around with different times but no luck. So I will try and provide you with job details below:
JOB DETAILS
Name: TransferData
Enabled, Target = Local Server
Category: Uncategorized Local
Description: Execute package: TransferData
STEPS
ID: 1
Step Name: TransferData
Type: Operating System Command
On Success: Quit with Success
On Failure: Quit with Failure
PROPERTIES OF STEP
Step Name: TransferData
Type: Operating System Command (CmdExec)
Command: ( I have no idea what this translates to as I did not write it) DTSRun/~Z0xF6EE76ED6259A60AC370F465DE7F3095F4B37F7176C05B8E72E396DEBE60135E53ACFEDB00E1F216DD8EC8206782439BA435771E3C1E8A7A5D0DAE3F3AAA9F48BF08A9A9FA23C010A85573546F6B6B900323F76DC8A27EACAFD63904464DD5A9B28137
Nothing special in the advanced tab
SCHEDULES TAB
ID: 20
Name: TransferData
Enabled: No
Description: Occurs every 1 day(s), every 2 minute(s) between 12:00:00 AM and 11:59:59 PM
and is setup as Recurring
Nothing in Notifications Tab
I only have two SQL books to reference. This is a production fire to put out and I really need the help here as I am not a certified SQL guru.
I hope I have provided enough information here for someone to help. I'm happy to provide an email address for easier contact should you request it.
Thanks in advance for any assistance with this.
Hi All,
I am not able to see any of the jobs in the enterprise manager that are scheduled on one of our production servers. Have any body seen this type of behaviour of SQL server.. The jobs are there in the SQL as I can query sysjobs table to see there entry.. The jobs are being executed properly when they are supposed to..
Thanks
Ajay
Hello all,
we just moved our databases over from a SQL 2000 server onto a new SQL 2005 server. We had no problem migrating them over, but was wondering if there was a way to migrate the jobs over as well. We have about 20 of them and would prefer not to hav to create them all again on the new server.
Thanks in advance,
Phoenix
HELP! I have been banging my head against a brick wall on this one all this morning AAAAAAGGGHHH!
1. I have an SSIS package that runs a simple SQL script and then updates a few tables by downloading some XML of the web. It runs fine when I kick it off manually under SSMS.
2. I created a SQL Server Agent job to run it every day. This always fails. The error information in the log is useless ("Executed as user: domainuser. The package execution failed. The step failed." - I had already figured that out!). It fails almost straight away, and when I enable logging for the SSIS package, no info is ever logged (text file, windows event log, whatever).
3. Out of desperation I have changed Agent to run under the same domain user account that I created the package with. No use.
My questions:
1. How can I get more detailed logging from SQL Server Agent?
2 Any ideas about why it's failing in the first place.
Many thanks in advance.
Ben
Hi,
I have created a SSIS package and tested it in V.Stdio where it runs fine and uploads file on the remote server.
Now I have scheduled it to run as a job in SQL SERVER AGENT as JOB, but it fails when it comes to the upload task?
I am quite sure as it is something with FTP connection string or security, but can't figure it out.
I have simply added the IP/login/password in the connection manager for upload task.
Any help/ guidance would be great.
Thanks,
Ad
Hello,
I need to document all SQL Server Agent Jobs with full description of dependencies - database, table, stored procedure, etc.
Is there are a tool that I can download for that particular use???
Thank you so much
I created an agent job, and it runs fine, but I want more control over the scheduling. I need to schedule jobs to run Sunday through
Thursday at 8:00pm, skipping Friday.
How can I use the agent job interface and customize the schedule this way? Will I have to resort to a Windows Service and control the
scheduling that way?
Hi Guys,
I am not sure if this is the right place to put a question on SQL Server Agent.
I have scheduled some SSIS Jobs using the SQL Server Agent, and wanted to know how can I view detailed log information on how the Job ran (particularly Failure Information).
The information in the Log File Viewer to see the job execution log doesnt seem to help much - as it only says weather the Job Failed or Succeeded.
I need to see the reason and/or the step in a job where it failed!
Can someone help me out with some insight into this....
Thanks
Pramod
I have a few jobs in sql server 2005 agent that got corrupted that Iwould like to restore.
Do they get backed up and how can I restore them?
We are not certain if this has happened due to the SSIS FTP Task, but incidently the Excel file that is being copied from the FTP site using an SSIS FTP Task got corrupted a couple hours after the package was scheduled as a SQL Server Agent Job on SQL Server 2005.
I had a SQL Server 2000 DTS package doing the same thing, but it was never an issue then. I was using the FTP Task there along with an Excel Data source in that and has been working for a couple years atleast with never any corruption related issues.
In the SSIS SQL Server 2005 package I am using an FTP Task with an Excel Connection Manager and Excel source and the Excel file got corrupted within a couple hours of the package being scheduled as a SQL Server Agent job.
Has anyone experienced this issue? Any inputs will be appreciated.
Just as an fyi, the excel file has a lot of vlookups.
Thanks,
MShah
Just wondering if anyone knew if it was possible to create a SQL Server agent job that ran once every 30 seconds. I can't enter a value below 1 minute when editing the job schedule in Enterprise Manager.
Alternatively, I can create duplicate stored procedures and set one to run on the minute and one on the half minute. Thought there might be a better alternative to this though and I'll always have to be remembering to makes changes to both sprocs.
Thanks!
Hi. I was wondering if anyone has ever had a problem where nothing seems to be wrong with the server, and SQL Server Agent is up and running, but jobs fail. We had a job run at midnight, and it was the last successful run. Every job failed after that, with an error stating "Unable to retrieve steps for job..." There doesn't seem to be any reason for the problem. The jobs were kicked off manually and they all ran.
The only other error messages we could find were in the Application Event Viewer on the server. But the first error happened days ago and said this: "The description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Unable to open shim database version registry key - v2.0.50727.00000."
Since then, every few seconds this error occurred: "Windows cannot load extensible counter DLL MSSQLServerOLAPService, the first DWORD in data section is the Windows error code."
We turned off the performance monitor counters and that error stopped. But we still have no idea if that was the cause of the problem.
This isn't the first time we've had an issue with jobs failing because the steps couldn't be 'found', while SQL Server Agent was up and running.
Has anyone else had this problem?
Thanks!
Hello everyone. I'm having a problem with the sql server agent occasionally not executing its scheduled jobs, and unless the sql server agent is restarted they will not execute according to their schedule. I've read many posts on people having problems with running a package manually and then not being able to run it in a job, although that is not my problem since these are jobs that have all run successfully historically, and only until the agent is restarted do they start working again. It is the strangest thing.....we have many different jobs on this server and all of them will just mysteriously stop being executed. Two other things of note, the agent and server processes both run on AD accounts, and we receive this error:
SQL Server Scheduled Job 'X' - Status: Failed - Invoked on: 2007-10-27 02:00:00 - Message: The job failed. Unable to determine if the owner (ADadacct) of job 'X' has server access (reason: Unable to connect to server - check SQL Server and SQL Server Agent errorlogs).
Any help would be greatly appreciated.
Hello All,
My database application has certain stored procedures which are scheduled to run at certain predefined interval (say once everyday). Now to implement this logic I have two options with me, first being to use the EXECUTE SQL TASK of the SSIS package and schedule it using the windows scheduler and the other is to use the SQL Server Agent Jobs and schedule it there itself. Now the current implementation is using the SSIS packages and I even know that the second approach of using the SQL Server Agents Job is better.
The only thing I want to know is whether it makes sense to invest time in converting my SSIS packages (20 in all) to SQL Server Agent jobs or not. Can somebody briefly explain or give some pointers regarding the performance benefits of Agent Jobs over the SSIS packages.
Thanks in Advance
Mitesh
I want to schedule a database backup using SQL Server Agent Jobs how can i do this?
View 1 Replies View RelatedWhen I give job Id in filter of this query this will give job status of "Success" but actually my job is currently in executing stage. I want to get all jobs that are currently in executing status.
Use msdb
go
select distinct j.Name as "Job Name", --j.job_id,
case j.enabled
when 1 then 'Enable'
when 0 then 'Disable'
[Code] ....
In one of my environments, I need to grant the ability to view all the logins and agent jobs to an account, but I don't want to give him "sysadmin" or "securityadmin".
View 2 Replies View RelatedI'm trying to execute my package using schedule in SQL Server Agent, I've already tested my package by run it manually in Integration services and it works. The table created, the data from my flat file also inserted into the table correctly and the result return with success.
The question is why when I execute my package using SQL Server Agent, the SQL Server Agent keep executing my package like infinite loop until I stop the job. after I stop the job there is no error generated by sql server. Could you figured why this happen?? I've already tried to upgrade into SP2 and set the package protection level and still not get good result from it. thank you.
I'm thinking of using the SQL Agent Job Scheduler as part of a larger application and I'm wondering if anyone knows of a limit on how many schedules or jobs that can exist on a SQL Server at one time.
Thanks!
hello All
I am trying to figure out a way , looking at the tables in MSDB (SysJobHistory) that if a scheduled job is running and not completed yet , for how long it has been running. I have to look for all the jobs with run_status = 4 (in process). But what i figured out it no history is written till the job is finished or cancelled. Can anyone help me with this
thanks
Alsi
Hi,
I have a scheduled job that run one time a day at 10 pm. My problem is that if the job fail, i want that the job run 10 minutes after until it complete with success.
Any tips on how to do this
Martin
I am running a scheduled DTS which transfers all the rows in a production table to another server every 30 minutes,each time it truncates the table on the second server before transfer.It has been running fine for several days.Will there be any problem in this kind of backup strategy? Do I have to clear any history logs frequently?Or any other problem can happen? Can anyone suggest any precautions,as there will not be any down time allowed.Replication is also not acceptable by the client.
Thanks.
Hi all,
I find some scheduled jobs are switching from an 'enabled' state to a 'disabled' state apparently for no good reason. The job itself still shows as being 'enabled', however the associated scheduled becomes 'disabled'. Does anyone why this would be? Is the problem associated with a paritcular service pack or anything??
Any help is appreciated.
Thanks!
I have a job that runs hourly every day from 7:00 to 19:00.
I'd like to be able to detect the last run of the day.
The problem is, I may change one (or both) or the scheduled run times,
so I don't want to hard code 19:00 into my detection scheme.
I stumbled across the sysjobsschedules table in the msdb database,
and I think the Next_Run_date and Next_Run_time fields will get me where
I need to be.
I'm trying to build a second job that runs at 10 minutes after the hour, 24 hours a day that will somehow detect whether or not the primary job just finished it's last run of the day, and if so, insert some records into a table.
Here's what I have so far...
DECLARE @intFlg1 INTEGER
SET @intFlg1= (SELECT CASE WHEN CONVERT(DATETIME, CAST(next_run_date AS CHAR(8)), 102) = Prod_Plan.dbo.RemoveTime(GETDATE()) THEN 1 ELSE 0 END
FROM msdb.dbo.sysjobschedules
WHERE (name = N'prodplan_importorders'))
IF @intFlg1=0
INSERT INTO BLDOFF_INV_DAILY()
SELECT GETDATE() AS Expr1, Product, Whse, Qty
FROM BldOff_Inv_Hourly
The problem with this is that it will append records every hour after the last run until midnight. I only want it to append them once.
Its not possible to schedule jobs via Express is it? Like I have a process that connects to an Oracle system grabs the data... plays with it some and then inserts it into the MSSQL 2005 server... We need this process to run say every 2 hours... Express cant do that cant it?
View 4 Replies View RelatedI have this backup job created, this job is being called from VB once all the data is finished loading. You need to have SA permissions or be the database owner in order to run the jobs.
How do I get around this, I don't want the user to be db owner or have sa privledges.
Does anyone have any SP to get around this
Thanks for any help
Hi all
I'm stuck here, I hope someone else has come across a problem like this.
About 12 scheduled jobs are running on SQL Server 7 (NT is the operating system)
They are supposed to run under the security context of an account set up to run as a service for both SQL Server Agent and SQL scheduling Agent. This user account was given all the permissions that the person scheduling them has(that's me, also part of sysadmin role). Everything was running fine until one day the server crashed and after it came back up, nothing was working. The error I get is an odbc link error. I was even unable to open up the packages, so I had to recreate them from saved .dts files. I did come to find out that the NT domain admin password was changed as well, but why should that affect the user account under which these jobs run? Anyway, at the moment, nothing runs on the server and I can only manually execute them as packages from my local computer. Please help me to narrow down what could be the problem. The Agent service and sql server services are running so that's not the problem. thanks...
Hello,
Does anyone has a script or knows how to find out whether the schedule job completed or not?
If I schedule the job to backup all databases on server and e-mail me when job completes.
But one time the job got stuck and somehow never completed. Is there a way I can schedule the job to see whether the other job completed or not?
Thanks for the Help
Rea
Had to rename a SQL 2000 box and now the scheduled maint jobs that were created under the previous name of the box cannot be deleted via EM. Can anyone offer help?
View 1 Replies View RelatedWe have DTS Packages that are scheduled to run nightly and show up in EM under JOBS under SQL Server Agent. A password got changed and some of the nightly jobs blew up.
Went into the Packages and entered the new password and successfully executed the packages BUT when I go back to jobs under the SQL Server Agent, the jobs STILL will not run - they fail with a login failure - as if i never fixed the DTS package. HELP