August 16, 2011 at 12:13 am
What is the best way to setup the following scenario:
I have a SQL 2008 database with a Customer and a Job table in domain A.
These tables need to be made partially available on a remote site (SQL Server 2008, on a different geographical location, in a different domain B).
At the same time, I need to "pull" time registration data from the remote domain B back to domain A.
Important: domain A will not accept incoming connections! Domain A will push/pull data to/from domain B.
What should I use:
- setup web services in domain B?
- setup replication?
- use linked server?
- other ... ?
Many thanks for your advice.
August 16, 2011 at 2:18 am
Is there cross domain authentication possible between A and B ie do they trust each other ?
Replication with a UI front seems to be good fit for what your trying to achieve.
If your trying to do reporting on a BI scale then there are more considerations such as should you have a ETL process.
Do you need a full fledged reporting solution like SSRS or microstrategy etc.
In a very basic sense ; replication with the web UI should do fine.
August 16, 2011 at 3:22 am
Thanks for your input.
I can't promise the trust relationship between both domains.
August 23, 2011 at 6:40 am
I've used SSIS to create text files and then SFTP them to the destination and restore if there is no chance of any connection between the domains / networks. Or alternatively set up a secure VPN connection and then use a linked server.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply