Forum Replies Created

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

  • RE: Double Insert?

    Sorry about the getdate() before, I guess I didn't read all the posts after a while.

    Anyhow, funny you should mention that it happens when there is a network slowdown....

  • RE: Double Insert?

    Looing at the sample data you provided,

    StageID RepairID StageType Result StartDate UserID EndDate Comments LastTestStageID Station

    1051324 305259 1 0 2009-03-24 10:31:29.720 phanyv 2009-03-24 13:51:02.400 no video NULL CR-TEST1

    1051331 305259 1...

  • RE: Double Insert?

    Have you discounted the possibility of 2 users entering the same information at the same time or maybe someone trying to break your software and didn't tell you about it?

    try...

  • RE: Double Insert?

    Journeyman,

    I totally concur with your suggestions. To add to your suggestion, to verify that the application is calling the proc more than once, I would fire up the SQL Profiler...

  • RE: Double Insert?

    Yes, of course. I didn't elaborate on a the whole solution.

    Sorry.

    AL

  • RE: Double Insert?

    I have gone down that path of having the application take care of deciding if the record exists or not.

    But now, I am much wiser and leave that to...

  • RE: Double Insert?

    I should have thought of this before, but wasn't thinking clearly.

    To prevent dupes also you could wrap your insert in "if not exists" t-sql statement with Begin/End.

    ie:

    if not exists (...

  • RE: Double Insert?

    I agree that it could also be a situation where there could be a

    trigger on that table causing a double insert.

    However, you should also have a unique index...

  • RE: Proc call runs longer than code execution in 2000

    Thanks and Yes this is a problem in SQL Server 2000 and I think still a problem with SQL 2005 even SP2.

    Dance away!:hehe:

  • RE: Proc call runs longer than code execution in 2000

    Could you send us the version # of your SQL instance?

    select @@version

    Mine:

    Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c)...

  • RE: Proc call runs longer than code execution in 2000

    We have SQL Server 2005 SP2 and I am not sure if it still happening. I am about to try and reproduce with a and old proc that had the...

  • RE: Proc call runs longer than code execution in 2000

    Right on! for some versions of SQL Server 2000 and SQL Server 2005.

    However, this problem was resolved in SQL Server 2005 SP1 if I remember correctly or is it still...

  • RE: Proc call runs longer than code execution in 2000

    I am not 100% sure but I have been in this situation before.

    It would appear that the Query Analyzer is being fooled by something in your procedure and forced to...

  • RE: Proc call runs longer than code execution in 2000

    Post d code and we can take a look.

    I have been in the same situation and could probably help.

    AL

  • RE: Effective Dating Query

    You were correct for asking for more data. It's been a crazy day for me

    and didn't get a chance to connect to the other db server.

    Anyhow, It actually works well...

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