High Availability (HA)

SQLServerCentral Article

High Availability (DR) Using SQL Server 2005 Transactional Replication

  • Article

One of the four high availability technologies in SQL Server is replication, though this can be very cumbersome to setup and get working. Longtime author Paul Ibison looks at how this has changed from SQL Server 2000 to 2005 and what you should consider before setting this up.

(9)

You rated this post out of 5. Change rating

2008-04-17

7,791 reads

SQLServerCentral Article

Mirrored Backups

  • Article

One very interesting new feature in SQL Server 2005 is the ability to run backups to multiple locations, ensuring you have a second copy of the backup file if your first one were to be corrupted. SQL Server expert Andy Warren takes a look at how this feature works and the implications of using it.

(1)

You rated this post out of 5. Change rating

2008-05-12 (first published: )

8,479 reads

Blogs

Prime Day Recommendations

By

It’s Prime Day. A few of my recommendations, since I want to do some...

Fabric for Operational Reporting & SQL Endpoint Trap

By

With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...

Crawl, Walk, Run with Agentic Development of Power BI Assets

By

If you’ve been watching AI roll through the data community and thinking, “this seems...

Read the latest Blogs

Forums

SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About

By Terry Jago

Comments posted to this topic are about the item SQL Art, Part 4: Happy...

Concurrency and Baseline Control: Level 5 of the Stairway to Reliable Database Deployments

By Massimo Preitano

Comments posted to this topic are about the item Concurrency and Baseline Control: Level...

Spending Time in the Office

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Spending Time in the Office

Visit the forum

Question of the Day

Multiple Values Inserted

I have this code on SQL Server 2022. What happens when it runs all at once?

DROP TABLE IF EXISTS dbo.Commission
GO
CREATE TABLE dbo.Commission
(id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY
, salesperson VARCHAR(20)
, commission VARCHAR(20)
)
GO
INSERT dbo.Commission
( salesperson, commission)
VALUES
( 'Brian', 12 ),
( 'Brian', 'None' )
GO
 

See possible answers