Site sponsored by: Idera Try Idera’s new SQL admin toolset
SQL Server Performance

  • Home
  • Articles
  • Forums
  • Tips
  • FAQ's
  • Blogs
  • Software
  • Books
  • About Us
RSS Feeds
Sign in | Join


FAQ Topics

All FAQ's
General DBA
General Developer
DBA Performance Tuning
Developer Performance Tuning
Clustering
Error Messages

SQL Server 2008 - Worth the Wait

SQL Server’s first significant upgrade in three years features a number of envelope-pushing enhancements and improvements. Which will have the greatest impact on SQL administration and development? More...
Latest Articles

Slowly Changing Dimensions in SQL Server 2005
Audit Data Modifications
SQL Server 2008’s Management Data Warehouse
Same Report but Different Methods in SQL Server Reporting Services ...

More     
 
Latest FAQ's

How to Integrate Performance Monitor and SQL Profiler
SSIS Lookups are Case Sensitive
Convert Number to Words in SSRS
After installing SP2 on SQL Server 2005 x64, when trying to ...

More     
   
Latest Software Reviews

SQL Server DBA Dashboard
SwisSQL DBChangeManager
SQLMesh - SQL Server Search Tool
SoftTreeTech SQL Assistant

More     

Database Mirror Certificate Expired


Printer friendly

When certificates are created, if you didn’t specify the EXPIRY_DATE parameter with an expiry date, it will be set to one year.  Hence the certificate will expire in one year.  The following method can be used to specify an expiry date for a certificate.

CREATE CERTIFICATE cert_Mirror
WITH SUBJECT = 'database mirroring certificate',
EXPIRY_DATE = '12/31/2030'; 

Although you are not able to change the expiry date for an existing certificate there is a workaround that can be used.

Let's say MIR1 and MIR2 are the two database server instances where mirror is running.

1. Create a new certificate on MIR1 giving appropriate expiry date as specified earlier.
2. Export or backup the public key part of the certificate.
3. Restore the certificate on MIR2. Make sure that this certificate is restored under the same owner of the old certificate.
4. Alter the endpoint at MIR1 to user new certificate.

ALTER ENDPOINT endpointname FOR DATABASER_MIRRORING AUTHENTICATION = new certificate name

5. Drop old certificate for completeness.

You may need to carry out the same steps by changing MIR1 to MIR2 and vice-versa as the certificate on MIR2 also may have expired.

Comments:
Your Name  
Email    
(Emails will not be displayed on the site or used for promotional purposes)
Comment  


Type characters in the image
 
 (case sensitive)

 
 
 







Home | Peformance Articles | Audit Articles | Business Intelligence Articles | Clustering Articles | Developer Articles | Reporting Services Articles | DBA Articles | ASP.NET / ADO.NET Articles | DBA FAQ's | Developer Peformance FAQ's | DBA Peformance FAQ's | Developer FAQ's | Clustering FAQ's | Error Messages | Audit Tool Reviews | Backup Tool Reviews | Coding Tool Reviews | Compare Tool Reviews | Documentation Tool Reviews | Design Tool Reviews | Monitoring Tool Reviews | Log Tool Reviews | Reporting Tool Reviews | Clustering Tool Reviews | Security Tool Reviews | Change Management Tool Reviews | Remote Access Tool Reviews | Book Reviews | Security Tool Reviews | QDPMA Performance Tuning | ADO.NET / ASP.NET | Administration | Analysis/OLAP Services | Application Development | Configuration | Components | ETL | Hardware | High Availability | Hints | Index | Misc | Operating Systems | Performance Tuning | Replication | T-SQL | Views