It seems like every DBA has a USB stick or a shared drive filled with scripts they can pull up in almost any situation. How can I build such a library of T-SQL files?
2023-06-26
Deadlocks can occur in any database system, and SQL Server is no exception. In this article, we look at the steps I used to detect and resolve deadlocks in stored procedures.
2023-06-23
SQL Server supports working with JSON data and provides many different functions that can be used. SQL Server 2022 has expanded the ability to check if the JSON format is valid using the ISJSON function which we will cover in this article.
2023-06-19
SQL Server Auditing utilizes Extended Events in SQL Server. Although it is a feature-rich native solution available in all editions, you'll realize that when you start configuring the Audit and Specifications the filter options are not that widely documented or intuitive.
2023-06-05
I enjoyed writing scripts to manage the servers, as it taught me a lot about the internals of SQL Server. Many of these scripts were eventually automated using SQL Server’s agent to run and save data on the different servers so we could review the results, looking for issues.
2023-05-31
In this article, we look at an ensemble AI model which can be considered a collection of two or more AI models that complement each other to arrive at an outcome for a set of historical data.
2023-05-26
One of the slowest parts of any application is data retrieval and in this article, we look at how to cache SQL Server data for a web application.
2023-05-22
The tip, Views in SQL Server, explored the purpose of views, creating views examples, and benefits of views. A view is a virtual table that references the actual database tables stored in the database. What if someone changes the underlying table structure, such as renaming the column, adding a new column, or dropping the table? What is the impact of changing schema on views? How can we stop any schema changes if the view references the schema?
2023-05-08
This article examines how one can structure a pipeline for processing real-time data using Kafka and Informatica.
2023-04-26
4,777 reads
As much as we tell people to use SCHEMABINDING and avoid SELECT *, there is still a wide range of reasons people do not. A well-documented problem with SELECT * in views, specifically, is that the system caches the metadata about the view from the time the view was created, not when the view is queried. If the underlying table later changes, the view doesn't reflect the updated schema without refreshing, altering, or recreating the view. Wouldn't it be great if you could stop worrying about that scenario and have the system automatically keep the metadata in sync?
2023-04-17
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...
Comments posted to this topic are about the item Risk Vs Reward, The never...
Telp/Wa 628218200203 Jl. Cideng Timur No.11 F, RT.5/RW.4, Petojo Utara, Kecamatan Gambir, Kota Jakarta...
Telp/Wa 628218200233 Kem Tower, Jl. Landas Pacu Barat No.Kav 2 Blok B, RW.10, Gn....
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