"I see" said the blind man...so in the scenario I'm attempting to create,
Can I create replication between my ServerB and ServerA for only 1 table and
then via a linked server (service) execute procedures to update these
tables... the trick I'm attempting to do is to only provide data to the
external server, based on what a user login in has rights to.. such that a
user that has rights to USA would only see USA, but maybe an AU user would
log in and get only AU data... of course the client application is also
developed by us so we are executing sp's with Where, to keep the data
> You can execute stored procedures on linked servers. You can also access
> all the tables and views. You won't see them through Enterprise Manager
> when looking at the linked server howerver. I would strongly urge against
> accessing a linked server through a trigger. I think you will have some
> severe performance problems with that. Make a job to handle changed rows.
> Or you might consider using Transactional Replication between the two
> servers. ServerB changes table X. Transactional rep to ServerA. ServerA
> reads changes to table X and inserts answers into table Y. Transactional
> rep table Y to server B. You can set transactional replication to make
> changes immediately but it will handle the condition where one of the
> servers is unavailable.
> > I want to start using the Linking feature in SQL, where we have 2 SQL7
> > Servers. What I want to do is the following...
> > ServerA is in house, ServerB is visible on the internet. When data
> > updates are made to ServerB, I'd like ServerA to be aware of the changes
> > issue updates to that data. Say if you have a column where data is
> > as 1+1, then ServerA could pull the data store it but also issue the
> > which in this case happens to be 2.
> > I've gone through BOL, but I can only link to ServerB but am unaware on
> > to set up the triggers.. plus I noticed I cannot see the Stored
> > or view etc....
> > --
> > -Francisco