I am just trying to think through a process I need where I have:
- One SQL 2008 express database on a webserver – takes orders into an orders table
- Another SQL 2008 express database on another webserver acting as a backend system to process the orders etc
The idea being that the webserver database can be left to do what it does, and only when a new order record is inserted (actually updated.. another part of the story) I wanted that row to be inserted to an orders table on another server…
The two servers do have local IP addresses, and are essentially on the same subnet – i.e. can communicate easily enough…
Just trying to work out if a SQL Trigger is the way to go, or do I have perhaps a scheduled job on the second server which queries the first server say every 5 mins (plenty, not too many orders) and inserts any new orders into it’s own database.. the idea is the table in the source/first server has a bit field to indicate if that row has been seen/read by server two…
Any ideas? unfortunately it’s all SQL 2008 R2 express at this stage…
You don’t want a trigger accessing another server as part of a transaction. One solution, is to use Service Broker; have the trigger insert a message into the the local queue, and given the other server access to this queue.