2009-11-26
3,064 reads
2009-11-26
3,064 reads
This article shows ways of getting feedback to your users when running a SQL Server agent job from an ASP.NET page
2009-09-16
9,386 reads
It is often the case in large DBA teams where multiple DBAs can administer the same SQL Servers and it is not apparent to one DBA the importance of some of the jobs to another DBA. In this tip I show how you can be alerted of these changes.
2009-08-13
3,880 reads
Checking for SQL Server Agent jobs and their status is part of your daily task as a DBA. How do we use Windows PowerShell to check for SQL Server Agent jobs?
2009-07-28
3,655 reads
You may have a number of jobs scheduled and often there is the need to analyze the data to see which jobs are taking a long time or which job steps are taking a long time. As you add more jobs and overhead to the server these times become even more critical and analyzing the data is key.
2009-05-29
3,827 reads
Here is a stored procedure that start a job, and then waits until the jobs is finished
2009-06-02 (first published: 2009-05-14)
1,064 reads
In this tip I provide a script with a few parameters that need to be setup to configure and turn on both of these features.
2009-05-11
4,009 reads
This article introduces the reader to Powershell. The application that it demonstrates is one that monitors SQL Server Agent to make sure it is running.
2009-03-31
3,061 reads
In a recent blog post, SQL Server expert Denny Cherry discusses adding a user interface to his Standalone SQL Agent, a replacement for the SQL Server Agent service.
2009-03-17
1,896 reads
2009-04-10 (first published: 2009-03-13)
2,175 reads
By Steve Jones
It’s a small change, but a handy one. Flyway Desktop (FWD) now includes the...
By Steve Jones
Software is hard. While I love our Lucid Gravity, I realize that they are...
By James Serra
Making Data AI-Ready, Part 2 (This is the second article in a three-part series...
The NABL-accredited calibration lab at Fare Labs offers the best calibration services in India...
Hi everyone, I'm hoping some of the longtime SQL Server professionals here might be...
Comments posted to this topic are about the item Checking the Error Log II
What is the reason I should change my old code that uses xp_readerrorlog?
See possible answers