I am getting this error when a user runs this job that was created. It is executing a dos command. Any hints on what to fix or look for? This account seems to be o.k. WHat privilege needs to be set for this account.
Password verification of the 'SQLAgentCmdExec' proxy account failed (reason: A required privilege is not held by the client). The step failed
Is there a way to grant a group of users the ability to execute some jobs on a server, but restrict their access to others.
We'd like to grant our developers the permission to execute their jobs (many developers and we'd like to avoid a shared account) without giving them the ability to execute our backup, reindex, etc jobs.
Is there a way to grant execute on some jobs, but not all to a Windows group?
We're using the new msdb SQLAgent role to allow them to see all jobs and view output, but there doesn't seem to be a way to grant execute on specific jobs only.
I have a very peculiar problem. I have few CommandExec jobs on SQL Server 7.0 which has been scheduled to execute at a specific time. The jobs are executing properly but, the problem is they stop after the completion. i.e after finishing the jobs they still flash a message "Executing the job" they don't flash the message "Not Running" this is happening only to commandExec jobs, I have also few TSQL jobs which are working properly. I tried even giving the duration (start and stop time) but no use. Has anyone encountered this problem? If you have a solution PLS pass it on to me. I am in a very desparate situation.
Is there any way so that we can run/ execute multiple jobs or local packeges at once. Can we create any sql script which will execute multiple jobs/packeges at once. please advise
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).
I have an web application where the users has to run SQL scheduled jobs from the webpage. How to assign permission to a specific user to run specific jobs without making them a member of a Sysadmin role?
Any ideas you all smart people? Thanks in advance!
Just an FYI for those scheduling SSIS packages on 64bit Itaniums. This came to light when using a 32 bit OLEDB driver on a 64bit Itanium.
When manually executing the package on the server through SQL Management Studio, we got the expected results. However, when we scheduled the package as a job, it failed every time. The error was: "The AcquireConnection method call to the connection manager 'ConnectionName' failed with error code 0xC0202009€?.
We tried everything to fix this, but nothing worked. Finally we found that when manually running the package, SQL Management Studio was calling the 32bit version of dtexec.exe, while the Agent calls the 64bit version of dtexec.exe. The fix is to not use the "SQL Server Integration Services Package" type in the job step, but use "Operating system (CmdExec)" type. Then in the command box, call the 32bit (x86) version of dtexec.exe.
I have user XY in SQL 05. I would like to find all stored procedures, where user XY has permission for executing. Is there any way to find it than look in every stored procedure?
I'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 have an application that uses Integrated Windows authentication. My Web.config looks like below <add key="dbconnection" value=" server=XXX;Initial Catalog=XXX;persist security info=False;Integrated Security=SSPI;Pooling=true" /> When users try to access my application, they get the below error: Execute permission denied on object 'SprocName', database 'DBNAME',Owner,'dbo' The Only way I could get rid off the error is if I set DBO permissions for the user group on the databse. Can someone suggest how to set up a security group with the ‘necessary’ permissions on SQL SERVER (ie read,write execute Sproc etc) and not too many extra ones, like DBO. Thanks,
I have a web application using Stored Procedure (SP). I see that there's a SP taking long time to execute. I try to capture it by Profiler Tool, and find out that with the same SP on the same db with the same parameter. The duration of executing by my web app is far bigger than the duration of executing on SQl server management studio - query window
Please see the image through this url http://kyxao.net/127/ExecutionProblem.png
Hi,I have a web application using Stored Procedure (SP). I see that there's a SP taking long time to execute. I try to capture it by Profiler Tool, and find out that with the same SP on the same db with the same parameter. The duration of executing by my web app is far bigger than the duration of executing on SQl server management studio - query windowPlease see the image attached http://kyxao.net/127/ExecutionProblem.png Any ideas for this issue?Thanks a lot Jalijack
Hi all,I am facing an unusual issue here. I have a stored procedure, that return different set of result when I execute it from .NET component compare to when I execute it from SQL Management Studio. But as soon as I recompile the stored procedure, both will return the same results.This started to really annoying me, any thoughts or solution? Thanks very much guys
SQL Server 2005 anomoly? In SQL Server Management Studio I granted specific permissions to user "A" to do Select, Insert, Update, Delete on Table "B" - When I logged on as User "A" and attempted the Insert imto table "B" I got the following error: "Insert Permission Denied on Table B, Database C, Schema dbo" Is this a problem with the dbo schema?
Then I went back and created a stored proccedure "D" with the exact same Insert statement inside the procedure. I granted User "A" execute permission on the stored procedure "D". I then logged on as User A and executed Stored Procedure "D". No Problem - stored procedure executed fine with the Insert. I attempted the Insert statement again - straight SQL - as User "A" and got the same error as above ("Insert Permission Denied.....") Strange behavior - cannot do a SQL. Insert even though user has permissions but can execute a store procedure with the same Insert statement. What gives?
Hi,It may sound funny but it is true. I have 2 version of same procedure, 1 is named as "update_aggre" other named as "update_aggre_2" .if I run these procedures using sql jobs the 1st procedure takes 12 seconds and the 2nd takes 2 second. I am stil surprise why is that both of them have same code.Any ideas please?and also I need to have lock mechanism within a procedure so that if some one is calling a procedure which is already called by some one ans is stil working on it the second user shld not be able to overwrite the existing data untill the first one is finished.TIAAmit
The error message is [Microsoft SQL-DMO (ODBC SQLState :28000}] Error 18456:[Microsoft]ODBC SQL Server Driver][SQL Server]Login failed for user 'Domainuser'. Process Exit Code 1. The step failed.
The user is a domain account and already in local administrator group. It also starts up both Sql server & Sql server agent. It can run the same job on another server. I have compared the set up and can't find any differences.
Hi, I have a DTS package that runs correctly when executed manually, but when I schedule a job via the package, the job begins executing and nevers seems to complete the run. The Package runs in less that 1 minute, but the job sticks on executing and does not complete. I have to cancel, any ideas?
I have 12 scheduled daily jobs, all the jobs are depending on one job.I want to run rest all the jobs if and only if the Job#1 gets success.Now all are running independently.Is there a way to force the sequence by using SQL. Thanks!
If we have several jobs running several times daily,do we have to do any clean-up with the logs/job history so that they don't run into any problem later?Will it be o.k if we do not clear off the history frequently?
Hi all, My firm has about 15 SQL Servers. 5 of them are still 6.5 and the other 10 are 7.0. I have noticed that the jobs I have setup to perform maintenance tasks, backups etc. almost never fail in 7.0. Similar tasks routinely fail on the 6.5 servers.
So I did a test. I deleted a database in 7.0 and ran a backup job. Although the log for the job said that it couldn't find the db it still said the job was successful. In 6.5 if you try to run a job on a non-existent db it fails. What's going on in 7.0? What has to happen for a SQL Server agent job to fail. This seems like an awfully dangerous new "feature".
If anyone could shed light on this I would appreciate it.
How do we add DTS pakages to a scheduled job ? Ex: Lets say i have 2 DTS pakages One has got to run immediately after the other. >Now i create a schedule for the main DTS pakage.
>Once i create a schedule, It goes into Jobs as a Scheduled job.
>Now in the propertied part of the first DTS job i need to add a second DTS as Step2, mentioning that it should run after the First DTS.
We had some jobs in Sql server 7.0 which ran together at the same time. Now we have moved to sql 2000 and when we run those jobs together again they just sit up(keep on going without doing anything) and do nothing.I have monitored that there is no Blocking or any kind of Performance Overload.
These jobs run fine when they are executed Individually in Sql 2000
hey guys!! can someone tell me, what are jobs on MS SQL? and what is a job scheduler? how do it function? what are the processes involved? and additional information about this stuffs.. thanks..really need it.. tnx tnx..
p.s. if your wondering why i asked the questions here..because it's really hard to search the meaning of it in the net..i hope you guys could help me.. tnx
Thanks for the help with moving jobs from one server to another.
Now that I have moved them, they now fail each and all. I have copied the script and saved them as vbs files and placed them in a folder on the server and ran them successfully. I think it has something to do with the rights, but I don't know what. Could someone shed some light on possible causes?
I am trying to run a job on Multiple SQL Servers in a domain.I am setting the job on my system,but the Radio button "Target Multiple Servers" is disabled.How do I enable the radio button "Target Multiple Servers". Please let me know if this is possible.
I can handle the setting up a SQL Job/DTS Package.
What I have is SQL Statement I need to run that creates a txt file Renames file to AUX_Export_020507.txt then zips that text file and Name it AUX_Export_020507.zip. Then move the zip file to a FTP directory. I would like to get email after it runs also.
This issue I am having is the Part that zips the file Renames the text file and zip file to add the current date on end like I have above and move it to a FTP directy..
The old days we would creat an autoex.bat file to move and rename.
I want to create a job which will basically fetch the information from the system. I mean job will fetch the following information about disk available in the system.
1) Drive 2) Total Size 3) Available Space 4) %free space
Suppose I have 3 drives d,h,i The information should look like this
Drive Totalsize Available Space %free space H 2 Gb 1 GB 50%