Hi Group,
Is it possible to schedule and execute sql jobs from an asp page.
I am developing an application that requires an administration section. In this section the admin would like to change / update the schedule of the sql job and also run the jobs ad hoc. Basicall y they would like the functionality of sql agen in enterprise manager to be available from their web application.
Has anbody done this before ?
All information / solutions shall be psoted back to the group as I reckon this would be pretty useful functionality.
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?
I had a few jobs as schduled DTS tasks in SQL 7. I manually saved them and reset the connection. I am able to execute the tasks successfully. However, on scheduling the same, it is failing. I am able to schedule other tasks successfully. So the scheduler is working OK. All tasks that involve dts are not running properply with the scheduler.
Hi I have a strange scheduling problem. I have a job, i test it through BIDS - Works I test it through SSMS - works I run the job - Works I schedule for a run time job - Works I schedule for a recurring job - Works
However (here is the really annoying part) it fails to run at the night run (11.20PM) there are 6 other packages that run fine after it , 11.30 , 1AM .. 4 AM etc ...
So last night I changed the package to run at a later time, and it worked, but the other package that ran 2nd (which now ran 1st) failed !!
its almost as if the 1st package has to fail !!!!! When i look at the history and detailed log all it says is "The step Failed"
anyway , I can set up a workaround by starting a dummy job that is supposed to fail..
FYI the jobs are run under administrator and they are protected by a password (encryptSensitiveWithpassword) .
Yao, Could anyone help me with, or point me to information regarding, scheduling jobs for MSSQL 2000? I need to execute a SQL Command, monthly, which sets a budget field to a fixed ammount, something like: UPDATE Programs SET Budget = 500. --Kyle Johnson
mangesh writes "HI Everybody, Please help me to solve this problem. I am not getting any solution to run jobs over sql server express. it does not have sql agent service.please suggest alertnative. Mangesh"
How can I use SQL Server Agent schedule to start my.exe? I am not sure in command that I have to place in "Edit Job Steps" DialogBox. It's not working just with path. File is accessible, it's on the same server. I dont know KeyWord to execute this .exe.
I have just moved an old sql 2000 database over to new hardware and sql 2005. I had a few dts jobs that ran on the old server and I have converted them over to SSIS. In VisualStudios the packages run just fine, but when I try to schedule it on Agent, It just fails and says step 1 failed. I have looked at it for hours and still have nothing.
Anyone got anything i can try to get this working?
I developed a package,configuration file on my machine i imported the packages on to the SSIS msdb folder, i am scheduling the package by using SQL Server Agent, Jobs while scheduling i got the error
Executed as user: user. ...cute Package Utility Version 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 3:14:00 PM Error: 2007-10-23 15:14:00.19 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "DTS Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2007-10-23 15:14:00.49 Code: 0xC0202009 Source: SampleSchdule Connection manager "Source Connection" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "HiT Software OLE DB Component for DB2/400" Hresult: 0x80004005 Description: "HiTOLEDB400 datasource object (Initialize) - ODBS error: Error on request data". End Error Error: 2007-10-23 15:14. The step failed.
and i have the sysdba permissions to schedule the packages. when i run the package manually in msdb folder it is executed successfully and one more thing i have developed this package on 32 bit machine, and the server is running on 64 bit and i developed the package on 9.00.3042 version, server is 9.00.3054 I am using SQL Server Integration services package option,package source as SQL Server in Steps while scheduling. I am using protection level as EncryptAllWithPassword.
I wanted to schedule my SQL Agent Job with SSIS package loading data into Oracle Destination can it be possible, if not. What do i do to schedule my SSIS package?
I have created a VB.NET application using Visual Studio. I wish to schedule this application on SQL Server Agent, reason being, I wish to be notified when the job succeeds / fails, which is not possible using Win Scheduler.
Any suggestions as to how this can be done?
One way, I think, this can be done is by making use of xp_cmdshell. But, I do not wish to use xp_cmdshell.
I created a fairly simple SSIS package to move data from a remote server which uses SQL Server Authentication to a local server that uses Windows Authentication. Everything works fine when executing the package within BI studio and if I execute the package by connecting to SSIS. If I schedule it as a SQL Server Agent Job, however, the non-integrated security fails unless I manually edit the connection to include the password. Obviously this is insecure because it is in plain text. What can I do?
I am having a strange error coming in SQL server 2005.
I had a DTS package developed in SQl server 2000. Then i had migrated that DTS package to SSIS package using Execute DTS 2000 package. The conversion is successfull.
Then when i manullt execute this package it runs successfully without giving any error. But then wheh i schedule a SQL server agent job for the same above SSIS package it fails giving me some cryptographic error as follows:
Message Executed as user: CATOS-CGDBTUW02SYSTEM. ....3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 11:00:00 PM Error: 2008-02-20 23:00:00.66 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "PackagePassword" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2008-02-20 23:00:00.66 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "SQLPassword" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2008-02-20 23:00:01.00 Code: 0x00000000 Source: Execute DTS 2000 Package T... The package execution fa... The step failed.
Not sure why is this happening.
Manually running the SSIS package from Visual studio does not gives error, but the same SSIS package when is been schedule from SQL server 2005's SQL server agent job it fails giving above error.
I have a series of jobs in the SQL server Agent that will begin and appear to run fine, but will never finish. Is there a way to limit the time that a job will run in the agent, for instance stop with failure if not completed within 1 hour?
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
Hi Guys, Can you please advice me on if there is a limitation on SQL agent Jobs. If then how many jobs can SQL server accomedate. If there is a limit, then is there are any ways to increase it? I appreciate your quick response. Thanks
I have several users that are a member of a Windows Nt group. I want to be able to allow this group to create, update, and delete SQL Agent Jobs. But I do not want them to be members of the SYSADMIN role. Everything that I have found states that they must be members of this server role to perform these actions. Does anyone have an idea on how to accomplish this? or point me in some kind of direction to explore.
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.
The SQL Server Agent process is running. When I use EM to start a database integrity check job, it fails with an error message of 22029 and the following:
[LOG] SQLServerAgent security context does not have server-autorestart privileges
I can not find error 22029 in Books on Line. I will go to Microsoft Knowledge base and research this problem.
In the mean time if someone can help, it is much appreciated.
I am trying to write a T-SQL script to change about 200 SQL Agent jobs to send notification to a different email notification list. I could do this manually but it would take me a lot more time. Is there a way to script this out in T-SQL? Thanks!
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???
I have a job with a single ActiveX step that I have setup and am having problems running.
If i set the SQL Server Agent to run as an Administrator then my job processes fine however under the default setup which has the SQL Server Agent running as Local System I get an error.
I assume this is permissions problem so I created a basic windows user called ABC. I then created a credential called ABC linked to the windows user ABC. I then created a proxy that uses the credential ABC and then ticked the box that allows the proxy to run ActiveX scripts. I then set the ABC as a principle of the proxy.
I then set my single job step to be run under the ABC credential.
Still no luck. This is the first time i've worked with this sort of thing so I'm not sure if I'm going about it in the right way.
Please explain how i can have a job that runs as an active X script. I understand running sql server agent as administrator is bad for security so what are the alternatives?
in reference to both MSSQL 2k8R2 and 2012, if i have a named instance AND a default instance on the same installation, and i create agent jobs (backups, indexing, etc) on either one, those same jobs appear on the "other" instance without having actually created them while logged IN to that instance.
Is this a normal feature of MSSQL? Doesn't seem like it should be happening that way.
I’m trying to write a script that will detect long running agent jobs.
Having looked at this article: http://www.databasejournal.com/features/mssql/article.php/3500276
It appears that agent job job id’s don’t necessarily get stored in the programname of the sysprocesses table. This is true if the agent executes an os command. It also appears that job steps do not get stored in the sysjobhistory until the step is complete so that cannot be used accurately.
Does anyone know of an effective way to find if there are long running jobs other than these methods?
I'm trying to configure mirroring with High Availability, Automatic Failover.
I know that all the jobs and maintenance plans need to be copied to the mirror server, and enabled if a mirror database takes over the principal role.
I wonder if it is a good solution to have all agent jobs on the Witness server (no jobs on principal and mirror). And all the jobs select the server where they should run (depending on current role).
One of the advantages of this approach would be that the jobs have to be created only once on the witness.
Will this solution work? What are the downsides of it?
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....
We have a SQL Agent job which runs on a server which is running mirrored databases. If the database which is affected by the job is in the mirror state, SQL Server agent locates the principle, executes the statements against that, and completes successfully.
This behavior is not consistent.
This is potentially serious; if jobs implemented on both sides of a mirror are not disabled, they may both execute.
We have suffered incorrect financial values due to a reconciliation job running twice (on each side of the mirror, and updating the principle twice).
I€™m trying to write a script that will detect long running agent jobs.
Having looked at this article: http://www.databasejournal.com/features/mssql/article.php/3500276
It appears that agent job job id€™s don€™t necessarily get stored in the programname of the sysprocesses table. This is true if the agent executes an os command. It also appears that job steps do not get stored in the sysjobhistory until the step is complete so that cannot be used accurately.
Does anyone know of an effective way to find if there are long running jobs other than these methods?
