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,520 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,340 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,058 reads
By Steve Jones
We had an interesting discussion about deployments in databases and how you go forward...
By ChrisJenkins
You could be tolerating limited reporting because there isn’t an off the shelf solution...
A while back I wrote a quick post on setting up key mappings in...
Comments posted to this topic are about the item Remotely Engineer Fabric Lakehouse objects:...
Comments posted to this topic are about the item Creating JSON III
Comments posted to this topic are about the item Testing is Becoming More Important
In a SQL Server 2025 table, called Beer, I have this data:
BeerIDBeerName 1Becks 2Fat Tire 3Mac n Jacks 4Alaskan Amber 8KirinI run this code:
SELECT JSON_OBJECTAGG(
BeerID: BeerName )
FROM beer;
What are the results? See possible answers