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 James Serra
Organizations increasingly want Snowflake and Microsoft Fabric to coexist without duplicating data or fragmenting...
By Steve Jones
In a previous post, I deployed a model to a database using SQL Compare...
By SQLPals
Reality (And Limits) of Instant File Initialization for Transaction Logs in SQL Server 2022 ...
I have a table with partition on create_timestamp field. Though we're storing all data...
Comments posted to this topic are about the item Adding and Dropping Columns II
Comments posted to this topic are about the item Leveraging DuckDB for OLAP Workloads:...
I have this table in my SQL Server 2022 database:
CREATE TABLE [dbo].[CityList] ( [CityNameID] [int] NOT NULL IDENTITY(1, 1), [CityName] [varchar] (30) , [Country2] [char] (3), [stateprovince2] [char] (2), [Country] [char] (3), [stateprovince] [char] ) ON [PRIMARY] GOI decide to drop the stateprovince2 and country2 columns. What code should I use? See possible answers
