Switched configure.php to diff DB, now error on original DB

On my development environment, I switched the server address in both copies of configure.php (regular and /admin), and pointed to a different DB that I backed up from an existing Zen install.

All was good. The "new" site came up fine.

But now, when switching both configure.php addresses BACK to the DB server address they originally contained, and ran fine, I get an error when bringing up the site.

What specifically is the error you're receiving? The most likely cause is that you futzed the edit when you changed it back.

Sorry, I get:

Sorry!
There seems to be a problem connecting to our database. Please give us a few minutes to remedy the problem. Thank you.

And I've checked that the server address, username and PW are matching, and the same they were previously in both versions of configure.php

It seems like, given that it worked earlier today on the original DB (and, in fact, just worked on the secondary DB I pointed it at, too), that I should be good to go either way.

Could pointing an install at a new DB somehow mess up the other DB? This isn't making much sense, is it?

Could pointing an install at a new DB somehow mess up the other DB?

Nope. As long as you enter the correct database information, it should still connect just fine. You left the original database intact and unchanged? Is all the other info the same, server paths, etc? Or is the second install on a different server? If on the same server, are you allowed two databases? Any possibility your host did something?

I'll check with them (GoDaddy). Worst-case, I've got the same original DB on my desktop I can theoretically upload and try that.

My concern was if, somehow, disconnecting the install from a certain DB somehow messed things up.

Ah, Godaddy. Their database setup is different than the rest of the world. They put the files and the database on different servers, plus there's some other screwball setting that needs to be adjusted for database connectivity.