2006-08-23
904 reads
2006-08-23
904 reads
2006-08-16
895 reads
2006-08-07
905 reads
After agreeing on our design goals we began looking for technologies to support them. It turned out that SQL Server™ Service Broker offered the asynchronous messaging support we needed and, since the message-queuing infrastructure is tightly integrated with the SQL Server database engine, our existing database backup, administration, and failover procedures could cover our messaging solution as well.
2006-07-26
1,736 reads
2006-07-17
908 reads
2006-07-13
930 reads
2006-07-10
980 reads
2006-07-04
936 reads
One way to understand Service Broker is to think of it as a postal service. New author Sachin Dedhia brings us a fantastic introduction to the Service Broker including the code to setup and begin working with queues, conversations and contracts. If that doesn't make sense, you need to read this article.
2006-05-08
9,801 reads
One of the less exciting, but perhaps very powerful new features in SQL Server 2005, the Service Broker is an asynchronous communications method. MVP Srinivas Sampath brings us the second part of his series looking at what you can accomplish with a practical example.
2005-08-30
13,129 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...
Hello team Can anyone share popular azure SQL DBA certification exam code? and your...
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
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