Database

WITH cteOrderedBillingCodes As
(
    SELECT
        T.BillingAccountKey,
        T.BillingCode,
        R.Rank,
        ROW_NUMBER() OVER (PARTITION BY T.BillingAccountKey ORDER BY R.Rank DESC) As RN
    FROM
        #BillingTransactions As T
        INNER JOIN #BillingCodeRank As R
        ON R.BillingCode = T.BillingCode
)
SELECT
    A.UserAccount,
    A.AccountType,
    A.BillingAccountKey,
    C.BillingCode,
    C.Rank
FROM
    #UserAccount As A
    LEFT JOIN cteOrderedBillingCodes As C
    ON C.BillingAccountKey = A.BillingAccountKey
    And C.RN = 1
WHERE
    A.AccountType = 'O'
;

Prices:
    ID (PK, Identity)
    ProductCode (FK to products)
    FromDate (optional)
    ToDate (optional)
    MinimumQuantity (optional)
    MaximumQuantity (optional)
    CustomerPriceGroup (optional)
    Price

JackMisani wrote:

Which is the best solution in your opinion?

Bastard Programmer from Hell
If you can't read my code, try converting it here[^]

JackMisani wrote:

that rarely change while other fields are prices fields that change different times per day.

indian143 wrote:

@ModifiedOn datetime=getdate

create  PROCEDURE [dbo].[usp_Update_Service_Program_Detail] 
    @PK_Service_Program_County_RateCap_Detail int,
    @Unit_Type int,
    @Rate_Cap decimal(15,2),
    ----@County int,
    @ModifiedBy nvarchar(50),
    @ModifiedOn datetime=getdate
AS
BEGIN 

select '220' 'Col' -- Test statement
    --Logic is here         
END  

exec usp_Update_Service_Program_Detail @PK_Service_Program_County_RateCap_Detail= 53196434, @Unit_Type=1
, @Rate_Cap=100
, @ModifiedBy='aaleemmo'
, @ModifiedOn=''

Member 13200024 wrote:

What is the biggest pet peeve(s) DBAs have with developers?