- What did you expect?
  Create an account
:: Home  ::  Downloads  ::  Your Account  ::  Forums  ::
Google Adsense
  • Home
  • Downloads
  • ExpectationReviews
  • Forums
  • Group29 FAQ
  • MovieReviews
  • OtherReviews
  • Stories Archive
  • Submit News
  • Top 10
  • Topics
  • Web Links
  • New at Group29
    ·Movie Review: Eternals [15]
    ·Tuna Is Not The Favorite Pizza Topping in Minnesota
    ·UCLA vs USC preview 2021
    ·Movie Review: Godzilla vs. Kong (2021) [28]
    ·Expectation Review: Captain Marvel [25]
    ·Expectation Review: Avengers: Infinity War [24]
    ·Forum Topic: Update your Facebook property
    ·Web Link: WEP Key Converter
    ·Forum Topic: Why does my IPA file get saved as a zip file in IE?
    ·Web Link: BeyondCompare

    ·Rebelscum Breast Cancer Awareness Charity Patch
    ·BBC Interviews J.J. Abrams About Trek And Wars
    ·CEII: Jabba's Palace Reunion - Massive Guest Announcements
    ·Fathead's May the Fourth Be With You!
    ·Star Wars Night With The Tampa Bay Storm Reminder
    ·Stephen Hayford Star Wars Weekends Exclusive Art
    ·ForceCast #251: To Spoil or Not to Spoil
    ·New Timothy Zahn Audio Books Coming
    ·SDCC: Exclusive Black Series Boba Fett With Han In Carbonite Set
    ·Star Wars Art Exposition May 4th

    Hot trends

     SQL schema version changed between compilation execution
    What do we know?
    Using Microsoft SQL Server 2000. You may see this strange type of error. This is the OLE DB error reported from an ASP.NET web page

    The OLE DB provider 'SQLOLEDB' reported a schema version for table '"{your table here}"' that changed between compilation and execution. OLE DB error trace [Non-interface error: Schema version number changed from compile time ({number}) to run time ({new number}) for ProviderName='SQLOLEDB' TableName='"{your table here}"'.].

    This article has been bumped from the Group29 Tech tips forums.

    The 7359 error indicates that the schema has changed since compilation.
    Microsoft SQL Server has an option "lazy schema validation". If this option is ON (default OFF), SQL Server postpones the execution time
    check as to whether the schema of a table has changed between compilation and execution of a stored procedure. Postponing the check causes performance improvements in cases when a given remote table is not actually used in the query (e.g. in partitioned view against remote table scenario); this may however cause a query to abort in the middle of execution if the schema has indeed changed since compilation.

    This problem typically occurs on stored procedure queries from one linked SQL server to another separate SQL server.

    This Microsoft Article: Configuring OLE DB Providers for Distributed Queries covers changing the configuration for the lazy schema validation.

    The article can be found in the MSDN library at:
    MSDN Home > MSDN Library > Servers and Enterprise Development > SQL Server > SQL Server 2000 > Managing Servers > Configuring Linked Servers

    Original Group29 Forums post: SQL schema version changed between compilation execution

    Posted on Tuesday, February 26, 2008 @ 03:38:53 UTC by BB
    "SQL schema version changed between compilation execution" | Login/Create an Account | 0 comments
    The comments are owned by the poster. We aren't responsible for their content.

    No Comments Allowed for Anonymous, please register
    Group29 Productions

    All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest (c) 2006 by Group29 Productions.

    You can syndicate Group29 Productions news with an RSS Feeder using the file backend.php

    PHP-Nuke Copyright © 2005 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
    Page Generation: 0.16 Seconds

    :: HeliusGray phpbb2 style by CyberAlien :: PHP-Nuke theme by ::