Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

  • jacob phillips 130 posts 372 karma points
    Jun 12, 2014 @ 02:08
    jacob phillips

    Reseeding umbracoNode with DBCC CHECKIDENT

    I have an old Umbraco install with 180,000 or so nodes.

    I want to preserve the ids in the umbracoNode table for several reasons, the most important being old web pages that pull up content using the id (i.e. permalink). Through redirects and custom uses of ISAPI Filters, it is very convenient to redirect requests that are no longer on the main production instance of the application, to a handler or other custom code to regenerate old content on the fly, or just point to an archive instance of old Umbraco.

    In a newer installation that did not import this old data, the id started over. There is minimal overlap at this point, but I want to address this quickly.

    On a test instance, I have tried running DBCC CHECKIDENT on the umbracoNode table with a new seed, and it appears to not have caused any problems. I created some content using the Umbraco Back Office and the newest entries are assigning identities > 200,000

    DBCC CHECKIDENT(umbracoNode, reseed, 200000)

    I just wanted to get a second opinion if this could cause any problems to the application.

Please Sign in or register to post replies

Write your reply to: