Forum Replies Created

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

  • RE: Schema design , many-to-many M:N

    bugg - Wednesday, June 14, 2017 5:22 AM

    Another common scenario is that an item might not have a warehouse assigned and the...

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

  • RE: Heap vs Clustered Wildcard Search

    Sergiy - Wednesday, June 7, 2017 5:51 AM

    You should not be merging different codes into one.
    You're losing data by doing this.
    If...

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

  • Reply To: Is the logic the same for these two queries?

    Jeff Moden - Monday, June 12, 2017 12:24 PM

    Based on the fact that someone used the YEAR() function in one of the renditions of the...

    • This reply was modified 7 years, 2 months ago by whenriksen.
    • This reply was modified 6 years, 2 months ago by whenriksen.

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

  • RE: Advice on creating unique clustered index

    I would question the need to make the indexed view unique.  Is a regular indexed view not enough?

    My biggest concern is when you attempt to insert a record...

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

  • RE: UNION returns null values

    acmedeepak - Friday, May 19, 2017 6:45 AM

    The @StoreNumber actually is a set of column names in a table. To test the...

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

  • RE: Add Accounts that have no orders to a SQL view

    The first and second result sets are likely to always be different.  Changing your UNION to a UNION ALL will save you some server resources.  If you are trying to...

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

  • RE: SQL Server | Architecture design -

    ranitb - Tuesday, April 18, 2017 6:23 AM

    Ex. User "RB" logs into database and lands on schema "Sales", as configured by...

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

  • RE: SQL Server | Architecture design -

    ranitb - Friday, March 31, 2017 6:24 AM

    1)Why is there no authentication mechanism between schemas ?

    2) Is there any concept of Collections...

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

  • RE: concatenate three fields with one date field

    Use the Concat function, all of the inputs are converted to character types.  I cast the date as a datetime2(0) to get rid of the milliseconds.

    DECLARE @Col1...

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

  • RE: Optimizing fact table for column store index

    I don't see any need to move description into a separate table just because of a columnstore index. 

    I agree that the description should not be in the fact;...

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

  • RE: Logical OR comparison between two queries hangs

    Sergiy - Monday, March 20, 2017 4:48 AM

    SELECT 1 WHERE EXISTS (
    SELECT 1 FROM View1 WHERE field1 = 'Y'
    union all
    SELECT 1...

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

  • RE: Old Query that I dont quite understand

    Budd - Monday, March 20, 2017 8:34 AM

    Thank you for all replies. (especially after all my mistakes in posting this)

    Tbl3 is a...

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

  • RE: Referencing another table throws off totals

    bzoom100 - Friday, March 3, 2017 8:39 AM

    Ah yes, you have steered me in the right direction. The Actions value needs this...

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

  • RE: Whitespace in 3-part name ignored???

    Jeff Moden - Wednesday, March 8, 2017 2:20 PM

    My biggest PO is when someone tries to make a column name like "IsNotActive".

    and...

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

  • RE: How to choose between Clustered Columnstore & Non-Clustered Columnstore index

    OLTP to me implies insert, update and deletes.  Updates and Deletes kill a columnstore pretty quickly, requiring the index to be rebuilt.  With a clustered columnstore (CCI), your table is...

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

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