We’re in the process of setting up a MOSS dev environment. We run an anonymous public facing site and an intranet portal, both use MOSS. I’ve migrated our content to a dev server and everything appears to be working… Except, one major-minor detail, approximately 5000 URLs are pointing to the production domain, this makes using the site nearly impossible. As menu item contain bad URLs, page content doesn’t display as it exists on the production site; the list of issues is immense. Has anyone had any experience in dealing with this type of problem? When we originally deployed the site we used DNS and AAC names to handle the domain name change when it came time to go live. In the case of a test server this isn’t an option… in ideas? I’m considering writing a SQL Script to update the URL references and making them relative in the test environment. Thoughts comment?

DO NOT go the SQL Script route!!! Microsoft does NOT support direct updates against the SQL database. You'd be violating your support agreement if you did that. Instead, use the SharePoint API to itterate all the links in all the sites and update them to be relative. This is fully supported and it's probably something you'd eventually want to do in your PROD environment too. When you use relative links, you can move the content to a DEV domain and it still works just fine. I trust that answers your question... Thanks C http://www.cjvandyk.com/blog

NO SQL updates for SharePoint. Use content deployment APIs for migrating huge data between farms Always use relative urls in custom solutions If the stuff is stored in a list , as specfied by Cornelius iterate them to do the updates only using the API Aravind http://aravindrises.blogspot.com