Database

SELECT
    DataPoint,
    STUFF
    (
        (
            SELECT ',' + Site
            FROM YourTable As I
            WHERE I.DataPoint = O.DataPoint
            ORDER BY Site
            FOR XML PATH(''), TYPE
        ).value('.', 'varchar(max)')
        
        -- Remove the first comma:
        , 1, 1, ''
    ) As Sites
FROM
    YourTable As O
GROUP BY
    DataPoint
;

/*
Output:

DATAPOINT   SITES
-----------------
Power       CH
Temp        CH,KC
WindSpeed   CH,KC
*/

DECLARE @cols As nvarchar(max), @query As nvarchar(max);

SET @cols = STUFF
(
    (
        SELECT DISTINCT ',' + QUOTENAME(Site)
        FROM Source
        FOR XML PATH(''), TYPE
    ).value('.', 'nvarchar(max)')
    , 1, 1, ''
);

SET @query = N'SELECT DataPoint, ' + @cols + N' FROM Source PIVOT (COUNT(Site) FOR Site IN (' + @cols + N')) As p';

EXEC(@query);

/*
Output:

DATAPOINT    CH    KC
Power         1     0
Temp          1     1
WindSpeed     1     1
*/

Ppl.GroupID.value('.', 'VARCHAR(6)') AS 'GroupID'

SELECT  *
FROM    Table
WHERE   Name >= 'Azar'

...
as (select TOP 1 g.ID_Pelanggan
,g.Meter_Lama
,g.Nomor_Lama
,g.Meter_Baru
,g.Nomor_Baru
,g.Tanggal
from GANTI_Log g
Order by g.Tanggal desc
)
...

hansoctantan wrote:

is it possible that more than one user can access the same record in this
process?

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

Session 1                                       Session 2
---------------------------------------------   -----------------------------------------------------
Select record A, field named SomeValue is 1

                                                Select record A, field named SomeValue is 1

Begin transaction

Update record A, 
   field named SomeValue is set to 2, 
   an eXclusive lock is taken

                                                Select record A, record is locked, session 2 waits

Some other modifications

                                                Session 2 still waits

Commit the transaction, lock is freed

                                                Session 2 now gets the answer, 
                                                   field named SomeValue is 2 
                                                   (the value session 1 updated)

Mycroft Holmes wrote:

If your users have SA rights using windows authentication then you cannot stop them.