January 7, 2009 at 12:32 pm
I may just be entirely out of luck.
I went to the application server (ROME) and took a look at it's configuration. It's an application called Misys, and it simply asks for the name of the server to look for, the login, and the db name. There's no place to put in a second, it's not running a native client, nothing.
The only thing I can think of doing (and I don't know if SQL will even do this), is to install a native client on ROME that passes all requests and transactions on to JERUSALEM (principle), acting as a sort of gateway/proxy. Then tell the Misys server to look look for a db at LOCALHOST (ROME).
Any of this possible? If not, I'm giving up the project right now.
January 7, 2009 at 12:41 pm
Ask that person/company that wrote the application if it supports SQL 2005 database Mirroring. If not, find out what they would recommend for high availability alternatives.
January 7, 2009 at 12:57 pm
You could ask them if they'll upgrade to SNAC.
Otherwise, what about a local alias? Then if you have a failure, you change the local alias in one spot. Not ideal, could be programmed or executed remotely, but it would still help.
January 7, 2009 at 2:46 pm
I'm not sure what a SNAC is. Is a local alias sort of what I described earlier?
I contacted the company that makes it, and they said it was impossible. They also said they didn't know what mirroring was, and it sounded like I wanted to replicate the DB.
So, assuming that there is NO way to tell the app server that there is a mirror . . . would it possible to mirror the databases anyway? If the principle goes down, I could log into the application server (ROME) and manually tell it to look at the mirror? Or would the mirror have issues with this?
January 8, 2009 at 3:05 pm
Zuke,
SNAC is the abbreviation for SQL Native Client.
I didn't mention this before but I'd highly recommend you setup some type of lab environment with a few servers to model and work out the details before doing this on other servers. Much better to crash a lab server than the one everyone is using.
And yes, you can mirror a database even if the clients aren't aware of that. Keep in mind that mirroring is a database level concept, meaning that you'd still have to add your server logins to the mirror server and manuall take care of any other dependancies, such as jobs, that aren't part of the database.
January 9, 2009 at 12:30 pm
FYI, I broke down and called Microsoft.
They had me walk through the steps and do it again through the tSQL query window instead of the GUI. Evidently, sometimes the GUI screws up the restore command. In my case, it was restoring the database with the NORECOVERY, but restoring the transaction log WITH RECOVERY. The mirror then failed at that point.
Viewing 6 posts - 31 through 35 (of 35 total)
You must be logged in to reply to this topic. Login to reply