SQL Server Agent is a Microsoft Windows service that allows a DBA to automate administrative tasks. SQL Server Agent can run jobs, monitor SQL Server, and process alerts. The SQL Server Agent service must be running before any jobs scheduled to execute automatically can be run
2020-02-19 (first published: 2011-02-17)
21,804 reads
Examines the database mail system configuration in depth. You will learn how to configure database mail to work with SMTP mail systems, and get some troubleshooting tips.
2018-01-10 (first published: 2011-07-28)
6,932 reads
How to be notified when a job succeeds or fails, or be notified when a SQL Server performance condition is met.
2017-12-13 (first published: 2011-06-29)
10,599 reads
SQL Server Agent jobs are made up of a series of one or more Job Steps. A job step is assigned to a specific job subsystem, which identifies the kind of work the job step is going to perform. Each job step runs in a separate security context, although each job also has an owner that determines who can modify the job.
2017-10-11 (first published: 2011-02-17)
10,126 reads
Security is a confusing topic to many, especially when it comes to understanding what rights are needed to monitor and use SQL Server Agent. This article will examine the rights and roles used for SQL Server Agent, as well as the security context requirements for jobs.
2014-04-16 (first published: 2012-01-11)
10,897 reads
Examines the scale-out capabilities of SQL Server Agent, using the MSX/TSX subsystem. This capability allows you to run jobs on multiple systems and consolidate the job results/history onto a single server.
2012-02-22
10,442 reads
How maintenance plans are used as SQL Server Agent jobs to automate standard system tasks. This article will also lay out some suggested jobs that should be on virtually all SQL Server systems.
2012-02-15
7,043 reads
Examines the proxy subsystem, which allows job steps to impersonate another user account in order to perform tasks as a user other than the SQL Server Agent service account. This is especially useful when you want jobs to run as lower privileged users of your SQL Server.
2012-01-25
13,057 reads
One common usage of SQL Server Agent historically has been the ability to shell out to the operating system and run command line programs, using SQL Server Agent primarily as a job scheduler. This article will examine the pros and cons of using the SQL Server 2008 & 2008 R2 Powershell subsystem versus the CmdExec subsystem to perform tasks in the Operating System.
2011-12-28
7,039 reads
The Job Activity Monitor is the system administration tool to run jobs, view job history, and enable/disable jobs. This article will also review some of the stored procedures run by the Job Activity Monitor that you can also use directly to do your own custom job monitoring.
2011-12-07
6,361 reads
By Steve Jones
semaphorism – n. a conversational hint that you have something personal to say on...
This week I was at PASS Data Community Summit in Seattle, and I attended...
By James Serra
(This is the third post in a three-part series on how AI is changing...
Comments posted to this topic are about the item Pay for Performance, which is...
Telp/Wa 628218200203 Jl. Jend. Sudirman No.49-51, Terban, Kec. Gondokusuman, Kota Yogyakarta, Daerah Istimewa Yogyakarta...
Telp/Wa 628218200233 Jl. MT. Haryono No.2, Jengglong Timur, Purwodadi, Kec. Purwodadi, Kabupaten Grobogan, Jawa...
I have a table, dbo.bittest, where I am testing an application response. This has this structure:
CREATE TABLE [dbo].[BitTest] ( [insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()), [a] [bit] NULL ) ON [PRIMARY] GOMy application runs this code:
INSERT dbo.BitTest
(
insertdate,
a
)
VALUES
(DEFAULT, 'true')
GO
See possible answers