Re: Help w/Transcational Replication setup

Tech-Archive recommends: Speed Up your PC by fixing your registry

You can replicate an indexed view as a table. It sounds like somehow you
have configured automatic identity range management on your publication, can
you review the problem table in this publication and make sure this feature
is disabled.

--
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



"dw" <dw@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2720EC6D-C679-4F08-972C-F989EEE569CF@xxxxxxxxxxxxxxxx
Good questtion...I don't think the column is an identity column...but I
will
verify. Both servers are SQL 2005.

By the way....could I use a View instead? In other words, could I create
a
view of the data from Server A and then replicate that view to a
subscribing
server?

thanks

"john.gagnon@xxxxxxxxx" wrote:

Is the column in question on Server B an identity column? It should
not be. What version are you using of SQL on both servers?

dw wrote:
Hello -

I am trying to set up a server to server (both are SQL 2005)
Transactional
Replication publication. (Source = Server A, Target = Server B)

In this situation, Server B (the source) only needs to receive the
data,
first the initial snapshot and then any subsequent Updates. Server B
will
not be making any changes to the data.

One of the tables I am trying to publish has an Identity column.
Whenever
the publication wizard on Server A is starting to build the
publication, I
get the following error: "Automatic identity range support is useful
only
for publications that allow updating subscribers."

In our case, we don't want the subscribing Server to update the data.
Is
there a way for me to get around this issue?

thanks for any help
- will




.

Relevant Pages

  • Re: Check Sysobjects Error during Snapshot
    ... Looking for a SQL Server replication book? ... > published databases, each publication is slightly different (row ... > A2 to subscriber 2 without a problem. ... I can replicate database b publication B2 to Subscriber2 without a ...
    (microsoft.public.sqlserver.replication)
  • RE: Synchronisation failing on SQL CE Database
    ... There is also an error on the publication in the Replication monitor. ... Server SERVER, Level 0, State 1, Procedure sp_MSprepare_mergearticle, Line 78 ... I am having a problem setting up merge replication between SQL 2005 and SQL ...
    (microsoft.public.sqlserver.replication)
  • SQL Server merge replication security
    ... Microsoft SQL Server replication. ... need to have the sysadmin role on their local database to initiate the ... The AppAdmin table cannot be removed from the publication as then the ...
    (Focus-Microsoft)
  • Re: Restore Replicated Database
    ... For the subscription script, I don't think I'll need to ... Once the restore of the database has taken place, I'll then run a script to ... DROP the publication and subscription. ... > want different agent profiles on each server and this is also something to ...
    (microsoft.public.sqlserver.replication)
  • Re: Create new publication error
    ... I was logged on as a server administrator in the ... about Windows NT group/user 'username', error code 0xffff0002"; ... I have changed the user name, the publisher name and the ... When I attempt to create a new publication, using either SSMS or EM, I ...
    (microsoft.public.sqlserver.replication)