Forum Replies Created

Viewing 15 posts - 2,551 through 2,565 (of 7,614 total)

  • Reply To: Comparing to Columns from the same table

    I prefer using CROSS APPLY to assign alias names.  CAs can also cascade, where one alias can be used to create another alias(es).  That's very helpful sometimes.

    select BSEG_ID,SP_ID,FINAL_REG_QTY,START_REG_READING, END_REG_READING,

    ActualRead

    from CI_BSEG_READ

    cross...

  • Reply To: Index larger than table

    .1. The PK itself.

    .2. No.

    .3. The clustering key column(s) are stored in higher-level index entries.  The deeper the index depth, the more space the upper levels of the index take.

  • Reply To: Fifi Calculation

    Jeff Moden wrote:

    jcelko212 32090 wrote:

    >> I don't think I was particularly snarky.

    THAT, good Sir, is the crux of the problem. 😉

    I don't think his first post was particularly snarky, esp. for him,...

  • Reply To: Fifi Calculation

    jcelko212 32090 wrote:

    My next correction is a little more controversial. The reason that debits and credits exist has to do with the fact that when modern bookkeeping began in the Renaissance,...

  • Reply To: Difference between where and INNER JOIN comparing a value

    I left one out, the sample INNER JOIN:


    ;WITH cte_A AS ( SELECT * FROM (VALUES(1, 'A', 10),(2, 'B', 20), (3, 'C', 30)) AS data(key_col, col1, col2)
    ), cte_B...
  • Reply To: Difference between where and INNER JOIN comparing a value

    Here are queries to demonstrate the points above.  Assume for this example that B.col2 is a NOT NULL column.

    ;WITH cte_A AS ( SELECT * FROM (VALUES(1, 'A',...
  • Reply To: Difference between where and INNER JOIN comparing a value

    Grant Fritchey wrote:

    ...OUTER JOIN, if the filter is on the OUTER table, it needs to go to the JOIN criteria or it converts the OUTER JOIN to an INNER JOIN which...

    • This reply was modified 6 years, 2 months ago by ScottPletcher. Reason: Reworded, for clarity
  • Reply To: persisted computed column error

    You need to specify an explicit format (conversion code) for the date conversions, viz:

    CONVERT(varchar(100),ISNULL(despatch_group_start_date,'01/01/1900'), <format_code_needed_here>)

  • Reply To: Temporal Table Columns

    OK, so I guess the AFTER trigger would have to use the deleted table to check for UPDATEs vs. just relying on the UPDATE() function.

    CREATE TRIGGER dbo.TriggerSource_AFTER_UPDATE
    ...
  • Reply To: Temporal Table Columns

    I don't know, maybe I'm not thinking about it right, but I was anticipating something like below.  SQL checks a column value being UPDATEd and doesn't actually change it if...

  • Reply To: Temporal Table Columns

    Jeff Moden wrote:

    ScottPletcher wrote:

    I've had to use "extension" tables here a few times too, for various reasons.

    If you have an identity column present, do remember / be aware of the issues...

  • Reply To: Temporal Table Columns

    I've had to use "extension" tables here a few times too, for various reasons.

    If you have an identity column present, do remember / be aware of the issues with SCOPE_IDENTITY()...

  • Reply To: Temporal Table Columns

    For (1), you could add a column to the table itself to store the original login name there too (or, far better to save space, an id (that you assign)...

  • Reply To: Temporal Table Columns

    1.  No way around it.  The temporal table must exactly match the original schema.  My guess is that this provides efficiency in the way SQL Server internally implements the Temporal...
  • Reply To: Temporal Table Columns

    Jeff Moden wrote:

    2. ...   Current trigger technology won't even directly allow the saving of LOB columns because the LOB values don't show up in the INSERTED/DELETED logical tables in standard DML...

Viewing 15 posts - 2,551 through 2,565 (of 7,614 total)