Log Shipping

External Article

Steps to rollback database changes without impacting SQL Server Log Shipping

  • Article

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

External Article

Steps to add Log Shipping monitor into an existing SQL Server

  • Article

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

Blogs

Using Customer Docker Compose File Names

By

As I use containers more and more to run various things, I decided I...

SQL Server Failover Cluster Instances

By

Old Reliable Still Matters If you’ve been around SQL Server for a while, you’ve...

How to: Regain SysAdmin Access to a SQL Server Instance Without the SA Password

By

Hello, reader! Today, I’m going to walk you through a scenario that many DBAs...

Read the latest Blogs

Forums

SQL Server authentication vs. Trusted connection

By Rod at work

I maintain an application written years ago, where the database is on a Windows...

Handling Engagement Rings & Wedding Band

By iBling Jewels

I’m working on a jewelry e-commerce project and need advice on designing an efficient...

The Duplicate Cursor

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Duplicate Cursor

Visit the forum

Question of the Day

The Duplicate Cursor

Can I run this code:

DECLARE ANewTable CURSOR FOR 
SELECT * FROM ANewTable

See possible answers