College Life
Life at college is good. It's a time in many people's lives that they'll never forget. Steve Jones asks if you'd want to go back to your adult roots.
Life at college is good. It's a time in many people's lives that they'll never forget. Steve Jones asks if you'd want to go back to your adult roots.
The I/O system is important to the performance of SQL Server. When configuring a new server for SQL Server or when adding or modifying the disk configuration of an existing system, it is good practice to determine the capacity of the I/O subsystem prior to deploying SQL Server. This white paper discusses validating and determining the capacity of an I/O subsystem. A number of tools are available for performing this type of testing. This white paper focuses on the SQLIO.exe tool, but also compares all available tools. It also covers basic I/O configuration best practices for SQL Server 2005.
Business Intelligence Architect Bill Pearson introduces the useful .AllMembers function, reinforcing the basic concepts, as always, with hands-on practice examples.
Does it suck to be a corporate programmer? Joel Spolsky things so, but Steve Jones takes issue with it.
An exploration of the process of translating a conceptual model to a logical model, and ultimately, a faithful implementation using T-SQL.
Most SQL Server DBAs have been taught that cursors are bad and should not be used. However there are some cases and places where they might be useful. SQL Server guru Andy Warren brings us an example of where they may be handy.
Locking is a major part of every RDBMS and is important to know about. It is a database functionality which without a multi-user environment could not work. The main problem of locking is that in an essence it's a logical and not physical problem. This means that no amount of hardware will help you in the end. Yes you might cut execution times but this is only a virtual fix.
Backing up a database is one of the most important things you need to do when having a database driven application. It 's only all of your data in there, right? But often developers and management don't realize the importance of backups and overall proper backup strategy for the most important side of the business – data and it's consistency.
Computer professionals are constantly complaining about the documentation for the software they use. And are notorious for not documenting their own code very well. Longtime author Raj Vasant brings us a short article with some suggestions on how to go about documenting your databases.
By Vinay Thakur
Continuing from Day 4 where we learned Encoder, Decoder, and Attention Mechanism, today we...
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...
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