Stairway to SQL Server Automated Database Testing Level 1: Why You Need TDD
The first article in this Stairway Series makes the case for test-driven development.
2023-10-15 (first published: 2014-12-31)
11,190 reads
The first article in this Stairway Series makes the case for test-driven development.
2023-10-15 (first published: 2014-12-31)
11,190 reads
The Publisher is the database where all
replicated data originates. Each Publisher can have multiple publications
defined within it. Each publication contains a set of articles that all need to
reside in a single database. Each article corresponds to all or part of a single
database object. A single database object can map to an article in more than one
publication.
2023-01-04 (first published: 2013-11-20)
11,962 reads
In this Stairway, Sebastian will be covering the details of SQL Server transactional and merge replication, from understanding the basic terminology and methodology of setting up replication, to describing how it works and how the basic replication processes can be monitored.
2022-12-28 (first published: 2013-11-13)
18,652 reads
In this Stairway, Sebastian will be covering the details of SQL Server transactional and merge replication, from understanding the basic terminology and methodology of setting up replication, to describing how it works and how the basic replication processes can be monitored.
2019-08-14 (first published: 2012-12-26)
37,520 reads
The Subscriber is the server where all the changes that are published by replication get delivered to. Every publication needs to have at least one subscriber, but a publication can have many subscribers. This level assumes that you have followed the first three levels and that you have a publication set up, to which you can subscribe.
2013-12-11
13,856 reads
Many of my clients need to make data that lives on one server available on another server. There are many reasons for such a requirement. You might want to speed up cross-server queries by providing a local copy of the data. Or you might want to make the data available to resource intensive reporting queries without impacting the OLTP load, maybe even with an intentional delay so you're always reporting against complete days only. Finally, you might be looking to implement high availability. In all these situations, SQL Server Replication is a viable option to look at when planning for the implementation of such a requirement.
2013-09-30
6,492 reads
The final level of this Stairway takes you through how to identify and fix common errors.
2012-04-18
14,575 reads
Introducing the replication monitor and how to use it to monitor replication health. It also introduces tracer tokens.
2012-03-21
9,519 reads
How merge replication works, including the impact on the published database. The merge agent, different conflict situations and their resolutions are introduced.
2012-03-02
10,791 reads
This level of the Stairway will cover the details of SQL Server transactional and merge replication, from understanding the basic terminology and methodology of setting up replication, to describing how it works and how the basic replication processes can be monitored.
2012-02-03
7,233 reads
By Chris Yates
A brief introduction to the tool and its advantages for database migrations DevOps is...
In a previous blog post we went through how to build a Docker container...
Businesses are drowning in data, but starving for insights. That's where SQL experts swoop...
select Custno, Addr1, City, Res_Phone, Bus_Phone, Fax_Phone, Marine_Phone, Pager_Phone, Other_Phone, email1, email2 from customer...
I'm only processing 50,000 records not everything from the Table where there are 250,00...
Comments posted to this topic are about the item The Marked Transaction
I want to mark a transaction in the log as a recovery point. How do I do this in my code if I use the transaction, myTran?
See possible answers