Replication frustration: Adding article does not create the table on subscriber

-
Working with the SQL Server replication is not a great pleasure.
Working with the SQL Server replication replication is not a great pleasure, when all is working as you expect.
Working with the SQL Server replication replication is not a great pleasure at all, when something is not working and there is no documentation.
Working with the SQL Server replication replication is not a great pleasure at all, when something is documented but simply is not working.
We have been fighting with some really weird behavior during the last few month. This is a basic transaction replication feature: adding article on the table supposed to create table on subscriber. It's working on some servers. And it doesn't work on some servers. Regardless the SQL Server version, whether it is SQL Server 2005 sp4 or SQL 2008 R2 sp1. The most amazing thing is that it's reproducible and not working on production environment ONLY. We could never reproduce it on the QA servers.
The scenario is pretty easy.

• Add a new article for a table
• Create subscriptions to it
• Start snapshot agent

On most subscribers at this moment the table gets created. Except some subscribers where it's not getting created. Subscribers don't get the snapshot. At all.
Getting into lower level, the new article and subscription exist in the distribution database. In the MSSubscriptions table we can see the subscriptions with status 1 before the snapshot is started. After the snapshot is completed the status is changed to 3 for a few seconds and then to 2. The snapshot scripts don't run on the subscriber and therefore the table not created.
When an inserts starting to flow into the published table, they get replicated to all subscribers and fail with the following error - "Invalid object name tablename".
According to the statuses of MSSubscriptions table:
0 - Inactive
1 - Subscribed
2 - Active
3 - Snapshot interrupted (undocumented)

We have created a support call to MS but, because we don't have premier support, the issue have got VERY LOW priority.

If you have experienced any similar behavior and have any solution to it, drop some comments here.

Comments

Post a Comment

Popular posts from this blog

SQL Awesomeness: Finding a QUALIFY query clause in the depths of the database ocean

-
Image
After so many years of writing SQL queries, I cannot believe I never came across a QUALIFY query clause. It feels like discovering a treasure in the depths of the database ocean. Even ChatGPT was not aware of it! QUALIFY query clause was invented by Teradata and is not a part of SQL Standart but apparently, multiple database vendors are supporting it, for instance, Snowflake and Databricks. QUALIFY clause solves the challenge when applying a window function as a query filter. SQL Standart and most database vendors will not allow to run of a window function as a part of a WHERE clause because window functions get evaluated after the HAVING clause. We typically create a CTE or subquery adding a window function to be able to filter on a it at a later query stage. Here is an example of how you can use QUALIFY to piece-of-cake filter on the window function.  I will use the Snowflake database, as an example. Let us consider that we have a list of queries and we need to find the last query ex
Read more

Look back and realize how far you came

-
Image
It appeared out of nowhere while I was having a strong argument with the ton of dust that had taken over my computer room. My former favourite book, "Advanced Transact-SQL for SQL server 2000" brought an upset look to my face, the one I usually get from our NetApp admin. He usually gives me such a look when I ask him for more disk space. At the time of SQL 2000 there were far less good SQL books available than today and amazing SQL programming tricks were living on Itzik’s book pages; and, similar to the Rubeus Hagrid’s “The Monster Book of Monsters” it attacked anyone who attempted to open it, unleashing wild and exciting brilliant ideas. Nowadays there are a lot of SQL books but not all of them are worth reading. Some of them should be strongly avoided and if you touch them you should immediately wash your hands and have a drink or three. A few month ago I was asked to technically review some new SQL Server book. Reading their missleading claims of how the optim
Read more

The Greatest Reasons to use or not to use a Centralized Data Access Architecture

-
Image
When developing a modern Data Platform Layer, one of the main decisions is whether to opt for centralized or decentralized data access architecture.  There is no “one-fits-all” solution, both have advantages and disadvantages. A Centralized Data Access Architecture would usually mean duplicating data from the operational layer into the analytical layer and applying various transformations to data to support and speed up data analytics. Operational online transaction processing Layer , where all microservices and their operational databases are located. Analytical Data Layer , where we would have data lakes that support data Scientists' work and a data warehouse, that supports Business Intelligence. Transformations, ETL or ELT data pipelines , which are moving data from the operational layer into the analytical layer. I f we opt for a Centralized Data Access architecture, what would be the benefits and the drawbacks? CONSISTENCY : consolidating data into a central location can
Read more