Nav Error caused by SQL Replication process???

Simo_ba

Hi guys,

I need your help to fix this issue,guys.

I get an error message when I upload fob file to Nav that contain replicated tables,

the error message is:

---

Microsoft Dynamics NAV

---

The following SQL Server error(s) occurred while accessing the Item Ledger Entry table:

3724,"42000",[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop the view 'dbo.Test$Item Ledger Entry$VSIFT$2' because it is being used for replication.

SQL:
IF EXISTS (SELECT * FROM sysobjects WHERE id = OBJECT_ID(N'dbo."Test$Item Ledger Entry$VSIFT$2"') AND OBJECTPROPERTY(id, N'IsView') = 1) DROP VIEW dbo."Test$Item Ledger Entry$VSIFT$2"

---

OK

---

I found Microsoft solution but it's not be applied to me sorry.
'
Error occurs for objects that are replicated
For objects that are replicated, remove the object from the publication before attempting to alter or drop it. If the publication has subscriptions, you must delete all subscriptions before removing the object from the publication. '

Thank you guys,

ara3n

I'm guessing you've solved it by removing the table from replication?

Simo_ba

I don't want to remove this table from my replication,

I want this table to be replicated.

i cannot do that each time a upload fob file to nav.
](*,)

ara3n

Then you need to use use Transaction log replication.
SQL cannot allow a table to be changed once you've enabled any another type of replication.
You can use mirroring, but that is essentially T-log replication done within the same transaction realtime.

Simo_ba

Hi Rashed,

i'm using Transactional publication of the database,

is it the same thing or not?

Thanks a lot

kine

ara3n wrote:

Then you need to use use Transaction log replication.
SQL cannot allow a table to be changed once you've enabled any another type of replication.
You can use mirroring, but that is essentially T-log replication done within the same transaction realtime.

You mean "log shipping"?

ara3n

yes log shipping.

ara3n

Simo_ba wrote:

Hi Rashed,

i'm using Transactional publication of the database,

is it the same thing or not?

Thanks a lot

May I ask why you are using replication?

bbrown

This is something that must be taken into consideration when implementing transactional replication. Schema changes require that the replication links (publications and their subscriptions) be dropped then recreated. This is why replication may not be a good choice where ongoing development, and schema changes, are occurring. This is not unique to NAV but is a consideration in any SQL system.