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,502 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 alevyinroc
T-SQL Tuesday is a monthly blog party hosted by a different community member each...
By DataOnWheels
It has been a while since my last T-SQL Tuesday blog. When I saw...
The last T-SQL Tuesday of the year is hosted by my good friend Mike...
Comments posted to this topic are about the item What is the PRODUCT
Comments posted to this topic are about the item Metadata Driven Pipelines (Incremental Load):...
Comments posted to this topic are about the item Metadata Driven Pipelines (Incremental Load):...
In SQL Server 2025, what does this return?
CREATE TABLE Numbers ( n INT) GO INSERT dbo.Numbers ( n ) VALUES (1), (2), (3) GO SELECT PRODUCT(n) FROM dbo.NumbersSee possible answers