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,674 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.
2019-03-26 (first published: 2012-01-25)
12,677 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.
2019-03-26 (first published: 2012-02-15)
6,925 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.
2019-03-26 (first published: 2012-02-22)
10,195 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.
2019-03-26 (first published: 2011-02-17)
9,997 reads
How to be notified when a job succeeds or fails, or be notified when a SQL Server performance condition is met.
2019-03-26 (first published: 2011-06-29)
10,451 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.
2019-03-26 (first published: 2011-07-28)
6,830 reads
How to interpret and configure the SQL Server Agent error logs. Critical information about SQL Server Agent is sent to this error log, so knowing how to find it and how to interpret information in the log will save you valuable troubleshooting time.
2019-03-26 (first published: 2011-08-19)
8,454 reads
How to configure and optimize job steps. Topics such as process flow between steps, security, and more details of the job subsystems are examined.
2019-03-26 (first published: 2011-11-23)
7,018 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.
2019-03-26 (first published: 2011-12-07)
6,198 reads
One feature that I have been waiting for years! The new announcement around optimize...
Following on from my last post about Getting Started With KubeVirt & SQL Server,...
By DesertDBA
I haven’t posted in a while (well, not here at least since I’ve been...
hi, i noticed the sqlhealth extended event is on by default , and it...
Hi everyone, I’m looking for some guidance on a SQL Server performance issue I’ve...
Using New-AzSqlInstanceServerTrustCertificate to import a certificate and get the message New-AzSqlInstanceServerTrustCertificate: Long running operation...
I am currently working with Sql Server 2022 and AdventureWorks database. First of all, let's set the "Read Committed Snapshot" to ON:
use master; go alter database AdventureWorks set read_committed_snapshot on with no_wait; goThen, from Session 1, I execute the following code:
--Session 1 use AdventureWorks; go create table ##t1 (id int, f1 varchar(10)); go insert into ##t1 values (1, 'A');From another session, called Session 2, I open a transaction and execute the following update:
--Session 2 use AdventureWorks; go begin tran; update ##t1 set f1 = 'B' where id = 1;Now, going back to Session 1, what happens if I execute this statement?
--Session 1 select f1 from ##t1 where id = 1;See possible answers