Replication SQL
-
Hi Guys I am sitting with a problem where we have a table in a database that must be replicated. This is the easy part. The problem is they only want inserts and updates to replicate and not deletes. Can anyone tell me if this is possible please? Kind Regards, Elizma
-
Hi Guys I am sitting with a problem where we have a table in a database that must be replicated. This is the easy part. The problem is they only want inserts and updates to replicate and not deletes. Can anyone tell me if this is possible please? Kind Regards, Elizma
-
How about creating an application to replicate excluding the deleted condition alone :)
Sathy
Would have love to, but that is not the requirement. They want a database with that table on the server. They want to make use of SQL replication (mirroring), but only replicate the Inserts and Updates. The problem with normal Mirroring is that the table will look identical. We dont want to make it look identical.
-
Would have love to, but that is not the requirement. They want a database with that table on the server. They want to make use of SQL replication (mirroring), but only replicate the Inserts and Updates. The problem with normal Mirroring is that the table will look identical. We dont want to make it look identical.
Well, as I understand replication; that isn't going to happen. However, you COULD create triggers on the source tables for insert and update to move the data to a table that IS replicated. For example, we have a table that is replicated; on inserts and updates, a trigger fires writing data to another table in another database. This process would work in reverse. Not exactly pretty, but it might work... Tim
-
Well, as I understand replication; that isn't going to happen. However, you COULD create triggers on the source tables for insert and update to move the data to a table that IS replicated. For example, we have a table that is replicated; on inserts and updates, a trigger fires writing data to another table in another database. This process would work in reverse. Not exactly pretty, but it might work... Tim
Hi There. Thank you so much for your reply. This was eventually the solution that I also came up with. What I've been told is that in SQL 2000 replication of Iserts and Updates alone cant be done, but it can be done in SQL 2005 by editing the Replication Log file and deleting the delete section. (Well, so I've been told). Unfortunately we user SQL 2000. Triggers will have to do. Thanx again for your reply. Kind Regards, Elizma