Hi All
We have movement of SQL Server 2000 at physical level. We have disable jobs and stop Agent and SQL Server services.
After moved the server we have started the server and then start SQL Server 2000 services.
All of databases in SUSPECT mode. Files are in correct folders as were before shutdown the server
What shall I do e.g. why databases come up in SUSPECT mode? what to check and how to get database live?
Pls help it is critical...
Thanks in Advance
Here is my situation.
I have setup an alwaysOn availability group which is working fine.
In this AlwaysOn availability group I have converted the Adventureworks database to a contained database. I also added a Contained User.
Connecting to the secondary "Contained" database was no problem.
But here is my problem, when expanding the tables I received the following errormessage:"Cannot resolve collation conflict between "Latin1_General_CI_AS" and "Latin1_General_100_CI_AS_KS_WS_SC" in add operator occurring in SELECT statement
column 3."
Doing this action on the primary is no problem. Executing a select statement against the secondary is also no problem and returns a result.
After some trial and error, I’ve seem to fixed the issue by doing a failover to all my secondary databases.
After, expanding the tables to the primary & secondary worked.
Does anybody have an idea why this happened, and am I the only one experiencing this issue?
Thanks, Bram
We're having an issue with an AG where the the log backup does not appear to truncate the log. symptoms
All backups are being run on the primary. Any ideas?
thanks
Hi
I know it might not make too much sense, and isnt really the intended use (considering the wording on books online) - but does anyone know of a way to be able to have two logshipping secondary databases configured on the same instance of sql server (for the same primary database, that is)?
I have tried it, but when i run sp_add_log_shipping_secondary_primary, i get an error saying that i already have an entry for the primary server/database.
Msg 32024, Level 16, State 1, Procedure sp_add_log_shipping_secondary_primary, Line 95Hello!
I am using SQL 2014 and tying to take Copy-Only full backup every day night and transaction log backup few times during the day time. I could not take the transaction log backup without first taking the full database backup (Non Copy-Only). When I try to take the transaction log backup after taking a Copy-Only full backup, got an error as I need to have the full Backup taken before taking a transaction log backup.
Planning to do the following. Please let me know if this is best approach or any other best way to do this.
1. Take a regular Full backup of the database (Non Copy-Only), first time only.
2. Take Copy-Only backup every day night (keep doing this every day night).
3. Take Transaction log backups (during the day) in between Copy-Only backups.
Repeat Step 2 and 3 for ever. When we need to restore, restore the latest copy-only full backup and restore the transcation logs taken after the copy-only full backup.
Please let me know if this is the right way to do this. I need the copy-only option as I am planning to do this in AlwaysOn AG Secondary Replica.
Thank you,
Louis
Is it possible to move to Alwayson Availability groups from? existing sql server FCI ?
If yes, how to move and what are the pre-requisites?
Hi,
We have configured new SQL Server 2008. Which contains multiple instances.
As part of disaster recovery test my colleague restored master databases on all the instances (about 15 instances).
I am suspecting that he missed restoration of mastes db's on some instances.
Now how can i validate that whether he restored master db's on all the servers are not?
As per test document the procedure is
First restore all userdatabases then restore master databases.
This is only DR testing environment.
In AWS I am told that sql server will go offline during maintenance windows.
Will Azure db's go offline for maintenance windows?
Hi,
I have been experiencing performance degradation on some production servers that previously were part of a SQL 2012 High availability Group.
I recently used a small window of opportunity to test the HADRON groups on some of my SQL Servers. Unusually because of the licencing and hardware high spec, identically setup servers required I had to take some of our servers out of the web production pool during a quiet period and use these for testing.
When the testing concluded, I removed all the HA SQL groups disabled, then removed the windows cluster and removed the cluster Feature from both of the servers and rebooted, but I see the following phantom queries.
()select table_id, item_guid, oplsn_fseqno, oplsn_bOffset, oplsn_slotid from[<dbname>].[sys].[filetable_updates_2105058535]with(readpast)orderby table_idA reboot resolved the issue initially and although unhappy without knowing the root cause I decided not to spend any further time investigating as believed it was resolved. But I noticed a major hit on performance on those specific server again after 2-3 weeks and the queries have returned, if this happens during peak period I will be short of capacity and unable to reboot.
How can I completely remove trace of this as these are obviously protected system tables?.... there are still the odd days when I wished I was still allowed to meddle in those system tables :)
Dear all,
I am having 3 server with same configuration one is production and other two is DR and Near DR
Suddenly something happens and DR and Near DR databases goes to restoring mode from standby/readonlymode.
Even I verified the .trn files it show's valid, even I checked the Disk there is no issues in the disk and I too checked the file share properties it is also fine.
Please find the below error log and below link it is similar SCENARIO
Processed 0 pages for database 'Logship_xxxxx', file 'xxxxx' on file 1. Processed 1 pages for database 'Logship_xxxxx', file 'xxxxx_log' on file 1. Msg 9004, Level 16, State 6, Line 1 An error occurred while processing the log for database 'Logship_xxxxx'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log. Msg 3013, Level 16, State 1, Line 1 RESTORE LOG is terminating abnormally. Msg 3414, Level 21, State 1, Line 1 An error occurred during recovery, preventing the database 'Logship_xxxxx' (27:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
http://social.technet.microsoft.com/Forums/en-US/9c39fc61-0a59-402b-91fb-17ac1f03da7b/sql-2012-log-shipping-to-report-server?forum=sqldisasterrecovery
Thank you..
Hi Folks,
Cluster validation step has failed due to the IP configuration validation ,
how can identity and How to resolve duplicate IP's
Can you suggest your views on this.
PFA
HI
After activating AlwaysOn High Availibility Groups in SQL Server 2012 R2 and adding databases at the availibilitygroup, SQL Server started genereting lots of messages in the SQL Server Logs.
Some example Messages are: "DbId (1466) log capture is rescheduled with partner generation: 45, log consumer id: 9828",
"HadrLogCapture::BuildMsgBodyForSend - DbId [2535]->[1807D374-DA55-4CAC-A831-AA3C3A8B8EC4] Send From saved msg - LogBlockId (0x000221e800000010)"
Is there is a possibility to stop generating these messages?Hi, I have 2 SQL 2012 servers in my DMZ and I have assigned SQL to run on a static TCP Port. I would like to setup Always On availability groups on the servers but I cannot get the failover to work with the static TCP port. It works fine with dynamic ports.
When the failover is initiated it attempts to connect to the secondary replica with out using the static port, can someone tell me how to setup the availability group using static tcp ports.
Thanks,
I have a scenario with the three nodes with server 2012 standard, each running an instance of SQL Server 2012 enterprise, participate in asingle Windows Server Fail-over Cluster (WSFC) that spans two data centers.
If the nodes in the primary data center are unavailable due to data center outage. Then how I can able to access node in the WSFC (Windows Server Fail-over Cluster) in the secondary disaster recovery data center automatically with some script.
Can you please guide me for script writing for automatic fail-over in case of primary data-center outage?
Currently I'm working on a large deployment of a SharePoint 2013 environment (stretched farm over 2 DC's). We are using a SQL 2012 alwayson multisubnet cluster (each DC has 1 SQL node). During the installation of SharePoint we encountered several connection time-out errors from the SQL environment. (Exception calling "Open" with "0" argument(s): "Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond;)
Steps we follow for SharePoint installation are:
- Restart SharePoint services with updated alias.
Event errors and SQL log errors that I found:
Date,Source,Severity,Message,Category,Event,User,Computer
09/18/2014 07:34:59,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPAG_CU8000001105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:34:59,MSSQL$SPAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:34:52,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPWMAG_CU8000002105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:34:52,MSSQL$SPWMAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:34:47,Service Control Manager,Information,The WMI Performance Adapter service entered the running state.,(0),7036,,CU8000000015
09/18/2014 07:32:41,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPSDAG_CU8000003105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:32:41,MSSQL$SPSDAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:31:09,PowerShell,Information,Engine state is changed from Available to Stopped. <nl/><nl/>Details: <nl/> NewEngineState=Stopped<nl/> PreviousEngineState=Available<nl/><nl/> SequenceNumber=61464<nl/><nl/> HostName=OpsMgr
PowerShell Host<nl/> HostVersion=7.0.5000.0<nl/> HostId=32012185-8d9a-41c2-be56-91929c02f1e8<nl/> EngineVersion=4.0<nl/> RunspaceId=af176e01-185d-4574-ab9b-0fd745178d29<nl/> PipelineId=<nl/> CommandName=<nl/> CommandType=<nl/> ScriptName=<nl/> CommandPath=<nl/> CommandLine=,(4),403,,CU8000000015
We are not allow to update/write in the DNS for the multisubnet cluster IP registration, so I think that explains the "failed registration" error. But can this explains our time-out errors during the SharePoint installation? For the installation we are connection directly to 1 SQL node and not to the SQL cluster.
Any help is appreciated!
Ronald Bruinsma - Independent SharePoint Consultant - iDocs.info - The Netherlands -- Please don't forget to propose this post as an answer or mark it as helpful if it did help you. Thanks.
Hello Frenz,
I have a SQL Always on environment with 02 Nodes, the Failover is not happening automatically when one server is down with the following error,
"network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)"
Kindly someone help.
Note: The Node which is available is in Synchornizing state, but when both the Nodes are available its working fine.
How do I achieve disaster recovery in the following scenario
WINDOWS 2012
MSSQL 2012 ENT
SiteA win2012wsfc_PROD with 2 nodes with DB1,DB2, here am able to achieve HA
SiteB win2012wsfc_DR with 2 nodes, I need to replicate DB1,DB2 on DR site
Besides Log shipping & SAN based replication, can we achieve this in any other way.
1. In the Availability Group can we configure, SiteB win2012wsfc_DR [ can a node be add in multi cluster]
2. Any other options
Thanks
Cleto
Currently I'm working on a large deployment of a SharePoint 2013 environment (stretched farm over 2 DC's). We are using a SQL 2012 alwayson multisubnet cluster (each DC has 1 SQL node). During the installation of SharePoint we encountered several connection time-out errors from the SQL environment. (Exception calling "Open" with "0" argument(s): "Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond;)
Steps we follow for SharePoint installation are:
- Restart SharePoint services with updated alias.
Event errors and SQL log errors that I found:
Date,Source,Severity,Message,Category,Event,User,Computer
09/18/2014 07:34:59,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPAG_CU8000001105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:34:59,MSSQL$SPAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:34:52,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPWMAG_CU8000002105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:34:52,MSSQL$SPWMAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:34:47,Service Control Manager,Information,The WMI Performance Adapter service entered the running state.,(0),7036,,CU8000000015
09/18/2014 07:32:41,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPSDAG_CU8000003105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:32:41,MSSQL$SPSDAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:31:09,PowerShell,Information,Engine state is changed from Available to Stopped. <nl/><nl/>Details: <nl/> NewEngineState=Stopped<nl/> PreviousEngineState=Available<nl/><nl/> SequenceNumber=61464<nl/><nl/> HostName=OpsMgr
PowerShell Host<nl/> HostVersion=7.0.5000.0<nl/> HostId=32012185-8d9a-41c2-be56-91929c02f1e8<nl/> EngineVersion=4.0<nl/> RunspaceId=af176e01-185d-4574-ab9b-0fd745178d29<nl/> PipelineId=<nl/> CommandName=<nl/> CommandType=<nl/> ScriptName=<nl/> CommandPath=<nl/> CommandLine=,(4),403,,CU8000000015
We are not allow to update/write in the DNS for the multisubnet cluster IP registration, so I think that explains the "failed registration" error. But can this explains our time-out errors during the SharePoint installation? For the installation we are connection directly to 1 SQL node and not to the SQL cluster.
Any help is appreciated!
Ronald Bruinsma - Independent SharePoint Consultant - iDocs.info - The Netherlands -- Please don't forget to propose this post as an answer or mark it as helpful if it did help you. Thanks.
