Peer to Peer difficulty when adding a column

I'm trying to add a column to my peer to peer replication. According to the
help I've found:
Adding Columns
a.. To add a new column to a table and include that column in an existing
publication, execute ALTER TABLE <Table> ADD <Column>. By default, the
column is then replicated to all Subscribers. The column must allow NULL
values or include a default constraint.
b.. To add a new column to a table and not include that column in an
existing publication, disable the replication of schema changes, and then
execute ALTER TABLE <Table> ADD <Column>.
c.. To include an existing column in an existing publication, use
sp_articlecolumn (Transact-SQL), sp_mergearticlecolumn (Transact-SQL), or
the Publication Properties - <Publication> dialog box.
For more information, see How to: Define and Modify a Column Filter
(Replication Transact-SQL Programming) and How to: Define and Modify a
Column Filter (SQL Server Management Studio). This will require
subscriptions to be reinitialized.
d.. Adding an identity column to a published table is not supported,
because it can result in non-convergence when the column is replicated to
the Subscriber. The values in the identity column at the Publisher depend on
the order in which the rows for the affected table are physically stored.
The rows might be stored differently at the Subscriber; therefore the value
for the identity column can be different for the same rows.
However, while I am able to add the column to the publisher and it is
replicated to the subscriber, I cannot update this column at the subscriber
and have it replicate to the publisher. However when I update at the
publisher it IS pushed to the subscriber.
Outside of the new column, my updates bi-directionally work. Can someone
tell me how I can get updates on newly added columns to be bi-directional?
Thanks,
Adam P. Cassidy
Did you quiesce the system as outlined in this link?
http://msdn2.microsoft.com/en-us/library/ms147385.aspx
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Adam Patrick Cassidy" <apcassidy@.aol.com> wrote in message
news:eoBB5en4GHA.1200@.TK2MSFTNGP02.phx.gbl...
> I'm trying to add a column to my peer to peer replication. According to
> the help I've found:
> Adding Columns
> a.. To add a new column to a table and include that column in an existing
> publication, execute ALTER TABLE <Table> ADD <Column>. By default, the
> column is then replicated to all Subscribers. The column must allow NULL
> values or include a default constraint.
> b.. To add a new column to a table and not include that column in an
> existing publication, disable the replication of schema changes, and then
> execute ALTER TABLE <Table> ADD <Column>.
> c.. To include an existing column in an existing publication, use
> sp_articlecolumn (Transact-SQL), sp_mergearticlecolumn (Transact-SQL), or
> the Publication Properties - <Publication> dialog box.
> For more information, see How to: Define and Modify a Column Filter
> (Replication Transact-SQL Programming) and How to: Define and Modify a
> Column Filter (SQL Server Management Studio). This will require
> subscriptions to be reinitialized.
> d.. Adding an identity column to a published table is not supported,
> because it can result in non-convergence when the column is replicated to
> the Subscriber. The values in the identity column at the Publisher depend
> on the order in which the rows for the affected table are physically
> stored. The rows might be stored differently at the Subscriber; therefore
> the value for the identity column can be different for the same rows.
> However, while I am able to add the column to the publisher and it is
> replicated to the subscriber, I cannot update this column at the
> subscriber and have it replicate to the publisher. However when I update
> at the publisher it IS pushed to the subscriber.
> Outside of the new column, my updates bi-directionally work. Can someone
> tell me how I can get updates on newly added columns to be bi-directional?
> Thanks,
> Adam P. Cassidy
>
|||Yes. That is the same article I used as a reference originally.
Adam P. Cassidy
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%234SYrOq4GHA.1188@.TK2MSFTNGP05.phx.gbl...
> Did you quiesce the system as outlined in this link?
> http://msdn2.microsoft.com/en-us/library/ms147385.aspx
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Adam Patrick Cassidy" <apcassidy@.aol.com> wrote in message
> news:eoBB5en4GHA.1200@.TK2MSFTNGP02.phx.gbl...
>

pdf ifilter sp_fulltext_service settings dilemma

