February 4, 2013 at 9:11 am
Hello,
I have a transactional publication with hundreds of articles. Each article is publishing all of its columns, but when I ask SQL Server to generate the script for this publication the @vertical_partition parameter is configured as true and the colums are added using the sp_articlecolumn stored procedure. I never had a vertical partition in any of my tables.
My question is: why is SQL Server configuring this parameter as true if I am not using vertical partitions? I tried to simulate this behavior in another database, but I could not simulate. In this simulation I confiured an article to publishing only some columns. Then I generated the script and it was configured to use vertical partition as expected. After this test I configured the article to publish all columns again and recreated the script and it was configured to not use vertical partition as expected.
I do not understand what is causing this behavior in this publication. Does anyone know?
-George
February 4, 2013 at 9:50 am
I found the cause. All my tables have a timestamp column and this column is causing the script to be generated as vertical partitions would be in use.
February 4, 2013 at 9:56 am
Thanks for the update. I hadn't noticed that, but it's good to see.
Did you determine this by testing with a an article that doesn't have a timestamp or finding a one in your system that doesn't have one?
February 4, 2013 at 10:26 am
Hi Steve,
I started with a very simple test table and then I added columns using a "wrong" table as reference.
I did some research at Microsoft web site and did not find any documention regarding this behavior.
-George
February 4, 2013 at 10:55 am
Thanks, George. I'll add it to my list to look into.
One note, if you have a place you think this should be noted, you can file a documentation bug at connect.microsoft.com
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply