Two Best Practices!
This article presents two best practices. One is about how to construct good table aliases, the other is about using ANSI join syntax. Good stuff!
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.
Blogs
Learn Better: Pause to Review More
By Brian Kelley
If you want to learn better, pause more in your learning to intentionally review.
Azure SQL Managed Instance Next-Gen: Bring on the IOPS
By John
If you’ve used Azure SQL Managed Instance General Purpose, you know the drill: to...
SQL, MDX, DAX – the languages of data
By DataOnWheels
Ramblings of a retired data architect Let me start by saying that I have...
Forums
Faster Data Engineering with Python Notebooks: The Fabric Modern Data Platform
Comments posted to this topic are about the item Faster Data Engineering with Python...
Which Result II
Comments posted to this topic are about the item Which Result II
JSON Has a Cost
Comments posted to this topic are about the item JSON Has a Cost, which...
Question of the Day
Which Result II
I have this code in SQL Server 2022:
CREATE SCHEMA etl;
GO
CREATE TABLE etl.product
(
ProductID INT,
ProductName VARCHAR(100)
);
GO
INSERT etl.product
VALUES
(2, 'Bee AI Wearable');
GO
CREATE TABLE dbo.product
(
ProductID INT,
ProductName VARCHAR(100)
);
GO
INSERT dbo.product
VALUES
(1, 'Spiral College-ruled Notebook');
GO
CREATE OR ALTER PROCEDURE etl.GettheProduct
AS
BEGIN
exec('SELECT ProductName FROM product;')
END;
GO
When I execute this code as a user whose default schema is dbo and has rights to the tables and proc, what is returned? See possible answers