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,438 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,332 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,052 reads
By Steve Jones
The PASS Summit goes on tour this year, with the final date the first...
By Arun Sirpal
The Business Critical tier of Azure SQL Managed Instance offers the read-scale out feature...
By Rohit Garg
Cloud computing is essential for modern development, data storage, and scalable applications. Setting up...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Comments posted to this topic are about the item Sometimes, Troubleshooting Is Hard
Comments posted to this topic are about the item Dimensional Modeling Case Study, Part...
I have this table in SQL Server 2022:
CREATE TABLE CustomerLarge (CustomerID INT NOT NULL IDENTITY(1, 1) CONSTRAINT CustomerLargePK PRIMARY KEY CLUSTERED , CustomerName VARCHAR(20) , CustomerContactFirstName VARCHAR(40) , CustomerContactLastName VARCHAR(40) , Address VARCHAR(20) , Address2 VARCHAR(20) , City VARCHAR(20) , CountryCode CHAR(3) , Postal VARCHAR(20) ) GOIf I check the columns_updated() function return in a trigger, what is the data returned? See possible answers