The second part of the series by Darren Fuller on SQL Server change management, version control, and ways that you can automate this approach. If you do any type of SQL Server development, having a version control system is key to ensuring stability and keeping to your deadlines. Whether you agree with this approach or not, it's good information to have.
Developing applications for SQL Server usually results in a variety of access methods that the programmers use. A data access layer class, given to the developers, is usually seen as the best practice, but one that isn't usually implemented. In fact, in most software I've built, each developer uses his own method, or may cut and paste from another, but rarely is there a central access class. New Author Patryk Nowakowski brings us his solution using ADO.NET.
Automating SQL Server tasks is the sign of an experienced DBA. One who doesn't waste time on repetitive tasks that can be easily setup in a job, task, or some other scheduling process to run when they need to run. Haidong Ji has written a number of articles on how to perform automation and brings us yet another technique. This time he looks at managing your backup files, something that we all need to do, but all too often forget to do.
Murphy's law has struck us all, as evidenced by the disaster entries we've received in the past. Imceda software, makers of Litespeed are sponsoring a new contest, looking for your nightmares.
NGS Software is in the security business and have been very successful in finding vulnerabilities in many products, notable SQL Server. They have used their expertise to build products to help you better secure your systems. Dale Corey looks at one of those products, NGSSquirrel, which does vulnerability assessment.
What do your programmers do with nulls? Do they know nullif, isnull, what about the powerful coalesce function? Do they think DBA's look at the world differently? Why, it's all code isn't it?
SQL Server change management is tough. The tools don't integrate with version control systems, there isn't good administrative controls to enforce control, and often you need to buy a third party tool to make this work. New Author Darren Fuller takes a look at the various ways in which you can implement version control in SQL Server. This is part one of a four part series on version control in SQL Server.
Designing a SQL Server database is a challenging task. Making decisions about how to build tables, their relations, etc. can be a full time job for any DBA helping to build an application. Lookup tables are a part of just about every application that you work with or build a back end for. Leo Peysakhovich brings us an article on database design that deals specifically with lookup tables.
The highly anticipated Beta 2 of SQL Server 2005 aka Yukon, was released today (Monday, July 26).
Monitoring your SQL Servers is something every DBA must do. Checking job status, disk space, etc. is a frequent question seen in our forums. Pearl Knowledge Solutions has developed a product to help you easily setup monitoring on your servers from a web interface. SQLCentric gets 4 stars from author Bruce Szabo; read his detailed review on this fine product.
By Vinay Thakur
Continuing from Day 3 where we covered LLM models open/closed and their parameters, Today...
By Steve Jones
One of the nice things about Flyway Desktop is that it helps you manage...
By HeyMo0sh
Microsoft Fabric (not to be confused with the more general term “fabric” in DevOps)...
I'm fairly certain I know the answer to this from digging into it yesterday,...
Hi Team, I am trying to refresh the Azure Synapse Dedicated pool from production...
hi everyone I am not sure how to write the query that will produce...
I have some data in a table:
CREATE TABLE #test_data
(
id INT PRIMARY KEY,
name VARCHAR(100),
birth_date DATE
);
-- Step 2: Insert rows
INSERT INTO #test_data
VALUES
(1, 'Olivia', '2025-01-05'),
(2, 'Emma', '2025-03-02'),
(3, 'Liam', '2025-11-15'),
(4, 'Noah', '2025-12-22');
If I run this query, how many rows are returned?
SELECT *
FROM OPENJSON(
(
SELECT t.* FROM #test_data AS t FOR JSON PATH
)
) t; See possible answers