Database

Dictionary Table; Records in only 2 lines (for example, a table of sex: male, female) or as much as 40-50 lines and changing of future data in the table Insert / Update / Delete operations possibility of very low.

Combining these tables in a single table, Does it make sense?


For Example;

TBL_Sex
1 Male
2 Female


TBL_WorkType
1 Full-Time
2 Part-Time


TBL_BloodType
1 A Rh(+) 
2 B Rh(+) 
3 AB Rh(+) 
4 0 Rh(-) 
5 A Rh(-) 
6 B Rh(-) 
7 AB Rh(-) 
8 0 Rh(-) 


Instead of following table;

TBL_DICTIONARY

ID  GROUP      VALUE
--  -----      -----
1   Sex        Erkek 
2   Sex        Kadın 
3   WorkType   Yarım Gün 
4   WorkType   Tam Gün 
5   BloodType  A Rh(+) 
6   BloodType  B Rh(+) 
7   BloodType  AB Rh(+) 
8   BloodType  0 Rh(-) 
9   BloodType  A Rh(-) 
10  BloodType  B Rh(-) 
11  BloodType  AB Rh(-) 
12  BloodType  0 Rh(-)

CREATE PROCEDURE usp_AddBook
--Variables
@Title varchar(200),
@Price decimal(18,2),
@Keywords varchar(200),
@Retired bit

AS

BEGIN
SET NOCOUNT ON

DECLARE @bookId int -- SET A VARIABLE TO HOLD THE BOOKID SQL MAKES

-- INSERT THE BOOK INFORMATION 
SELECT @bookId = Book.ID from Book where Book.Title = @Title


IF @bookId = null
BEGIN
INSERT Book(Title,Price,Keywords,Retired)
VALUES
(@Title,@Price,@Keywords,@Retired)
SELECT @bookId = @@IDENTITY; -- SET THE BOOK ID TO THE ID SQL MADE
END


INSERT INTO BookNumber (BookID)
VALUES
(@bookId)
END

sys.sp_cdc_enable_table procedure 

@schema, @source_name, @source_name

cursor

ALTER PROCEDURE [dbo].[Engagement_Get_StandardYears]
(
	@clientName NVARCHAR(255)=NULL
)	
AS
BEGIN

	SET NOCOUNT ON;
    
	SELECT Distinct [Year] 
		FROM Engagement_Standards 
	WHERE [Year] IS NOT NULL AND [Client Name] like 
	CASE 
		WHEN @clientName IS NULL THEN %
		ELSE @clientName
	END
	ORDER BY [Year];
	
END