Forum Replies Created

Viewing 15 posts - 511 through 525 (of 582 total)

  • RE: How would you handle this and why??? (Common Data)

    quote:


    But I wonder how many people have thought about making a single Phone Numbers table with maybe a field

    tbl_From

    to know which table...

  • RE: Deadlocking Problems

    code please?

  • RE: Check Constraints versus Lookup Tables

    I would favour using a lookup table even for these small domains. Although you are right that check constraints would would involve fewer joins (including the SQL Server internal joinlike...

  • RE: 1st SELECT after INSERT

    Dave, just had a thought - if it's practical to do on a test environment, you could use DBCC pintable, which forces the whole table to be RAM resident, so...

  • RE: 1st SELECT after INSERT

    So you've eliminated the (apparently strong) possibility that the initial delay is due to building the query plan??????

  • RE: 1st SELECT after INSERT

    I wrote 'procedure cache' - meant 'plan cache'.

  • RE: 1st SELECT after INSERT

    It sounds like it is the query plan. If your app is sending simple textual SQL statements with constants as SARGs, then there won't be a match in the procedure...

  • RE: Locking problem

    ADO spawns additional connections! May not be the cause of your problem, but is interesting anyway...

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;194979

  • RE: Locking problem

    I (and Guarddata, it appears) still don't believe that the code as you describe it would open a new connection. Something else is going on in the code.

    You might...

  • RE: Locking problem

    Using nolock means that transactions are no longer honoured. You can read data which has not been (and might never be) committed. Equally you might be unable to see data...

  • RE: Locking problem

    Yes - agree with GuardData - closing the rocordset ought to release any locks it is holding - in some configurations of the lock- and cursor- type parameters, the rst...

  • RE: Locking problem

    I suspect that FK caused the problem because the new connection is waiting for the other connection to commit and release its locks so that the new conn. can check...

  • RE: trigger cache?

    Don't understand what's happening here, but here's a few randomly selected musings:

    Have you tried updating the table from Query analyser rather than the app?

    How about dropping the trigger and then...

  • RE: Locking problem

    Is there any reason why you wouldn't remove the mistake of creating a new connection? That would solve your problem.

    A couple of subsidiary points:

    Using @@identity is more efficient than select...

  • RE: Locking problem

    alzdba - how do you see the trans. iso. level via Profiler? That would be very convenient...

Viewing 15 posts - 511 through 525 (of 582 total)