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,457 reads
The first article in this Stairway Series makes the case for test-driven development.
2023-10-15 (first published: 2014-12-31)
11,457 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)
12,197 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,963 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)
38,035 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
14,860 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,521 reads
The final level of this Stairway takes you through how to identify and fix common errors.
2012-04-18
14,876 reads
Introducing the replication monitor and how to use it to monitor replication health. It also introduces tracer tokens.
2012-03-21
9,757 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
11,016 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,333 reads
By Steve Jones
I needed to back up a PostgreSQL database as a part of the repro...
By James Serra
There are three Azure SQL products with so many different deployment options, service tiers,...
By Steve Jones
I hosted this month’s T-SQL Tuesday party with my invitation asking about tracking permissions....
I need some guidance on choosing data types and lengths for columns in my...
Hi all, First I want to ask just a generic question. Does RLS in...
Reading the Microsoft documentation it says SQL2019 STANDARD EDITION has a max memory of...
I have this data in a table?
CatIDCatName 3MonitorsWhat is returned when I run this code?
SELECT CHOOSE(catid, 'Laptops', 'PCs') FROM dbo.Categories AS cSee possible answers