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,719 reads
The first article in this Stairway Series makes the case for test-driven development.
2023-10-15 (first published: 2014-12-31)
11,719 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,587 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)
19,517 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,616 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
15,843 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,818 reads
The final level of this Stairway takes you through how to identify and fix common errors.
2012-04-18
15,283 reads
Introducing the replication monitor and how to use it to monitor replication health. It also introduces tracer tokens.
2012-03-21
10,048 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,232 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,479 reads
By Steve Jones
I use ConEmu for my terminal interface. I’m still on Windows 10 at home,...
Creating a Fabric workspace takes about 30 seconds. Restructuring workspaces after people have built...
By Steve Jones
It’s a small change, but a handy one. Flyway Desktop (FWD) now includes the...
Comments posted to this topic are about the item Adding new column with DEFAULT...
Comments posted to this topic are about the item Advanced Deployment Scenarios: Stairway to...
Comments posted to this topic are about the item You Need a DBA Pipeline
Which number did the two COUNT(*) return:
DROP TABLE IF EXISTS #tmp CREATE TABLE #tmp (id INT NOT NULL) INSERT INTO #tmp (id) SELECT gs.value FROM GENERATE_SERIES(1, 5) AS gs ALTER TABLE #tmp ADD my_value INT NOT NULL CONSTRAINT df_tmp_my_value DEFAULT 1 SELECT COUNT(*) FROM #tmp AS t WHERE my_value = 1 ALTER TABLE #tmp DROP CONSTRAINT df_tmp_my_value ALTER TABLE #tmp ADD CONSTRAINT df_tmp_my_value DEFAULT 2 FOR my_value SELECT COUNT(*) FROM #tmp AS t WHERE my_value = 1See possible answers