Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Campese1981
Starting Member
2 Posts |
 Posted - 2008-07-03 : 13:30:25
|
Hi all.I've done a merge replication in Sql Server 2005.The database has a publish table with 107 columns and in my PDA only appears 99 columns in the replicated same table. This is a problem because my application needs needn't the 107 columns to work. But needs one of the missed colums.Anyone knows why is it? How can I solve this problem?Thanks. |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-07-03 : 13:33:21
|
| what?107 columns. you need to Normalize so that your replication performance is efficient. Did you set any column in Publisher with NOT FOR REPLICATION ? |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-07-04 : 00:18:31
|
| Not for replication applys to identity column only, other than constarints and trigger. |
|
|
|
Campese1981
Starting Member
2 Posts |
Posted - 2008-07-04 : 04:07:06
|
| How can I normalize that? I only need 12 columns but I'm not allowed to drop any column of the tables by the assistant. I don't know any other way to do that.I tried to find any column with the parameter NOT FOR REPLICATION in "yes" value. But all of them are with the parameter in "no" value.The table has columns with trigger, constraint or are identity. But no one has the NOT FOR REPLICATION value in true so the problem must be other I think.Thanks for the answers. |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-07-04 : 19:49:31
|
| You can set column filter for article in replication. |
|
|
|
|
|
|
Merge replication. Missing columns in table.