T-SQL is a powerful language, enabling you to handle many different types of set based operations. But having flexible WHERE clauses isn't something that many DBAs deal with on a daily basis. New Author Sotiris Filippidis brings us an article on how you can structure a WHERE clause to handle all types of strange business logic without using dynamic SQL. Read on to learn more about his technique.
Most SQL Server instances are installed with the default values, but that's not always the way it should be. Often there is the need to "move" databases to comply with standards, free up disk space, or some other reason. Moving the system databases can be a little tricky, but author Vince Iacoboni brings us his code and technique for easily doing this for SQL Server 2005 databases.
Isolation levels are used to prioritize the acccess to a resource. SQL Server 2005 extends upon the support for isolation levels in 2000 with several new features including an additional level.
Continuing with this series looking at encryption functions.
Continuing with his series on professional development, Andy Warren takes a look at funding some of your career growth and why it pays to invest in yourself.
A few proposed changes to the newsletter. Read about them and give us some feedback on what you think.
Continuing on with his series on ADTs, Yakov Shlafman takes a look at working with schema changes when your ADT is on a column used as a primary or foreign key.
I came across an interesting blog post on jobs, which actually caught me eye after another blog on time spent on various things, many of which are not necessarily important to your business.
When a function is wrapped around an indexed column in the WHERE clause it will usually prevent the proper usage of that index. This article gives an example and discusses what other options are available.
We are always searching for new ways to improve the performance of our database systems. Raghavendra Narayana brings us a new article that examines an idea for rebuilding partitions and indexes based on data access: in real time!
By HeyMo0sh
One of the biggest challenges I’ve faced in cloud operations is maintaining clear visibility...
By Steve Jones
I come to Heathrow often. Today is likely somewhere close to 60 trips to...
By Brian Kelley
If your organization is spending money, then meaningful results are a must. Pen testing...
Comments posted to this topic are about the item Fun with JSON II
Comments posted to this topic are about the item Changing Data Types
Comments posted to this topic are about the item Answering Questions On Dropped Columns
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 t1.[key] AS row,
t2.*
FROM OPENJSON(
(
SELECT t.* FROM #test_data AS t FOR JSON PATH
)
) t1
CROSS APPLY OPENJSON(t1.value) t2; See possible answers