Post reply

Cross Server Queries

  • December 2, 2008 at 10:14 am

    #194531

    Hi,

    One of our developers has pointed our the Following:-

    We are selecting rows from a table on server "Tom" from a Server"Jerry" so performing a cross server query. What we have found is that after the script has finished newly inserted rows do not appear straight away. This occurs when running the cross server query from only some of our servers and others are fine which seems to indicates the server "Tom" is not the problem. After 2 -3 minutes the server the query was run from seems to catchup.

    Any ideas?

    Thanks in advance

    Vinny

  • December 3, 2008 at 4:03 pm

    #907233

    Are the new records inserted in "Tom" or is there replication involved (possible delay)?

  • December 4, 2008 at 2:39 am

    #907423

    Hi Jo,

    We are inserting records, no replication involved.

    Thanks

    Vinny

  • December 4, 2008 at 2:45 am

    #907427

    Hi all

    Maybe a bulk insert instead of the insert solve this. Just an ideia

  • December 4, 2008 at 2:45 am

    #907428

    It may due to concurrency.

    If you are selecting the data from the server and at the same time some insertion is happening then the new inserted row wont be reflected in the select statement.

  • December 4, 2008 at 2:50 am

    #907432

    Or U could use the table hint dirty read to see if it is about transactions or not.

  • December 4, 2008 at 4:14 am

    #907459

    Hi all,

    I've spoken to our developer, whe have tested this from several servers to iliminate a single route cause and founf that some of the servers produce expected results and some dont, an that basis, it doesnt seem a bulk insert would resolve the problem in this scenario. Concurrency seems unlikely as all inserts are carried out and completed prior to carrying out any selects.

    Again would Table Hint Dirty be a criteria in the scenario above?

    Thanks in Advance

    Vinny

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply