After I restore and recover our SQL 2000 standby server, how do I turn it into our production server without having to change the data sources and config files of our applications? Thank you in advance for your help.
That depends on the applications that connect to it. Do they use ODBC? Are they web apps? There are many ways to connect to a SQL server. As long as your database is not in a read only or single user or some state that would not allow active connections you just point your apps to it.
Thanks for your response. Some of our applications use ODBC and some use OLEDB to connect to our SQL server. We have no web apps. I was looking for a way to make our standby server 'impersonate' our production server (in case our production server goes down) without having to re-point our applications to the standby server.
Oh, Ok now I understand...There are a few things you can do to address what you are thinking about.
First, you could install MS cluster service, To do this you would need 2 servers and one or more shared arrays. The way it works is one Node is active the other is Passive. Should you have a hardware failure in the active Node the other one will take over. This however has its problems. You still have one single point of failure. (The Shared drive where your database and log exist) All other things you can do would require changing connection strings and odbc conections. ie.. Log shipping and replication. There is a very good article in this months SQL server magazine about this very subject. Here is link to the Article. You will have to define your buisness needs and use the best approach for your company.
Good Luck.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.