Database replication (NAV 2009 Classic / SQL 2008)

ALopez27

I'm new to using NAV/SQL replication, we have several replicated databases, these are mostly for reporting purpouses, and one is for a remote location, I have searched the forum but have not found anything specific (basic) to my two questions, which are the following:

1) For reporting, is it really necessary to have a replicated (real-time) NAV (SQL 2008) db? Would having an automated script to copy the db during off-hours accomplish the same thing? I'm thinking that since we really don't need real-time reporting, there is un-nessary updates to the replicated db and possibly performance issues.

2) For our remote location, it's basically the same operations, they do write-transactions to the database which gets replicated, I guess this was set-up so that the remote location would continue to use NAV in case of a downed communications line, we very rarely experience this, would it make more sense to just have those remote users remote connect to the corp. database and not do replication? Could this contribute to some lock/integrity of data when doing process intensive transactions?

kine

ad 1) You can use Log Shipping instead transaction replication to create the copy for reporting. It is on you, you really do not need the real-time replication...

ad 2) All depends on details. There is no simple way how to create replicated database for both way communication. For this you will need some addon or modifications (you cannot just setup merge replication and expect that it will work...). If possible and usable, just use the terminal services to connect the users to the central DB. But all depends on details...