2023-03-27
313 reads
2023-03-27
313 reads
Several years ago, I was brought in on a project to review a database design. I was provided a time for a meeting. No written requirements were available, but I generally knew what the system was supposed to do. No before/after schema images showed what was being changed were available. Still, I was assured that […]
2023-03-25
107 reads
Zero downtime used to be more important in Steve's job, but lately it seems customers aren't as concerned.
2023-03-24
119 reads
Poor patterns and practices are code smells. Steve Jones notes we have plenty in T-SQL.
2023-03-22 (first published: 2015-10-05)
563 reads
We need to measure and monitor things to become better, but we need to keep an eye on what the actual goal is from this monitoring.
2023-03-20
153 reads
A week ago I was in Pasadena attending the SCaLE 20x conference, a gathering of many different open-source communities discussing the technologies and platforms that draw them together. I was fortunate enough to hear some excellent presentations on PostgreSQL and give two talks as well. After the first round of talks on Friday morning a […]
2023-03-18
91 reads
A guest editorial from Andy Warren that looks at annual training to try and improve security.
2023-03-17 (first published: 2015-08-21)
190 reads
Are you a good writer? You should be. Steve Jones notes that communication skills are not only important, but that poor ones can set you apart in a way you might not like.
2023-03-15 (first published: 2014-01-20)
329 reads
This editorial was originally published on Jan 16, 2007. It is being republished today as Steve is on vacation. This one looks at the potential issues with data mining when data might be shared between companies.
2023-03-13 (first published: 2011-11-10)
153 reads
I honestly enjoy writing editorials. Something pops into my tiny brain next to something else, and I'm off. However, today, as I started to write on the topic of learning, I suddenly felt like I had just written this same editorial. I go and look, sure enough, several of my recent editorials have been on […]
2023-03-12 (first published: 2023-03-11)
86 reads
By Brian Kelley
If you want to learn better, pause more in your learning to intentionally review.
By John
If you’ve used Azure SQL Managed Instance General Purpose, you know the drill: to...
By DataOnWheels
Ramblings of a retired data architect Let me start by saying that I have...
Comments posted to this topic are about the item Faster Data Engineering with Python...
Comments posted to this topic are about the item Which Result II
Comments posted to this topic are about the item JSON Has a Cost, which...
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