I've read Mr. Cotter's article on full-text search and as with several other
folks, he mentions the use of the following commands to allow the adobe pdf
ifilter to be used.
exec sp_fulltext_service 'load_os_resources', 1;
exec sp_fulltext_service 'verify_signature', 0;
This works fine. However, a few articles I've read suggest that after you
have added the ifilter, you should restore these less secure values back to
exec sp_fulltext_service 'load_os_resources', 0;
exec sp_fulltext_service 'verify_signature', 1;
Because I want to keep my SQL Server secure, I have run these statements.
However after stopping and starting SQL Server or rebooting, the pdf ifilter
is no longer available to SQL Server full text search. Therefore, no new
pdf's are indexed. Is this the expected behavior? If so, What good is it to
restore the values if you can't index new documents. On the other hand, how
can you justify the security risk by not restoring the values to their more
secure state? Am I missing something here?
Can you direct me to the articles which suggest you can re-enable the
verification of the signatures. My understanding is that these signatures
are verified each time SQL Server or MSFTESQL starts. This is the suggested
behavior.
The danger is that one of the iFilters you load could be a victim of a
buffer overflow or another exploit . While the risk of this happening if
real it is really quite unlikely.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Dlorbecki" <Dlorbecki@.discussions.microsoft.com> wrote in message
news:DCB580BC-BAC1-47EB-A2A0-F67958DEA29E@.microsoft.com...
> I've read Mr. Cotter's article on full-text search and as with several
> other
> folks, he mentions the use of the following commands to allow the adobe
> pdf
> ifilter to be used.
> exec sp_fulltext_service 'load_os_resources', 1;
> exec sp_fulltext_service 'verify_signature', 0;
> This works fine. However, a few articles I've read suggest that after you
> have added the ifilter, you should restore these less secure values back
> to
> exec sp_fulltext_service 'load_os_resources', 0;
> exec sp_fulltext_service 'verify_signature', 1;
> Because I want to keep my SQL Server secure, I have run these statements.
> However after stopping and starting SQL Server or rebooting, the pdf
> ifilter
> is no longer available to SQL Server full text search. Therefore, no new
> pdf's are indexed. Is this the expected behavior? If so, What good is it
> to
> restore the values if you can't index new documents. On the other hand,
> how
> can you justify the security risk by not restoring the values to their
> more
> secure state? Am I missing something here?
|||Here's one link:
http://activeobjects.blogspot.com/2006/01/sharepoint-services-sql-2005-and-pdf.html
Are you saying not to run the latter two commands? My experience is that
after you do, the pdf ifilter does not function for new documents. However,
then you have the dilemma of the security hole.
"Hilary Cotter" wrote:

> Can you direct me to the articles which suggest you can re-enable the
> verification of the signatures. My understanding is that these signatures
> are verified each time SQL Server or MSFTESQL starts. This is the suggested
> behavior.
> The danger is that one of the iFilters you load could be a victim of a
> buffer overflow or another exploit . While the risk of this happening if
> real it is really quite unlikely.
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Dlorbecki" <Dlorbecki@.discussions.microsoft.com> wrote in message
> news:DCB580BC-BAC1-47EB-A2A0-F67958DEA29E@.microsoft.com...
>
>
sql

pdf ifilter issue with sp_fulltext_service

Several internet posts I've read describe how to get SQL Server to recognize
a 3rd party ifilter .dll. This involves the use of sp_fulltext_service with
the following syntax:
Exec sp_fulltext_service 'verify_signature', 0
Exec sp_fulltext_service 'load_os_resources', 1
I've used these commands and have been able to get SQL Server and SharePoint
to build an index for pdf documents. Many of these instructions tell you to
reverse the settings after you're finished in order to better secure the
server. Those commands are:
-- Restore the Full-text service settings to their default
Exec sp_fulltext_service 'verify_signature', 1
Exec sp_fulltext_service 'load_os_resources', 0
The problem is, that once you run the above commands and reboot, you no
longer index any new pdf files added to the server. Is this the expected
behavior? If not, what am I doing wrong? I don't want to leave the security
hole open by not running these commands but then you don't index new files.
This is a duplicate post I created because I did not see my original after a
day of waiting. Please disregard this post and use the other. Thanks.
"Dlorbecki" wrote:

> Several internet posts I've read describe how to get SQL Server to recognize
> a 3rd party ifilter .dll. This involves the use of sp_fulltext_service with
> the following syntax:
> Exec sp_fulltext_service 'verify_signature', 0
> Exec sp_fulltext_service 'load_os_resources', 1
> I've used these commands and have been able to get SQL Server and SharePoint
> to build an index for pdf documents. Many of these instructions tell you to
> reverse the settings after you're finished in order to better secure the
> server. Those commands are:
> -- Restore the Full-text service settings to their default
> Exec sp_fulltext_service 'verify_signature', 1
> Exec sp_fulltext_service 'load_os_resources', 0
> The problem is, that once you run the above commands and reboot, you no
> longer index any new pdf files added to the server. Is this the expected
> behavior? If not, what am I doing wrong? I don't want to leave the security
> hole open by not running these commands but then you don't index new files.
>

