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.
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?
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%
I already learned SQL by reading "Head First SQL" book (which uses MySQL). I also know how to use Excel(using basic function and creating pivot table.) However, I noticed that many available jobs require Microsoft SQL Server 2005 and also using SQL with Excel. Now, I am thinking to learn SQL Server 2005 Express Edition because it is free! I would really appreciate if anyone who has been working in industry give me some suggestions about what is the best way to learn SQL Sever 2005? or does it worth to learn? or is it hard to learn? Can you recommend good book or website for learning SQL Server 2005 Express Edition. Thanks!
How is it possible to schedule a job to run every 40 seconds. It seems every 1 minute is the shortest time available in the job properties for scheduling a job. Thanks
Is there anyway(trigger) so nobody can delete the jobs in SQL Server?Actually we have 4 people who has SYSADMIN rights in that server and just wanna track out.No information is recorded in error logs and application log.
I have scheduled a T-SQL job that runs every morning using Enterprise Manager. Now I want to change the SELECT and UPDATE statements that this job runs, but I can't find anywhere to edit a job that has already been scheduled. Any help would be appreciated.
I have moved my database recently from a NT server to a Windows 2000 server, both running SQL 7.0 I have a couple of jobs that sometimes, work, sometimes not, the problem it tells me is that it cannot find the file specified, I run the job from enterprise manager and it runs just fine, it'll run here and there but it still fails frequently. Any suggestions on what to check? Thanks.
I want to know if there is anyway to distribute jobs to a non system administrator. In other words do they have to have System Admin rights, to be able to modify a job and run the job.
I would like to move over all of my DTS packages and corresponding jobs onto another MS SQL server machine. The problem that I have is that I haven't been able to find any straight-forward info on how to script up these jobs, move them onto another machine and execute them. I have scanned through previous posts written by people with the same problem, but every response is simply "script up the jobs and move them onto another server." Maybe I'm missing something, but how "exactly" do I get a job to show up on this destination machine in EM, in the management/sql server agent/jobs folder. I did the jobs/all tasks/script job... but then what? I saved it on this destination machine, but am unclear as what to do next. The MS SQL Server Administrators companion book is of no help on this subject, and I do not understand how this simple task can be so confusing and is not documented. Any help would be greatly appreciated. Thanks in advance! TB
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?
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.
I have a couple of jobs set on 1 server. I want these jobs to be transferred, or rather copied to another server. Is there a method by which I can just point these jobs to another server, without having to manually create them again ??
I am trying to create a SQL Job which will report on another job which hasn't finished within its normal completion time. I schedule the new job late enough after the first job that the first should have finished by then.
I would like to have just queried msdb..sysjobhistory.run_status. However, this seems to only report on job STEP status - and after the step is finished! It is always showing run status = 1 (Complete).
Does anyone know the base meta-data table and column I could query? Enterprise Manager shows the current status as running and I want to know where it gets that.
If it is still running, I will raise an error to notify our support group, etc.
PS: My job steps include a combination of DTSRun commands and TSQL commands. I don't think the flavour of commands should matter...
