Forum Replies Created

Viewing 15 posts - 16 through 30 (of 34 total)

  • RE: Using replication for manual failover

    Hi,

    We have a similar scenario and have used queued Transactional Replication to the backup system - using all the default setting our latency is about 5 seconds.

    Our plan, if the...

  • RE: No data in Timestamp field

    Hi,

    And don't forget - Timestamp has nothing to do with date/time - it is simply a integer, incremented by one, on each row insert and update in a database.

    Cheers, Peter

    ...

  • RE: Not for Replication seems to be ignored

    Hi Jay,

    Thanks for your help - all is working well. In our load test (2 x 1.6Ghz Pentiums with 1Gb memory) there was no noticable change to user response times....

  • RE: Not for Replication seems to be ignored

    Hi Jay,

    machine problems hit and delayed work on replication. But we are looking good now although we hit problems with having the "If Update.." code in our Insert triggers. But...

  • RE: Not for Replication seems to be ignored

    Hi Jay,

    Thanks for the prompt response. So, as I undestand it, we need both "NOT FOR.." and "IF UPDATE (msrepl_tran_version) RETURN" in all our triggers. I was concerned that...

  • RE: Not for Replication seems to be ignored

    Hi Jay,

    Ok, we have restored the database and published one article (tblACNAcntCodes). The snapshot and creating the subscription worked fine.

    See below for the two triggers involved. AAAA is our own...

  • RE: Not for Replication seems to be ignored

    Hi Jay,

    Thanks for that. Yes the trigger is applied correctly at the subscriber but the nesting error is on the publisher.

    Now that you have provided confirmation that what we are...

  • RE: Not for Replication seems to be ignored

    Hi Jay,

    Correct - it was before the AS. We did indeed start off with it after the AS which did give a syntax error.

    Cheers, Peter

  • RE: Trans Rep and PK problem on initial import

    OK - by deleting the XXX update trigger the error goes away. Further research revealed what seemed to be the answer - insert the line:

    NOT FOR REPLICATION

    just before the "AS"...

  • RE: Trans Rep and PK problem on initial import

    Well we are passed first base but, unfortunately, we are not sure how. Our database has now been replicated to a second server - clearly we must have 'stumbled' into...

  • RE: CAL licencing

    Hi,

    Yes - that was my general understanding maybe the point I'm missing is where the CALs are installed. I presume the physical install is on the Server if so, does...

  • RE: Is this good sql?

    Hi Andy,

    Thanks for the comment. But can you expand - what is a "see issue"?

    Also, can you comment on my original question - will SQL Server perform a complete scan...

  • RE: Is this good sql?

    Thanks for the feedback.

    I don't have much experience in writing SQL - my background is Access and linking queries is common place. A view (to me) looked like a an...

  • RE: Connections and User Connections - same??

    Hi Andy,

    It would be great if I could do this but that code generates the error:

    Runtime 3705

    Operation is not allowed when the object is open.

    Then, if I close the recordset,...

  • RE: Connections and User Connections - same??

    Hi Andy,

    It says: "..one important caveat: SQL Server can only support one active query on a connection" and goes on to say that the OLE-DB spec requires that extra connections...

Viewing 15 posts - 16 through 30 (of 34 total)