Script object as alter using cache instead of current code

meyerovbmeyerovb Posts: 21
edited April 5, 2011 12:52PM in SQL Prompt Previous Versions
When doing script object as alter I expect to see the current version.

However, if I do it once, change it, then do it again without refreshing the cache, I see the old version, which may lead to overwrites of new code.

Please change script object as alter to get latest version instead of cached version.
· Share on Twitter

Comments

  • James BJames B Posts: 1,124 Silver 4
    Thanks for your post. We already have an internal job to improve the refreshing of the cache (ref. SP-2962)
    I've added a note of this topic to that, along with the other requests we've had.

    I'm not currently sure when this is likely to be implemented I'm afraid, but hopefully it'll get looked at.
    Systems Software Engineer

    Redgate Software

    · Share on Twitter
  • meyerovbmeyerovb Posts: 21
    Refreshing the cache is unrelated to script object as alter. Scripting as alter should not use the cache at all, but the live database element. If need be partially refresh the relevant cache before generating the script from it. That's just my 2 cents about how I feel it should operate.
    · Share on Twitter
  • James BJames B Posts: 1,124 Silver 4
    Makes sense. I linked back to this topic anyway, so that should get noted.
    Systems Software Engineer

    Redgate Software

    · Share on Twitter
Sign In or Register to comment.