My opinion, and it's just an opinion... and really has little to do with "can you, technically..."
If it were me, and I had a choice, I'd change the site code certainly, and if possible, the name of the server as well. I know sometimes politics or processes don't allow that. But the reasoning is because if I'm looking at logs or trying to troubleshoot something... and it's the same sitecode and servername showing up in the logs... is it a remnant of the old/possibly failed site... or the new site config that's in that log? I'd have less guesswork on t-shooting the NEW site if it were a new servername and sitecode. On Fri, Jan 20, 2017 at 2:52 PM, Heaton, Joseph@Wildlife < [email protected]> wrote: > So, I still have database replication issues. Other than that, everything > works fine. I’m thinking of nuking one of my secondary sites, and > reinstalling, hoping that will resolve the issue. If it does for that > site, I’ll do the other 14. > > > > I know there is a Delete, and Uninstall option. I’m thinking Uninstall is > the way to go, so that the files are removed from the secondary side. Is > this process as simple as doing the Uninstall, then recreating them? Can I > use the same site code and name that way, or do I have to change? > > > > Thanks, > > > > Joe Heaton > > Information Technology Operations Branch > > Data and Technology Division > > CA Department of Fish and Wildlife > > 1700 9th Street, 3rd Floor > > Sacramento, CA 95811 > > Desk: (916) 323-1284 > > > > Every Californian should conserve water. Find out how at: > > [image: SaveOurWater_Logo] <http://saveourwater.com/> > > SaveOurWater.com <http://saveourwater.com/> · Drought.CA.gov > <http://drought.ca.gov/> > > > -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, http://www.smguru.org
