I have a an application that needs to run at the end of a series of database jobs in SQL Server 2005. The application will do processing on the data that was created by these jobs.
What would be the best way to trigger the execution of this application?
Depending on the type of application, if it's non-interactive then you can write CLR stored procedure that can be executed like any other stored procedure call.
If you don't mind having the application run on the database server, just add a new job step and execute it as part of the job. The command type is "operating system command (CmdExec).
Related
I have a huge amount of data in my tables and to extract results I used a stored procedure from it takes nearly 60 minutes.
Until it's done, my application is frozen or in wait.
My question is: I need to call the stored procedure from C# code and I do not need any output from it.
I handled all code in backend once done email got send.
I need only stored procedure should start execute and give alert to user, that once procedure is done mail will get to you.
Please describe how to run that procedure in the background without blocking my application in wait for user.
One possible solution which I have used successfully is to create a SQL Agent job that runs your stored procedure.
From your application you then just start the Agent job using sp_start_job, which returns immediately; SQL Agent then runs your procedure asynchronously with no additional involvement from your application.
I'm trying to build a background process that will check and execute a stored procedure (SQL Server 2008R2) that users will schedule on a UI application. I don't want to create a job, I want to handle it myself. So I was planning to run a check every 2 secs for example and check if there is process that rich the specific time and run it.
Is there any better way to do it?
If you don't want to set up a task within SQL Server, you could write an app that makes the DB call, then schedule that app through Windows Task Scheduler.
I have a stored procedure that I want to have run every day. I have never used jobs or schedules so i'm not sure how to do this. I'm using sql server 2012 management studio.
It is pretty straight forward. Here is an overview for creating a job from MSDN.
Ultimately you just create the job and your step is to EXEC yourStoredProc.
You can then create a schedule for your job to run whenever (link at the bottom of above article).
If it's a simple stored procedure, try the sqlcmd
http://msdn.microsoft.com/en-us/library/ms162773%28v=sql.110%29.aspx
which you can schedule in the Windows Task Scheduler. Be careful in setting up the service account it will run as, it need permissions on the database.
If it's more complex, setting up a package in SSIS (SQL Server Integration Services) gives a huge degree of power and flexibility.
I wanted a stored procedure to run at specified intervals everyday. Is there a way to do the same on SQL Server 2005?
I know we can create a batch file to run SP and schedule it with windows scheduled tasks but is there a way to do it from SQL Server itself?
There's a separate service called SQL Agent, which is created for this specific purpose: scheduling of tasks related to SQL Server.
This is a Windows Service that's initially disabled, so you'll have to enable that. Otherwise, it's all very straightforward: Management Studio has nice UI for managing Agent.
You can create jobs with sql server 2005
Use SQL Agent to schedule jobs.
See Creating Jobs
I have two queries saved on my SQL Server 2005 and I would like to have them running at certain intervals, e.g. every 24 hours. Is there a way to automate these queries and schedule them via SQL Server Management Studio?
You need to use the SQL Server Agent, installed as part of SQL Server. This is the background service that's responsible for running scheduled maintenance and backup tasks.
Expand the SQL Server Agent node in SQL Server Management Studio, you should see a tree node called "Jobs"
Right-clicking this will give you the option to add a new job. Jobs consist of a series of steps to be executed in order, and when you add a new step to your job, you can choose various types of step, including "Transact-SQL Script"
Create a new job, add a single T-SQL step, put the queries that you want to run into the step properties, and then use the "Schedule" option in the Job properties to create a recurring schedule that'll run the job every 24 hours (or whenever).
You can use the SQL Server Agent, which will allow the server to run the script/stored procedure.
You can also use the Windows Task Scheduler, either on the server or on any other server or workstation to schedule isqlw/sqlcmd to execute your script/stored procedure.
Create a job with a step in which you execute your queries; the job can be scheduled at your needs.
At a previous employer the operations department had a task sheduling application. They prefered to use the command line tools that come with sql server to execute jobs (stored procedures) on a scheduled basis. This way the "task scheduling application" could recieve an exit status (pass/fail, ok/error) and hold up dependent jobs.
I'm sorry I don't remember the name of the command line tool, but it was part of the sql server distro. I also do not remember the name of the task scheduling application. It was not the windows task scheduler. It was something enterprise level used to manage the nightly cycle.
Not sure of the scale of your project, but this is another way to go.
SKapsal's comment on a command line tool for executing SQL commands is a reference to osql (for SQL2000) or sqlcmd (for SQL2005+). You could save your script a file and run it from that command line using Windows Task Scheduler or something similar.
SQL Agent is still the preferred solution, however, as it provides GUI controls for job creation, scheduling, logging and viewing job execution history/results.
how to schedule a job for sql query to run daily?
This is similar question with helpful answer.
Covering simple step by step manual.