Problem:
*, **, ***
Solution:
Common Error Messages:
1) The server network address TCP:// can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational.
References:
[1]Mirroring vs Replication and Others http://nilebride.wordpress.com/2011/07/24/log-shipping-vs-mirroring-vs-replication/
[2] Introduction http://www.guillesql.es/Articulos/database_Mirroring_SQL_Server_2005_2008.aspx
[3] High Recomended http://www.mssqltips.com/sqlservertip/1705/implementing-database-mirroring-in-sql-server-2005-across-domains/
[4] Resume http://blog.capside.com/2012/04/10/como-configurar-db-mirroring-utilizando-certificados-sql-server-2008-r2-db-mirroring-untrusted-servers-using-certificates/
[5] Mirroring 2008 using GUI http://www.databasejournal.com/features/mssql/article.php/3828341/Database-Mirroring-in-SQL-Server-2008.htm
[6] * http://blog.sqlauthority.com/2010/01/11/the-server-network-address-tcpsqlserver5023-can-not-be-reached-or-does-not-exist-check-the-network-address-name-and-that-the-ports-for-the-local-and-remote-endpoints-are-operational-microso/
[7] ** http://www.gknzcfc.net/subsite/server-tcp-provider-failed-to-listen-on-1433-tcp-port-is-already-in-use.html
[8] *** https://www.simple-talk.com/sql/database-administration/sql-server-endpoints-soup-to-nuts/
[9] SQL Server Data Encryption http://selfhandle.com/post/2011/08/05/How-to-enableremove-Transparent-Data-Encryption-%28TDE%29.aspx
Subscribe to:
Post Comments (Atom)
Posts
No comments:
Post a Comment