Best Practices in an Adhoc Environment
This short article looks at some mistakes developers should avoid when they also have the task of designing the database, database objects, or TSQL used to access it.
Duplicate Indexing Woes
Why would you ever create duplicate indexes? Does that even make sense? Steve Jones isn't sure, and that's for another day, but it sure caused him some problems. Follow along and find a solution for tracking these down.
Full Text Indexing - Text Parsing Routine
Full text indexing is interesting, but not always easy for the user to apply well. Chris has some ideas about to make that
Superior SQL Builder v1.3 released
Red Earth Technologies announces the release of version 1.3 of Superior SQL Builder, its SQL tool that allows users to visually build complete SQL scripts without typing any code.
Superior SQL Builder introduces new SQL scripting technology, allowing users to quickly and easily transform their database data. In version 1.3 this scripting technology has been extended and enhanced so that complex SQL scripts can be built in less time and with greater ease.
Codd's Rules
Frank gives us his take on Codd's Rules. If you're new to databases, this is the core theory that resulted in the development of RDBMS. If you're more experienced with databases, maybe now is a good time to return to the rules to see how you're doing!
Server side tracing in SQL Server, using system stored procedures
Ever wanted to use the SQL Trace system stored procedures instead of Profiler, but got intimidated by the cryptic system stored procedure calls? Then this article is just for you. It will show you how to use SQL Trace system stored procedures and provide you with wrapper stored procedures, that can be used to quickly get server side traces up and running.
Navigating Yukon - A First Look
Steve Jones takes a first look at the next version of SQL Server. It's been sitting for some time, but with the NDA lifted, here's some first impressions of the tools.
Worst Practice - Defining Rows that Exceed The Max Length
Andy started writing about worst practices a long time ago and returns this week with one that is short and sweet - why defining rows that exceed 8060 characters is a very bad idea and how you can avoid it.
Service Pack 1 for SQLCentric v.1.2.3 Now Available
This service pack contains bug fixed, plus enhancements including test email button, sorting, and drill down.
Sequential Numbering
Needing to number rows with a sequential id is a pretty common request. Sometimes it's because the user hasn't made the transition to 'set based' thinking, sometimes it really is a valid request (more or less!). Greg provides several different techniques to help you achieve sequential numbering.
Blogs
T-SQL Tuesday #192: What career risks have you taken?
By James Serra
I’m honored to be hosting T-SQL Tuesday — edition #192. For those who may...
AI: Blog a Day – Day 3: LLM Models – Open Source vs Closed Source
By Vinay Thakur
Continuing from Day 2 , we learned introduction on Generative AI and Agentic AI,...
How to Parameterize Fabric Linked Services in Azure Data Factory for Azure Devops Deployment
Quite the title, so let me set the stage first. You have an Azure...
Forums
how to write this query?
hi everyone I am not sure how to write the query that will produce...
Rollback vs. Roll Forward
Comments posted to this topic are about the item Rollback vs. Roll Forward
Foreign Keys - Foes or Friend?
Comments posted to this topic are about the item Foreign Keys - Foes or...
Question of the Day
Fun with JSON I
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