Oh CRUD!

Funktionen und Stored Procedures in SQL Server schreiben

Meghan Kwartler

IT Consultant

Warum Stored Procedures für CRUD?

Trennt SQL-Code von anderen Anwendungsebenen

Kapitel 3 N-Tier-Architektur

Warum Stored Procedures für CRUD?

Trennt SQL-Code von anderen Anwendungsebenen
Bessere Sicherheit

Kapitel 3 N-Tier-Architektur

Warum Stored Procedures für CRUD?

Trennt SQL-Code von anderen Anwendungsebenen
Bessere Sicherheit
Performance

Kapitel 3 N-Tier-Architektur

C wie CREATE

CREATE PROCEDURE dbo.cusp_TripSummaryCreate (
  @TripDate as date, 
  @TripHours as numeric(18, 0)
) AS BEGIN INSERT INTO dbo.TripSummary(Date, TripHours) 
VALUES 
  (@TripDate, @TripHours) 
SELECT Date, TripHours 
FROM dbo.TripSummary 
WHERE Date = @TripDate END

R wie READ

CREATE PROCEDURE cusp_TripSummaryRead
    (@TripDate as date)
AS
BEGIN
SELECT Date, TripHours
FROM TripSummary
WHERE Date = @TripDate
END;

U wie UPDATE

CREATE PROCEDURE dbo.cusp_TripSummaryUpdate
    (@TripDate as date,
    @TripHours as numeric(18,0))
AS
BEGIN
UPDATE dbo.TripSummary
SET Date = @TripDate,
    TripHours = @TripHours
WHERE Date = @TripDate
END;

D wie DELETE

CREATE PROCEDURE cusp_TripSummaryDelete
    (@TripDate as date, 
     @RowCountOut int OUTPUT)
AS
BEGIN
DELETE
FROM TripSummary
WHERE Date = @TripDate

SET @RowCountOut = @@ROWCOUNT
END;

Jetzt bist du mit CRUD dran!

Funktionen und Stored Procedures in SQL Server schreiben