A useable but non-updating subscriber?

Is there a way in SQL 2005 to be able to use a subscriber to test run data
and not have the updated data sent back to the publisher using any method of
replication? We will have 1 publisher and 2 subscribers (all 2005), and we
would like to use one of the subscribers for running test jobs, without
having the data returned to the publisher.
Thanks in advance
Nancy
Use either transactional or snapshot replication.
You can also use merge replication with the ExchangeType downloadonly
setting.
Hilary Cotter
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
"Nancy Lytle" <nancy_lytle@.payformance.com> wrote in message
news:eoSdBsreHHA.4560@.TK2MSFTNGP03.phx.gbl...
> Is there a way in SQL 2005 to be able to use a subscriber to test run data
> and not have the updated data sent back to the publisher using any method
> of replication? We will have 1 publisher and 2 subscribers (all 2005),
> and we would like to use one of the subscribers for running test jobs,
> without having the data returned to the publisher.
> Thanks in advance
> Nancy
>
|||So with transactional (in 2005), the subscription database would be usable
for reporting or testing, it woudn't be in a read only state, is that
correct? For some reason we were thinking the subscription database would
be read only.
Thanks,
Nancy
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eudjU0reHHA.1252@.TK2MSFTNGP04.phx.gbl...
> Use either transactional or snapshot replication.
> You can also use merge replication with the ExchangeType downloadonly
> setting.
> --
> Hilary Cotter
> 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
>
> "Nancy Lytle" <nancy_lytle@.payformance.com> wrote in message
> news:eoSdBsreHHA.4560@.TK2MSFTNGP03.phx.gbl...
>
|||Hilary Cotter
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
"Nancy Lytle" <nancy_lytle@.payformance.com> wrote in message
news:ubDFB5reHHA.3632@.TK2MSFTNGP02.phx.gbl...
> So with transactional (in 2005), the subscription database would be usable
> for reporting or testing, it woudn't be in a read only state, is that
> correct? For some reason we were thinking the subscription database would
> be read only.
> Thanks,
> Nancy
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:eudjU0reHHA.1252@.TK2MSFTNGP04.phx.gbl...
>
|||Yes it will be readable and you can write to it, in other words put new
indexes on. When you update data you might cause your replication agent to
fail unless you run in the continue on data consistency error profile.
Hilary Cotter
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
"Nancy Lytle" <nancy_lytle@.payformance.com> wrote in message
news:ubDFB5reHHA.3632@.TK2MSFTNGP02.phx.gbl...
> So with transactional (in 2005), the subscription database would be usable
> for reporting or testing, it woudn't be in a read only state, is that
> correct? For some reason we were thinking the subscription database would
> be read only.
> Thanks,
> Nancy
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:eudjU0reHHA.1252@.TK2MSFTNGP04.phx.gbl...
>
|||Thanks for the information,
Nancy
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23qSxO1seHHA.4848@.TK2MSFTNGP06.phx.gbl...
> Yes it will be readable and you can write to it, in other words put new
> indexes on. When you update data you might cause your replication agent to
> fail unless you run in the continue on data consistency error profile.
> --
> Hilary Cotter
> 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
>
> "Nancy Lytle" <nancy_lytle@.payformance.com> wrote in message
> news:ubDFB5reHHA.3632@.TK2MSFTNGP02.phx.gbl...
>
|||As well as Hilary's recommendation of transactional replication in this case,
I'd add that you could look at Read Committed Snapshot as a tool of
maintaining greater concurrency for those reports run during synchronization.
Paul Ibison
sql