2025-05-12
272 reads
2025-05-12
272 reads
2025-04-28
400 reads
This article shows how we were able to migrate a TB size database to new storage with minimal downtime.
2024-01-01 (first published: 2021-02-24)
7,823 reads
2020-12-10
417 reads
2018-06-28
866 reads
Get Logshipping report only when secondary is more than certain time behind Primary.
2017-11-14 (first published: 2017-10-27)
474 reads
2016-05-11
4,469 reads
How to move a log shipping database to a new monitor server without removing and rebuilding the log shipping setup.
2016-04-04
2,500 reads
When you’re reading from a log shipped secondary, you want the duration of restores to be as short as possible. The sproc provided switches the restores to “NORECOVERY” mode, and then switch back to “STANDBY” at the end of the process.
2015-12-11 (first published: 2015-11-23)
3,065 reads
A look at a SQL script solution that can help you easily fail over and back from log shipping scenarios.
2018-12-14 (first published: 2015-09-08)
3,707 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,...
Comments posted to this topic are about the item The AI Bubble and the...
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...
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