A Failed Jobs Monitoring System
One DBA's tale of how to monitor jobs for failure and ensure that the DBA is alerted to the fact that there is a problem. (from Feb 2008)
2017-02-02 (first published: 2008-02-05)
23,274 reads
One DBA's tale of how to monitor jobs for failure and ensure that the DBA is alerted to the fact that there is a problem. (from Feb 2008)
2017-02-02 (first published: 2008-02-05)
23,274 reads
2009-04-01
5,203 reads
What are some of the on-call duties a DBA must perform? TJay Belt talks about them in this new article.
2008-10-27
6,273 reads
Tjay Belt brings us a quick and easy DR solution that might provide you some protection if you don't have a DR plan and want some lessons learned in this area.
2008-07-31
8,322 reads
Tjay Belt brings us a story of how auditing was actually implemented and a discussion of why particular decisions were made.
2008-06-11
9,077 reads
2008-03-27
5,106 reads
This will report all backup activity for all databases, sorted by date, so you see the last backup activity first. You can filter this one by a db name as well, and only see the backup info for said database.
2002-03-07
807 reads
This will get the last date a database was backuped. It allows you to report this date on all databases on a server, or pass in a db name, and it'll report the date that db was last backed up
2002-03-07
448 reads
spAddField is the proc I use to add all fields to the db in our upgrade scripts. With this proc, you pass it the tablename, fieldname, datatype, and null or not null. This will call spGetFieldsExists and see if the fields exists or not. If it does, spAddField will drop that column. Then it readds […]
2002-03-05
228 reads
spDropField does exactly the opposite of spAddField. It checks for existence, then drops it, if it does exist.
2002-03-05
147 reads
By Steve Jones
Superheroes and saints never make art. Only imperfect beings can make art because art...
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,...
Hi, in a simple oledb source->derived column->oledb destination data flow, 2 of my...
hi, i noticed the sqlhealth extended event is on by default , and it...
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