Forum Replies Created

Viewing 11 posts - 1 through 11 (of 11 total)

  • RE: How ADO.NET and stored procs work together

    I am most grateful for your response Kenneth.

    I think in hindsight it is probably best to leave this system the way it is. However, I would very much like to...

  • RE: How ADO.NET and stored procs work together

    Perhaps you could comment on these SP's?

    Create Procedure WorkType_Upd

      @WorkTypeCode varchar(5),

      @WorkTypeDesc varchar(50),

      @ChangeStamp timestamp

    AS

    Update WorkType Set WorkTypeDesc = @WorkTypeDesc

    Where ChangeStamp = @ChangeStamp and

     WorkTypeCode = @WorkTypeCode

    GO

    Create Procedure WorkType_Del

      @WorkTypeCode varchar(5),

      @ChangeStamp timestamp

    AS

    Delete from WorkType

    where WorkTypeCode...

  • RE: Multiple resultsets

    I've discovered that if I create an untyped dataset in code (ie not use a designer) then it works!

    I wonder if there is a way, using Add -> New Item......

  • RE: Multiple resultsets

    OK, I have a number of SP's that return an entire lookup table each (they are only ever going to be a handful of records long) so I guess I...

  • RE: Multiple resultsets

    OK, thanks for that.

    Perhaps my next question requires posting elsewhere but here goes.

    Can I retrieve these two resultsets directly into an ADO.NET 2.0 dataset into the proper DataTables each with...

  • RE: How to return No. of rows updated in SP

    Thank you for that.

    What's the precise effect of using SET NOCOUNT ON?

    Regards

  • RE: Trigger firing sequence

    Yes, that makes sense.

    Thank you both for your responses

    Gary

  • RE: Using trigger to concatenate field values

    If a Computed column is more efficient then that's what I want to do. You'll notice I'm new to SQL Server....

    Could you tell me what the syntax for a computed...

  • RE: Using trigger to concatenate field values

    In fact it doesn't even work for single row insertions/updates because it always sets the value of the ClassTreeKey field on ALL records in the table to the value obtained...

  • RE: Creating and managing records with triggers

    Again this makes sense. The table can end up with ~20,000 rows which will certainly benefit from an indexed computed column.

    Thanks

  • RE: Creating and managing records with triggers

    I think this is a *much* better way of achieving the same result!

    I'm going to implement this and see how the dev likes it!

    Many Thanks

Viewing 11 posts - 1 through 11 (of 11 total)