Hello Community
If you install SQL Server 2012 and setup the SQL Server in
standalone mode, later on can you convert that setup into a
SQL Server Cluster Failover mode or do you have to install SQL Server
2012 all over again and set it up in Failover Cluster mode?
Thank you
Shabeaut
Good morning experts,
In our environment, we have an AlwaysOn Availability Group which provides us with a Primary replica and a secondary replica in a co-location for Disaster Recovery purposes. We have been more concerned with the disaster recovery concept all along and do not use the secondary replica for anything other than a fail-over replica. We would like to configure this now to utilize the read-only aspects on the secondary replica to a greater degree. The problem is, our co-location connection is a bit expensive and we cannot send all read-only traffic through that connection on a regular basis.
To counter this, we have decided to set up a third replica in our primary facility that can be used as a Read-Only replica. There is another issue though. The AG contains 13 databases. They total over 15 Terabytes in size. We only need 3-4 of them in the third replica which totals only about 750GB in size (some of the remaining databases simply contain BLOBs which we do not need to read from in this scenario).
It looks to me like it's not possible to have some databases in an AG on three replicas and others in the same AG on two replicas. Is this true or is it possible to do this? Thanks is advance.
My DBs are big (7.5 TB), they are encrypted using TDE. I need to rotate the keys once every 2 years. I have a DR site which is getting synchronize with the primary site using a 25 MBits line. The synchronization is made using SQL 2012 AlwaysOn.
As the key rotation generates lots of transform on the lines, I will not be able to do it.
How should I rotate the keys while keeping the synchronization active?
Hello All,
We have a 3 nodes AlwaysOn environment(Windows 2012 R2 + SQL Server 2014 + SQL Server 2012, all latest rollup installed).
Sometimes the CPU stuck on 100%, all clients complaining the system is freezing, we have to shutdown some instances or drop some cpu on those instances.
I am wondering if there is a way to put the recovery operation in a specific resource pool and limit the cpu on that pool (I checked the internal pool which is not changeable)? or there is other ways to work around?
Thanks,
Albert
I have some maintenance which generate a lot of IO (i.e. compress big tables, apply partition on a big table, reindex on very big tables etc.),
My DBs are synchronize to the DR site over a network line with low bandwidth.
I have to keep both sites synchronized all the time.
How can I do such maintenance if while doing the above activities it generates a lot of IO which can not be handled by the network?
I have implemented Log Shipping in test Environment of SQL Server in two Different Systems and Everything is Set up Successfully. for first time the database is restored with the log and the next time the database went in to Restoring mode,but i have selected the Stand By Mode in my Log Shipping Settings. I dont now how it happened.
in Forums i have found that dropping the Secondary Database and restarting the Log Shipping Process resolves the Issue. Did the same even though the same error. When i try to recover it.with the query
Restore Database AyubKhanTesting with Recovery
it created another error.
Msg 926, Level 14, State 1, Line 1
Database 'AyubKhanTesting' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
Please help on this. Thanks in Advance.
RehaanKhan. M
Hi All,
What is the basic difference between Always on Fail-over cluster and Always on availability group?
Is Always on Fail-over cluster also a new feature in SQL 2012? or it is just the Fail-over Cluster Instance which has been introduced a decade go?
aa
Hi
I am trying to create a 2 Node cluster on a Windows 2012 with SQL Server 2012 Standard edition. I created the SQL Server ( Database Engine ) Failover instance on the 2 Node Cluster successfully. However I am unable to Create a DTC Service that will fail over with the Cluster Instance.
I have done the following steps :
1. Create a Failover Cluster Service ( SQL Server (PRD1 ) )
2. On the Failover Cluster Manager I added a Role ( Distributed Transaction Service ) (DTC1)
3. Created the Dependencies for the Failover.
When I try to move the PRD1 service to the second node the Service Fails as the DTC1 role does not move to the Second Node and the DTC resource fails to come up on the second node.
What am I doing wrong am I missing any steps. Please if you can provide me with the step by step instruction it would be helpful as I need to set it up asasp.
Thanks & Regards
i use availability groups synchronous mode , i want to shrink log file but it not reduce
i do this step
1.i access primary node
2.i backup transaction log
3.i shrink log file it finish but file not reduce
4.i try dbcc loginfo it show 4 record as status is 2
SQL Server 2014
please help me.
Here is my dilemma:
We do have a 3 node MSCS (Microsoft Cluster Services) and we can failover the entire SQL instance from one node to another.
If I want to move to Availability Groups with WSFC SQL 2012 and Windows 2012, which provides only database failover, here are the questions:
1.- Does FCI will replace my 3 node MSCS? Can I implement this?, if not what is my alternative.
2.- Once I have my SQL 2012 3 nodes clustered running, how do I implement WSFC to have 3 replicas which will include our DR replica? Can I do this?
It is very confusing for the people that worked on MSCS in 2005 and 2008, and then go to WSFC which is a different clustering failover of databases ONLY?.
Any link that will help clarify?.
Thank you for your help
Oscar Campanini
Hi,
In my environment we have configured SQL server clustering. Currently we are getting the following error and the service is not starting up.
ERROR: TDSSNIClient initialization failed with error 0x2741, status code 0x1.
While rebooting the secondary side of the failover cluster, the primary availability group hung with the database "resolving".
I found these messages in the SQL server log on the Primary AG. Any idea what error 41005 is?
Source spid9s
Message
Failed to update Replica status within the local Windows Server Failover Clustering (WSFC) due to exception 41005.
Source spid52
Message
The state of the local availability replica in availability group 'MSDGRLE_AG' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information,
see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
we have two node cluster active passive with shared storage , I have setup AlwaysOn as DR on standalone instance
daily morning on failover cluster events, i am getting following critical events
On windows log i couldn't see much information, please help me
Hello Everyone,
Suddnly stop merge replication. transaction cannot replicated from publiser to sunscriber.
I tried to set heartbeat_interval= 5 but still not working..
The replication agent has not logged a progress message in 5 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Distributor are still active.
What is the problem with merge replication and why this erroe comes..
any solution of this error or reconfigure merge replication?
please give me a solution
Hello,
We have an Active/Passive SQL Server setup (DB1 & DB2 Servers) connected to a cluster for SQL & SSAS. I have a web server not on the same domain that I am trying to authenticate with SSAS. This works OK if I set the website to impersonate myUser and I add local account myUser as an Admin on SSAS for the active server (DB1). But when this fails over to DB2 then it fails to authenticate. SSAS won't allow us to add myUser as an admin for local accounts on both DB1 & DB2 as it errors adding the second one. Could anyone advise how such a scenario should be approached?
We have tried creating a domain user too which DB1 & DB2 can of course both share but I don't think the web server can impersonate this with being not part of the domain.
Thanks.
Hello all...
can anyone tell me how I delete database file from C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data\[database name] . this path .
I attached database from sql server . its can deleted by UI. but not programmatically.
I use
RemoveDirectory(file path);
this function ... but this is not working .
what should i do .
Hello:
I Have SQL Server 2012 Ent. Edition & WindowsOS 2012 STD Edition.
I have configured Always ON & i am getting following error. i haven't configured listner & that can be done later on.
I check the firewall & any other port issue which can be stopping me to join my secondary replica to always ON but no luck.
Also i installed latest Service Packs (SP1 - CTP) for SQL Server 2012, but no luck.
Any help is greatly appreciated.
Error:-
message A connection timeout has occurred while attempting to establish a connection to availability replica 'XYZ' with id [0B1ECED7-31BB-4834-AEDE-E15378DC722A]. Either a networking or firewall issue exists, or the endpoint address provided for the replica is not the database mirroring endpoint of the host server instance.
Hi Folks,
i've just been handed a 2 node sql 2008 r2 cluster running 4 instances. When I observed the ports they were listenng on all were listening on port 1433. In addition, in order to connect to them I simply use inst1, or inst2, inst3, or inst4 in SSMS.
I'm used to the old convention of connecting to a named cluster instance prefixed with the virtual server name followed by the instance name. i.e. sqlvirt00, sqlvirt01\instname01, sqlvirt02\inst02, etc. all with different static port numbers for firewall requirements. I also understood that it wasn't advisable to use 1433 for a named instance.
So my 1st question is, can you use the same port for all 4 instances - without conflict? Is it the combination of virtual IP and port# that make the connection unique, or is it the physical IP and port # that make the connection unique?
Second question is, do we no longer need to prefix instance names with vrtual server names, or is there perhaps some DNS manipulation here?
Thanks for your help here.
Scott H
Suppose there is a scenario.
CREATE DATABASE [DBMaint2008];
GO
USE [DBMaint2008];
GO
CREATE TABLE [TestTable] ([C1] INT IDENTITY, [C2] CHAR (100));
GO
-- Take a full backup
BACKUP DATABASE [DBMaint2008] TO DISK = N'D:\SQLskills\DemoBackups\DBMaint_Full.bck' WITH INIT;
GO
-- Insert some rows
INSERT INTO [TestTable] VALUES ('Transaction 1');
INSERT INTO [TestTable] VALUES ('Transaction 2');
GO
-- Take a log backup
BACKUP LOG [DBMaint2008] TO DISK = N'D:\SQLskills\DemoBackups\DBMaint_Log1.bck' WITH INIT;
GO
-- Support we insert 10000 records here
INSERT INTO [TestTable] VALUES ('Transaction 3');
INSERT INTO [TestTable] VALUES ('Transaction 4');
...........
GO
Now here we make the database offline.
We damaged the transaction log file, suppose which also would caused failed to backup the tail of the transaction log, and caused the database in the "pending recovery " when we try to make the database online.
For the such situation we should use the restore from the backup or repair the database with "REPAIR_ALLOW_DATA_LOSS"?
If we choose the restore from the backup ,the last 10000 records would be lost, if we choose "REPAIR_ALLOW_DATA_LOSS" we could save some records, but the records is inconsistent.
So which one should I choose?
Please click the Mark as Answer button if a post solves your problem!