Setup:
SQL Server 2005 -> Merge pull subscription via HTTPS
Tables:
1) StudioType (Id [tinyint] PK, Name [nvarchar])
2) Studio (Id [int] PK, StudioTypeId [tinyint] FK, ComputerName [nvarchar]...)
3) etc
Remarks:
I have a single parametrized filter (for the entire database) on article
Studio like so -> ComputerName=HOST_NAME().
@.partition_option for Studio is obviously 3.
I have a join filter between Studio and StudioType like so:
@.filtername = N'StudioTypes_Studios', @.join_articlename = N'Studios',
@.join_filterclause = N'[StudioTypes].[Id] = [Studios].[StudioTypeId]',
@.join_unique_key = 0
Basically I have multiple Studios that belong to the same StudioType
Question:
Which @.partition_option can/should I use on article StudioType?
I know 0 works, but can I use 2 instead?
In order to save you guys some time searching, this page should contain all
the info required:
http://technet.microsoft.com/en-us/library/ms152478.aspx
But I have a problem undestanding whether the join filter creates
overlapping or nonoverlapping partitions...
Also, could somebody answer this question as well:
Does the following - "The Subscriber cannot update columns referenced in a
parameterized filter." - also apply to columns used in joins or does it only
apply to the parametrized filter column (ComputerName)?
I'm guessing not...
Ok, I figured out that I can't use partition_option 2, because the rows are
indeed overlapping.
So I can only use partition_option either 0 or 1.
But it would still be nice if somebody can answer the last question in my
post...
"mommi" wrote:
> Setup:
> SQL Server 2005 -> Merge pull subscription via HTTPS
> Tables:
> 1) StudioType (Id [tinyint] PK, Name [nvarchar])
> 2) Studio (Id [int] PK, StudioTypeId [tinyint] FK, ComputerName [nvarchar]...)
> 3) etc
> Remarks:
> I have a single parametrized filter (for the entire database) on article
> Studio like so -> ComputerName=HOST_NAME().
> @.partition_option for Studio is obviously 3.
> I have a join filter between Studio and StudioType like so:
> @.filtername = N'StudioTypes_Studios', @.join_articlename = N'Studios',
> @.join_filterclause = N'[StudioTypes].[Id] = [Studios].[StudioTypeId]',
> @.join_unique_key = 0
> Basically I have multiple Studios that belong to the same StudioType
> Question:
> Which @.partition_option can/should I use on article StudioType?
> I know 0 works, but can I use 2 instead?
>
> In order to save you guys some time searching, this page should contain all
> the info required:
> http://technet.microsoft.com/en-us/library/ms152478.aspx
> But I have a problem undestanding whether the join filter creates
> overlapping or nonoverlapping partitions...
> Also, could somebody answer this question as well:
> Does the following - "The Subscriber cannot update columns referenced in a
> parameterized filter." - also apply to columns used in joins or does it only
> apply to the parametrized filter column (ComputerName)?
> I'm guessing not...
Monday, March 19, 2012
merge replication partition options
Labels:
database,
httpstables1,
int,
merge,
microsoft,
mysql,
nvarchar,
oracle,
partition,
pull,
replication,
server,
setupsql,
sql,
studio,
studiotype,
subscription,
tinyint,
via
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment