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 Andy Warren
Somehow two years have elapsed since my last update; hopefully it won’t be that...
By Steve Jones
If someone is trying to convince you it’s not a pyramid scheme, it’s a...
By Steve Jones
I was looking back at my year and decided to see if SQL Prompt...
Hi experts, I have a 3+ TB database on a 2019 sql server which...
Comments posted to this topic are about the item The North Star for the...
Comments posted to this topic are about the item Multiple Escape Characters
In SQL Server 2025, I run this code (in a database with the appropriate collation):
SELECT UNISTR('%*3041%*308A%*304C%*3068 and good night', '%*') AS 'A Classic';
What is returned? See possible answers