Forum Replies Created

Viewing 15 posts - 91 through 105 (of 149 total)

  • RE: Clustered Index on datetimeoffset?

    Make sure you understand the big picture of your system. If you focus on fixing one symptom, you'll frequently cause other problems.

    Another factor in clustered index design is the...

    Wes
    (A solid design is always preferable to a creative workaround)

  • RE: A scenario where SQL Server doesn't seem to help

    It would be helpful if you can post some of the dynamically generated SQL, ideally one with all 20+ columns included. In my experience, procedural developers don't write very...

    Wes
    (A solid design is always preferable to a creative workaround)

  • RE: Check default constraint for 2 columns

    @Patrick123 (11/23/2016)


    IF NOT EXISTS(SELECT * FROM sys.objects

    WHERE object_id = OBJECT_ID(N'[dbo].[DF_locked]')

    AND object_id = OBJECT_ID(N'[dbo].[DF_count]'))

    1. This will NEVER EXIST. A single object_id can never be equal...

    Wes
    (A solid design is always preferable to a creative workaround)

  • RE: ROW_NUMBER to distinguish between identical records

    You're filtering your inner query by the outer query values. That will affect the results of the inner query and thus the row numbers. To ensure consistent row...

    Wes
    (A solid design is always preferable to a creative workaround)

  • RE: will it call subquery for every row of table with distinct in subqyery.

    rajemessage 14195 (11/22/2016)Q3) in second query if uz table has two million records , and query is executing , at the same time if some one inserts a new record...

    Wes
    (A solid design is always preferable to a creative workaround)

  • RE: Convert Cross Join to Inner Join

    use Excel or some other spreadsheet tool and type up what your desired result will look like, with column headers. Than paste that back into the thread so we...

    Wes
    (A solid design is always preferable to a creative workaround)

  • RE: Convert Cross Join to Inner Join

    RonMexico (11/17/2016)


    My intent was to get the syntax for joining the same tables multiple times.

    First, you have the table self-join syntax correct (tableA as A1, tableA as A2... Where A1.ID...

    Wes
    (A solid design is always preferable to a creative workaround)

  • RE: Coalesce and ISNULL not grabbing columns with NULL

    Matt.Altman (11/17/2016)


    Seems like this worked

    SELECT COALESCE (n.Application, k.Application) Application

    FROM Table1 n

    FULL OUTER JOIN Table2 k

    ON n.Application = k.Application

    GROUP BY COALESCE (n.Application, k.Application)

    That looks like you are trying to get a...

    Wes
    (A solid design is always preferable to a creative workaround)

  • RE: Approach to normalising 15 million transactions

    Why can't you insert-select into the normalized tables, in order of dependency, to get the data moved over. 15m rows is not a very large amount so I assume...

    Wes
    (A solid design is always preferable to a creative workaround)

  • RE: Concurrency - Please Provide Comments

    I took a look at how I populate my drain table. I'm using TABLOCKX to lock the table entirely before I insert. This causes all other activities to...

    Wes
    (A solid design is always preferable to a creative workaround)

  • RE: Concurrency - Please Provide Comments

    Phil Parkin (11/3/2016)

    I have a question about the READPAST hint. Have you ever found that it has locked rows (at a page level) which are not and have not been...

    Wes
    (A solid design is always preferable to a creative workaround)

  • RE: Concurrency - Please Provide Comments

    Phil Parkin (10/30/2016)


    in this case, for queues of SSIS packages waiting to be executed, within different ETL jobs.

    The volumes I am dealing with are much lower than yours and I...

    Wes
    (A solid design is always preferable to a creative workaround)

  • RE: ColumnStore Index

    MadAdmin (10/26/2016)


    Deletes and updates should be avoided.

    Use partitions for your fact tables and apply partition switching instead of deleting data.

    Agree completely.

    Don't bother issuing a delete/update on a columnstore. It...

    Wes
    (A solid design is always preferable to a creative workaround)

  • RE: Concurrency - Please Provide Comments

    I assume you're implementing some kind of work queue table. As you reach high concurrency levels, you may experience blocks because the shared lock on read can block the...

    Wes
    (A solid design is always preferable to a creative workaround)

  • RE: Summarizing COUNTs - Flumoxed by getting my SQL right...

    The window function brings the summary data into the detail row, but does not affect how many records are returned.

    If you can't use a group by because you are mixing...

    Wes
    (A solid design is always preferable to a creative workaround)

Viewing 15 posts - 91 through 105 (of 149 total)