Friday, March 1, 2013

[SQL 2012] SQL SERVER 2012 MAINTANANCE TASK- BEST PRACTICE

[SQL 2012] SQL SERVER 2012 MAINTANANCE TASK- BEST PRACTICE

SQL SERVER 2012 MAINTANANCE TASK- BEST PRACTICE

Posted: 28 Feb 2013 07:48 PM PST

Hi All,Can u anyone suggest me for best practice maintenance task in sql server 2012.I am planning to do the following in my Always on server- Production database.1. Full Backup -- Every day2. Diff Backup -- Every 4 Hourly3. Log Backup-- Every One hour.4.Check database integrity -- Every day5. Reorganize and update statistics -- Weekly basis6. Rebuild index -- Every two Weeks7. sp_delete_backuphistory & sp_purge_jobhistory & Output File Cleanup every Week.Thanks for you help in advance.

Mirroring failed due to invalid connection string

Posted: 28 Feb 2013 05:07 PM PST

Hello, I'm receiving the following error:ALTER DATABASE command failed due to an invalid server connection string.when I issue the command:ALTER DATABASE DBName SET PARTNER = 'TCP://DCDRSQLv01.datacoremarketing.com\SQLMICH01:5022';GOSituation - I'm attempting to mirror from a default instance to a named instance. Each instance is running SQL 2012 SP1. Each server is in a different domain and I have configured logins and certificates to make it work properly. I've seen several posts indicating try the following:- check that both servers can be pinged, name resolves and telnet succeeds to the configured port 5022.- confirm that mirroring is started and logins are granted permission.- restore database and transaction log with NORECOVERY option.- Confirm the database and instance are correct.- Attempt connection without the instance name.- Start the Browser service on all nodes.None of these appear to be providing a different result except for the later which complains "network address cannot be reached" (note telnet to 5022 does work).Any assistance is most appreciated. I'm out of ideas.
Posted by at
Labels:

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Search This Blog