Hi
If you are using their APIs to access the database then they have
effectively written your data access layer and it sounds like they don't want
you to access the database directly.
Why are you wanting to have two copies of the database? How up-to-date does
the second copy need to be? What activity will be occurring on the second
copy?
If transactional replication is not advisable you should find out why, then
you will be in a better position to work out if snapshot replication is
viable or possibly log shipping. Period manual backup/transfer/restore
operations may be adequate.
John
[quoted text, click to view] "Inderjit Rai" wrote:
> Hi John,
>
>
> I'm replicating (after some major data testing and modifications)
> records one way, from sql server X to sql server Y. Sql server Y is a
> backend database for a application called Blackboard and they have
> several Java api's to update and retrieve data from their database, and
> they suggest that we don't use transactional replication but build a
> standalone application. I'm not familiar with developing applications
> in middle tier (or any tier) and i was wondering if you could elaberate
> or let me know of any online tutorials that deal with this sort of
> thing.
>
> Thanks again,
> Inder
>
> *** Sent via Developersdex
http://www.developersdex.com ***