Why does changing a table on a SQL Server 7.0 server cause "OLE DB provider 'SQLOLEDB' supplied inconsistent metadata. An extra column was supplied during execution that was not found at compile time." to occur when query the table from a SQL Server 2000 server via link to other. In this article by James Travis, he shows you what the problem is and how to fix it.
2002-02-28
15,508 reads
SQL Server 7 has a number of bugs that occur on multi-processor machines. This article presents a concise listing of these bugs.
2001-05-30
3,337 reads
If you use performance log data and need to conduct time-sensitive analysis, watch out for this little feature in Windows 2000.
2001-05-15
3,057 reads
By Brian Kelley
Following the advice in Smart Brevity improves communication.
By John
Microsoft has released SQL Server 2025, bringing big improvements to its main database engine....
By Steve Jones
A customer was asking about what certain items in Redgate Monitor mean. They have...
Comments posted to this topic are about the item Which Table I
Comments posted to this topic are about the item Using Python notebooks to save...
Comments posted to this topic are about the item Your AI Successes
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
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