Additional SQL Server features and topics not covered by specific categories
No columns were deselected or dropped.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We have transactional replication and when I generated script to create or enable the components, I noticed that for just one table the @vertical_partition was set to True for sp_addarticle, followed by sp_articlecolumn calls for each of the columns in the table. There is no partitioning defined for the table so why is it doing this?
SQL 2019 SE 64bit CU9 running on an Azure VM
Additional SQL Server features and topics not covered by specific categories
No columns were deselected or dropped.
Hi @Michael MacGregor ,
Did you drop/deselect one column from the article? Could you check in the article properties if there are columns which are deselected/not published?
Check if this similar thread could help you.
That doesn't help explain why it has been set in the generated script.
Hi @Michael MacGregor ,
'@vertical_partition' enables or disables column filtering on a table article.
false indicates there is no vertical filtering and publishes all columns.
true clears all columns except the declared primary key, nullable columns with no default, and unique key columns. Columns are added using sp_articlecolumn.
If the response is helpful, please click "Accept Answer" and upvote it, as this could help other community members looking for similar thread.