We have a mirrored SQL 2005 server. When Server1 fails, we want people to be automatically redirected to Server2. Is this a function of DNS or of SQL Server? How do I accomplish this?
We have a mirrored SQL 2005 server. When Server1 fails, we want people to be automatically redirected to Server2. Is this a function of DNS or of SQL Server? How do I accomplish this?
Hello, Izu. If you want to implement auto-failover mirroring server, 3 servers are needed. It's something like this : +--- Witness ---+ | | Master ---> Mirroring Simply speaking, Witness watch two servers and if something happens on Master, Witness changes Mirroring server into Master server (MS call this as Principal server, I think) You can find more detail article on SQL server's Books Online.
I understand how the mirroring works on the backend but how is the client application going to know which server to write to? Is that done in SQL Server or through DNS?
Refer this : SQL Server 2005 Books Online Overview of Database Mirroring http://www.**--****.com/ I have little time now. sorry.
Izu, I skimmed over the link Kenial provided and still am not clear about the answer to your question. Did you ever figure out the answer? I have an application where the SQL Database is configured within (I give it the server name, database name and SQL access info). I did not write the app and was wondering if it could be used with SQL mirroring. Thanks New2SQL
I'd start by checking the state_desc column etc in the sys.databases view. -- Tibor Karaszi, SQL Server MVP http://www.**--****.com/ http://www.**--****.com/
1.Connection from SQL Server 2005 to SQL Server 2000 stalling
We have an SSIS package running on a SQL Server 2005 machine. It is a series tasks where it truncates a table on the 2005 machine and repopulates the table by querying the equivalent table on our SQL Server 2000 machine. The problem we are experinecing is that some of the tasks seem to stall and the package, which should take about an hour and a half to run, instead runs forever. We have determined however that it is not a SSIS problem because we converted the SSIS package to a simple query job and that stalls also. Now today, I tried to run a simple select from the 2005 machine on a table on the 2000 machine and it just stalled after returning about 700 of the 4000 rows in the table. Any of you SQL Server or Network wizards ever hear of this problem before? Dave
2.Connection SQL Server 2005 with DNS hostname mismatch
When using the MS SQL 2005 JDBC driver, I now need to have the DNS name resolution to the client correctly set up. If not I get the following error: SQLState: 08S01 SQLError: 0 Message: hostname : hostname Where "hostname" is the client host name. It doesn't seem to matter if I use an IP address or hostname in my connection URL. When searching the net, I have seen a similar error, but not exactly the same, where the message is "Hostname: hostname not found" (once again, here "hostname" is the client machine) where they suggested the issue was the DNS name conflict. I found the error goes away if the client machine's hostname match the DNS name used for the same IP addess that the DB server is using. One work-around is to set hostname on the client to the IP address being used. I know the right thing to do is set the hostname and the DNS name lookup the same, but I have a customer who doesn't want to do this. They didn't have to for 2003, and they don't want to for 2005. Sigh. Is there a way to disable this feature?
3.Connection SQL Server 2005 with bad DNS
When using the MS SQL 2005 JDBC driver, I now need to have the DNS name resolution to the client correctly set up. If not I get the following error: SQLState: 08S01 SQLError: 0 Message: hostname : hostname Where "hostname" is the client host name. It doesn't seem to matter if I use an IP address or hostname in my connection URL. When searching the net, I have seen a similar error, but not exactly the same, where the message is "Hostname: hostname not found" (once again, here "hostname" is the client machine) where they suggested the issue was the DNS name conflict. I found the error goes away if the client machine's hostname match the DNS name used for the same IP addess that the DB server is using. One work-around is to set hostname on the client to the IP address being used. I know the right thing to do is set the hostname and the DNS name lookup the same, but I have a customer who doesn't want to do this. They didn't have to for 2003, and they don't want to for 2005. Sigh. Is there a way to disable this feature?
4.Microsoft DNS and Sql server 2005
Hi Folks, I was wondering if there is a plugin to Microsoft DNS server that will enable to store zones in slq database as supposed to file system. If so could some one provide me pointers. The scenario that I am trying is to create millions of sub-domains programatically. Thanks, Bharat
Happy Thanksgiving. I have a client trying to connect to a new VPN for MS SQL 2005 - and is getting the following error: Unable to process request Internal error - DNS resolution resulted in a local IP I'm not finding much on google and don't really know much about VPNs.. any ideas? -B
6. DNS CName and SQL 2005 Bulk Insert
7. Migrating SBS 2003 to Windows 2003 Server, AD, DNS, Exchange Server and SQL Server 2005
Users browsing this forum: No registered users and 40 guest