Complex Searching
More complex searching is likely to be a requirement in the future, but for many of us, this won't require us to learn much.
2021-10-22
208 reads
More complex searching is likely to be a requirement in the future, but for many of us, this won't require us to learn much.
2021-10-22
208 reads
Learn how to enable or disable full text search for a specific database on a SQL Server instance where the Full Text Search components have been setup.
2021-10-20
Searching for data in a database is something we all do constantly, but few of us use the Full-Text Search features of SQL Server. Yousef Ekhtiari brings us a look at how you can get around some of the limitations of this feature and possibly use it in your application.
2007-07-24
6,469 reads
Are you considering upgrading from SQL Server 2000 to SQL Server 2005? Are you using Full-Text Search? One of the top SQL Server consultants in New York walks us through an interesting issue that you might want to consider before migrating your databases.
2008-01-18 (first published: 2007-03-08)
15,065 reads
This is the second of a two-part article that explores the language features of SQL Full-text Search (SQL FTS), an component of SQL Server 7 and above that allows fast and efficient querying of large amounts of unstructured textual data. Part I dealt with index time language options, covering how words or tokens are broken from the text stream emitted from the iFilters and stored in the index.
2006-07-14
2,945 reads
By Brian Kelley
I will be leading an in-person Certified Information Systems Auditor (CISA) exam prep class...
EightKB is back again for 2026! The biggest online SQL Server internals conference is...
By HeyMo0sh
Working in DevOps long enough teaches you two universal truths: That’s exactly why I...
Hi all, I just started using VS Code to work with DB projects. I...
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
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