I want to temporarily use a Log Shipped secondary database for Read Only operations, but Log Shipping was not configured for read only operations. I don't want to reconfigure Log Shipping, so is there a way to do this without redoing Log Shipping.
2015-07-07
3,197 reads
The code in this tip will demonstrate how to continue SQL Server Log Shipping after a file has been added to the primary SQL Server database.
2014-02-05
2,846 reads
Using Log Shipping? Looking for a more automated way to fail over during a disaster? Read on...
2013-12-03
1,619 reads
When pushing a major release to a large production database, you want to know that you'll be able to rollback changes if the need arises. These are some simple steps which we can follow to ensure that we don't have to reconfigure log shipping all over again thereby saving time and ensuring systems are not affected when rolling back changes.
2013-10-23
3,892 reads
Freshly minted MCM Wayne Sheffield fills a log shipping crack that could otherwise cause you to re-initialize your log shipping.
2024-10-11 (first published: 2013-06-06)
5,814 reads
This tip I will explains a step-by-step method to perform the SQL Server Log Shipping migration.
2013-03-04
2,547 reads
2012-12-05
1,838 reads
I have a requirement to add the Log Shipping Monitor for an existing installation. I have heard you can only complete this by rebuilding the Log Shipping infrastructure. Is that true? Are there any other options? In this tip I will explain how we can add the Log Shipping monitor to a SQL Server 2005, 2008, 2008 R2 or 2012 environment without rebuilding the Log Shipping installation.
2012-12-05
2,688 reads
Delete Log-shipping Tlog backup files which are already restored onto Secondary Server.
2012-06-28 (first published: 2012-06-06)
707 reads
This topic explains the log shipping if the primary database is suspected or corrupted and how you can convert the secondary database into primary database.
2012-04-27 (first published: 2012-03-31)
1,009 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