2023-05-01
152 reads
2023-05-01
152 reads
Once you've done a number of SQL code-reviews, you'll be able to identify signs in the code that indicate all might not be well. These 'code smells' are coding styles that, while not bugs, suggest design problems with the code. In this PDF, Phil Factor's put together 119 of those code smells so you can see what to avoid and why.
2014-09-25
12,476 reads
By Steve Jones
This is timely, as I’m currently on a boat in the Adriatic taking a...
You can find the slides and SQL scripts for my session “Spice up your...
By SQLPals
How to Clear the SSMS Cache (SSMS 21 and Later) Updated...
Telp/Wa 628218200203 Jl. Batu Ceper No.18 A-B, RT.1/RW.2, Kb. Klp., Kecamatan Gambir, Kota Jakarta...
Telp/Wa 628218200233 Komplek Apartemen Grand Kartini, Ruko. 18, Jl. Kartini Raya No.57, RT.3/RW.2, Kartini,...
Telp/Wa 628217555651 Wisma 46 Lantai Dasar, Jln. Jend. Sudirman Kav. 1, RT.5/RW.3, Senayan, Kec....
We have this code that sets some status values and then queries them using the CHOOSE() function in SQL Server 2025.
CREATE TABLE Status
(
StatusID INT,
StatusDescription VARCHAR(20)
);
GO
INSERT dbo.Status
(
StatusID,
StatusDescription
)
VALUES
(0, 'Uncategorized'),
(1, 'Active'),
(2, 'Inactive'),
(3, 'Temp');
GO
SELECT CHOOSE(StatusID, 'Unknown', 'Active', 'Inactive', 'Temporary')
FROM Status;
When the SELECT runs, what is returned? See possible answers