Forcing SQL Agent Jobs to Fail When Remote Procedures Timeout
Your SQL Agent Jobs may be silently failing when using Linked Servers.
2016-05-02
2,742 reads
Your SQL Agent Jobs may be silently failing when using Linked Servers.
2016-05-02
2,742 reads
An alternative read-only routing technique for non-Microsoft clients.
2015-12-28
2,656 reads
Performance penalties for omitting SQL data types when using ADO.Net or light weight ORMs.
2015-06-22
6,262 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