pb with a trigger

hello,
I've a problem with a trigger :
this trigger update a file with an index field but it's return an error
: UPDATE stop because the Set option : "QUOTED_IDENTIFIER" return bad
parameters
for information, this is my trigger :
CREATE TRIGGER COOP_article ON F_ARTICLE FOR insert AS
SET NOCOUNT ON
set arithabort on
set concat_null_yields_null on
set quoted_identifier on
set ansi_nulls on
set ansi_padding on
set ansi_warnings on
set numeric_roundabort off
declare @.code varchar(17)
select @.code=ar_ref from inserted
begin
*/ replace if reference = 0 */
if @.code='0'
begin
update f_article set ar_ref='test' from f_article join
inserted on f_article.cbmarq=inserted.cbmarq
end
end
if you ave an idea...
thanks
philned
Perhaps the trigger was created with SET QUOTED_IDENTIFIER OFF. This
setting is remembered for subsequent trigger executions. Try:
SET QUOTED_IDENTIFIER ON
SET ANSI_NULLS ON
GO
CREATE TRIGGER COOP_article ON F_ARTICLE FOR insert AS
SET NOCOUNT ON
set arithabort on
set concat_null_yields_null on
set quoted_identifier on
set ansi_nulls on
set ansi_padding on
set ansi_warnings on
set numeric_roundabort off
declare @.code varchar(17)
select @.code=ar_ref from inserted
begin
*/ replace if reference = 0 */
if @.code='0'
begin
update f_article set ar_ref='test' from f_article join
inserted on f_article.cbmarq=inserted.cbmarq
end
end
GO
Hope this helps.
Dan Guzman
SQL Server MVP
"philned" <philned@.wanadoo.fr> wrote in message
news:418783e6$0$9305$636a15ce@.news.free.fr...
> hello,
> I've a problem with a trigger :
> this trigger update a file with an index field but it's return an error :
> UPDATE stop because the Set option : "QUOTED_IDENTIFIER" return bad
> parameters
> for information, this is my trigger :
> CREATE TRIGGER COOP_article ON F_ARTICLE FOR insert AS
> SET NOCOUNT ON
> set arithabort on
> set concat_null_yields_null on
> set quoted_identifier on
> set ansi_nulls on
> set ansi_padding on
> set ansi_warnings on
> set numeric_roundabort off
> declare @.code varchar(17)
> select @.code=ar_ref from inserted
> begin
> */ replace if reference = 0 */
> if @.code='0'
> begin
> update f_article set ar_ref='test' from f_article join
> inserted on f_article.cbmarq=inserted.cbmarq
> end
> end
>
> if you ave an idea...
> thanks
> philned

pb with "QUOTED_IDENTIFIER"

hello,
I've a problem with a trigger :
this trigger update a file with an index field but it's return an error
: UPDATE stop because the Set option : "QUOTED_IDENTIFIER" return bad
parameters
for information, this is my trigger :
CREATE TRIGGER COOP_article ON F_ARTICLE FOR insert AS
SET NOCOUNT ON
set arithabort on
set concat_null_yields_null on
set quoted_identifier on
set ansi_nulls on
set ansi_padding on
set ansi_warnings on
set numeric_roundabort off
declare @.code varchar(17)
select @.code=ar_ref from inserted
begin
*/ replace if reference = 0 */
if @.code='0'
begin
update f_article set ar_ref='test' from f_article join
inserted on f_article.cbmarq=inserted.cbmarq
end
end
if you ave an idea...
thanks
philned
Why are you setting quoted identifiers on? You don't seem to need it.
Same goes for most of the set statements.
"philned" wrote:

> hello,
> I've a problem with a trigger :
> this trigger update a file with an index field but it's return an error
> : UPDATE stop because the Set option : "QUOTED_IDENTIFIER" return bad
> parameters
> for information, this is my trigger :
> CREATE TRIGGER COOP_article ON F_ARTICLE FOR insert AS
> SET NOCOUNT ON
> set arithabort on
> set concat_null_yields_null on
> set quoted_identifier on
> set ansi_nulls on
> set ansi_padding on
> set ansi_warnings on
> set numeric_roundabort off
> declare @.code varchar(17)
> select @.code=ar_ref from inserted
> begin
> */ replace if reference = 0 */
> if @.code='0'
> begin
> update f_article set ar_ref='test' from f_article join
> inserted on f_article.cbmarq=inserted.cbmarq
> end
> end
>
> if you ave an idea...
> thanks
> philned
>