Home/ Questions/Q 6673447
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T03:37:42+00:00

Below is an existing ms sql server 2008 report query. SELECT number, batchtype, customer,

  • 0

Below is an existing ms sql server 2008 report query.

SELECT
    number, batchtype, customer, systemmonth, systemyear, entered, comment, totalpaid
FROM
    payhistory LEFT OUTER JOIN agency ON
        payhistory.SendingID = agency.agencyid      
WHERE
    payhistory.batchtype LIKE 'p%' AND
    payhistory.entered >= '2011-08-01 00:00:00.00' AND
    payhistory.entered <  '2011-08-15 00:00:00.00' AND
    payhistory.systemmonth = 8 AND
    payhistory.systemyear = 2011 AND
    payhistory.comment NOT LIKE 'Elit%'

Results will look like this:

number  batchtype   customer    systemmonth systemyear  entered     comment         totalpaid
6255756 PC      EMC1106     8       2011        12:00:00 AM DP From - NO CASH       33
5575317 PA      ERS002      8       2011        12:00:00 AM MO-0051381526 7/31      20
6227031 PA      FTS1104     8       2011        12:00:00 AM MO-10422682168 7/30     25
6232589 PC      FTS1104     8       2011        12:00:00 AM DP From - NO CASH       103
2548281 PC      WAP1001     8       2011        12:00:00 AM NCO DP $1,445.41        89.41
4544785 PCR     WAP1001     8       2011        12:00:00 AM NCO DP $1,445.41        39

What I am trying to do is modify the query that will exclude records where the customer is like ‘FTS%’ and ‘EMC%’ and batchtype = ‘PC’. As you can see in the result set there are records where customer is like FTS% and batchtype = ‘PA’. I would like to keep these records in the results. I would appreciate any ideas offered.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Your query contains a mix of upper and lower string comparison targets. As far as I’m aware, SQL Server is not by default case-sensitive; is it possible this is what is tripping your query up? Check collation per this answer.

    EDIT: Based on your updated question, can you not just use an AND clause that uses a NOT on the front?
    In other words, add a ‘AND not (x)’ clause, where ‘x’ is the conditions that define the records you want to exclude? You’d need to nest the customer test, because it’s an OR.
    e.g.:

    ... payhistory.comment NOT LIKE 'Elit%'
AND not ((customer like 'FTS%' or customer like 'EMC%') AND batchtype = 'PC')

    As a side note, I believe that a LIKE clause may imply an inefficient table scan in some (but not all) cases, so if this query will be used in a performance-sensitive role you may want to check the query plan, and optimise the table to suit.

    • 0