replication cache plan

Hi,
I heard that simple delete stmt which deletes no of rows everytime in
replication is not using came plan caching why you have any idea or is there
any option that we can turn on to use cache plan..
Thanks in advance
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server-replication/200706/1
No, it will use the plan that either the ad hoq sql statements use or the
stored procedure plan.
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
"pardhiveswar via droptable.com" <u8956@.uwe> wrote in message
news:73eafdf38c451@.uwe...
> Hi,
> I heard that simple delete stmt which deletes no of rows everytime in
> replication is not using came plan caching why you have any idea or is
> there
> any option that we can turn on to use cache plan..
>
> Thanks in advance
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums.aspx/sql-server-replication/200706/1
>
|||Hillary,
ok if Autoparameterization is not using for simple delete statement in 2000
what we have to do..
is there an option to force sql server...
Thanks in advance
Hilary Cotter wrote:[vbcol=seagreen]
>No, it will use the plan that either the ad hoq sql statements use or the
>stored procedure plan.
>[quoted text clipped - 4 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server-replication/200706/1
|||Hillary,
Just ignore the above stsmt.
Actually my questions is during replication from sql to sql it will create
stored prodecudres
but from sql to oracle iinstead of stored procedure it will only create sql
stmt so during this time it is not using autoparameterisation for simple
delete stmt(adhoc stmt),is there a way that we can use autoparam...
please let me know if you didn't understand
sorry for the confusion before..
Thanks, in advance
pardhiveswar wrote:[vbcol=seagreen]
>Hillary,
>ok if Autoparameterization is not using for simple delete statement in 2000
>what we have to do..
>is there an option to force sql server...
>Thanks in advance
>[quoted text clipped - 3 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server-replication/200706/1

Replication - filtering

Hi All,
Is it possible to replicate only INSERTS and UPDATES and NOT Deletes.
We have a production server and reporting server. The challenge is to keep
90days of data in the production system, and 180days of data on the
reporting system. Need to some how to ensure that the cleanups done on the
Production server are not propogated through to the Reporting server.
Really appreciate it if someone can point me in the right direction - I am
sure this problem has been solved before.
thanks
Mathew
If you're using transactional replication, on the article properties,
commands tab, enter NONE for the delete command. if it's merge, there isn't
a straightforward method, but provided you understand the ramifications, you
could disable the merge delete trigger.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)