I setup my first Sql 2014 cluster. (Windows 2012 R2, Sql 2014). I can successfully use Management Studio by pointing it to the Sql Cluster name but not when I point to the Sql server instance on a individual node in the cluster. I get "server could not be found". On the one hand this makes sense ("hands off the nodes"; stick with the published name) but how then can sql maintenance be done directly on a particular node?
TIA,
edm2
P.S The cluster uses shared storage. (SMB 3.0 file shares)
I have a two node cluster in a testlab. I'm thinking of INSERTing a million rows in a table, and while the process is running, failover to the other node. (Obviously I'm hoping for minimal loss). Can think of a better way to show failover " in action"?
TIA,
edm2
Hello Team
We have to configure AlwaysOn to an already existing Failover Cluster Instance (FCIs) like in the below architecture.
How is it now -
Setup:
FCI-1: SQLFCIPRIMARY\Inst_A
FCI-2: SQLFCIDR\Inst_B
Nodes
PrimaryNode1
PrimaryNode2
DRNode1
DRNode2
Each of the above FCIs are 2 node clusters as shown the above figure. All the 4 nodes are in the same data center.
Since all the instance should be in WSFC for setting up AlwaysOn AG, I tried adding the seconday node to the existing cluster in Primary. But it is throwing an error saying"The computer 'DRNode1' is joined to a cluster." While this is expected since DRnode1 and DRNode2 are already participating in clustering, I would like to know how to get around with this issue. I have researched (actually googled ) quite a bit but do not find an applicable solution for this. One way is to remove the secondary node (DRNode1 or 2) from the cluster but I guess it doesn't make sense in my case since I want to create a AlwaysOn solution between two FCIs.
What I am not able to do -
Ideally I would like all the 4 nodes showing up in Primary Failover Cluster Manager.
Thanks a lot in advance.
Dear support
good day for you,
i using SQL server 2012 and using AlwaysON High Availability (server_SQL1 = Primary & Server_SQL2=Secondary), when i try to shrink the log files he told me you must alter the database to simple recovery mode first but i cant coz using AlwaysON !
thats mean:
any other solution for shrink logs without add/remove DB from AlwaysON
Regards,
I am in the process of setting up a SQL Failover cluster over two availability zones in AWS. My issue I am having is my File share witness is throwing me an error when trying to set this part up.
set-clusterquorum -NodeAndFileShareMajority "\\EPMMNSDC1\Witness"
Gives me this error:
set-clusterquorum : There was an error configuring the file share witness '\\EPMMNSDC1\Witness'.
Unable to save property changes for 'File Share Witness'.
The parameter is incorrect
At line:1 char:1
+ set-clusterquorum -NodeAndFileShareMajority "\\EPMMNSDC1\Witness"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Set-ClusterQuorum], ClusterCmdletException
+ FullyQualifiedErrorId : InvalidParameter,Microsoft.FailoverClusters.PowerShell.SetClusterQuorumCommand
I have both my nodes as read/write on the share. I am able to browse to the share from both nodes.
I try to run it through the GUI and i get this error:
Hi All, I'm in the process of setting up log shipping for several SQL 2008 DB's. Everything works fine using a small test DB, but for the next step, I need to configure Log shipping for a 100+GB DB that will be backed up and shipped across a 35Mbps WAN link. If I select to backup that DB using the Log Shipping Wizard and it takes 8+ hours, do I need to be concerned about any changes that have occurred since the start of the backup or will it automatically know which transaction logs to apply after the backup completes? If you've setup something similar, are there any gotchas or best practices I should be aware of when setting up log shipping for a large DB across a WAN link? *This DB gets moderate use and we don't need an aggressive RPO so I'll probably opt for a 30 minute schedule for Log Shipping jobs.
Thanks!
Hi All:
We have an discussion with VM team and DB team.
Requirement: Configure DR for all the SQL Servers hosted on Virtual Machines.
VM Team: They are asking us to configure Mirroring or Logshipping with out extra license.
DB Team: We are asking them to implement DR by using "VMware vCenter Site Recovery Manager".
We informed that we are not ready to configure either log shipping (or) mirroring for all the databases on the SQL Instance.
Please share your experiences with us who worked on DR planning on VM Hosted SQL Servers., Highly appreciated that who worked onVMware vCenter Site Recovery Manager for there DR plans. Your experiences was help full for us.
Thanks,
Satish Kumar.
Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)
Hi I am trying to follow this terribly written article to setup CRM to be part of a SQL alwayson availability group.
The part that is pissing me off is the create SQL logins. http://technet.microsoft.com/en-us/library/jj822357.aspx#BKMK_always_updateorg
So many errors with this post causing so much frustration. What is the actual correct Syntax for creating the key?
Obviously you have to use a UNC path to the CRM front end server. SQL doesnt like UNC and I think an earlier guy said it doesnt like double quotes. Here is what I have and it does not like it. Its hard to see but right before end I have two single quotes to close it. It's complaining about the \\ in the UNC path.
IF NOT EXISTS (SELECT * FROM sys.asymmetric_keys WHERE name = 'MSCRMSqlClrKey') BEGIN EXECUTE ('CREATE ASYMMETRIC KEY MSCRMSqlClrKey FROM EXECUTABLE FILE ='\\CRM2013\C$\Program Files\Microsoft Dynamics CRM\tools\Microsoft.Crm.SqlClr.Helper.dll'')END
Hello,
I have created an availability group that contains a database. The database is working fine.
I get a request to create a full-text catalog and to add full-text indexes.
Is it possible to create full-text indexes on databases that have a primary replica and a number of secondary replicas?
Best regards,
Erik
We are looking at consolidating our databases onto a Windows / SQL Server cluster. In our lab environment we have full control over the environment AD & DNS Servers. In our test and Production environments, there is a separate team that manages
AD & DNS. For AD, it only takes 7 - 10 days to get users and groups created. For DNS, everything is handled by the DNS team, and nothing is automatically added to DNS; part of the issue is DNSSEC.
If DNS is not available or unable to create/update an A record, will the install of the SQL Server Failover cluster fail? In place of DNS, can you use local hosts files?
Thanks.
DJ
We have 2 AG each with on DB in it. the mode of the synchronization of those AG is Asynchronize.
What will happen in a case where a transaction crosses the boundary of a database.
Example SP on DB A deletes account records from DB B and inserts account records into DB A– in a single transaction.
what happens in a case of disaster to the copies in the DR site, will they be as it was before the begining of the transaction, or it could be that one DB will have half a trasaction commited on it?
I want to implement Always on from 1 primary server to a DR site on maby DBs, the AG will be one for each DB, and the synchronization mode for most of the AG will be synchronized. Failover will be done manually, and will always include all the DBs. we will never have some DBs active in one site, and others in the other site.
If a disaster will happen, in order to return to the primary, we are not expecting to use the auto recover of the mirror, but recreate the DB.
We have some cross-DBs transactions. My question is what will be if a disaster will happen in a middle of a cross DB transaction, will the transaction end or will rollback in both DBs, or could I find the DBs in a partial data lost situation. (meaning in one DB the command which was part of the transaction will end, and in the other will not exists).
I saw this article http://msdn.microsoft.com/en-us/library/ms366279(v=sql.110).aspx which worries me.
I have 2 scenarios:
1. Always on with synchronize mode on 2 seperate AG, both on the same server, replicas are to the same server, no automatic failover, when failover one AG, we fail over the other one as well. Each AG on one DB(i.e. DB A is under AG_A, DB B is under AG_B), I have a cross-database transaction. Can I be sure that the transaction will be on the same state on both replicas in the DR site, if a disaster happens in the middle of the cross DB transaction?
2. As above, but asynchronize mode. Will it keep the same state of the transaction on both replicas? will it help if I will have one AG to cover both DBs (when the mode is asynchronized)?
Hi guys
I need some help from you.
Sql 2008 R2 clusteer with 2 instances (VS are Virtual Names):
VS1/InstanceA
VS2/InstanceB
The cluster works fine without issues.
Problem:
I have configured the SS Integration Services in the cluster belonging to the VS2/Instance group.
I successfully connect to SSIS (from SQL Management Studio) by using the VS2 virtual name, but when I try to open the MSDB folder I get the error: Failed to retrieve... The SQL Server instance specified.... (A log error message).
Could you help me?
Thanks
Hi, We are are working on a High Availability & Disaster Recovery Planning solution for an application database which is on SQL Server 2005. What different options have we got to implement this for SQL Server 2005 and after we have everything setup how do we test the failover is working?
Thanks in advance.........
Ione
Our server ran out of disk space during a stored procedure process. We were able to free up some space, stopped all SQL services, restarted all SQL services and now SQL Management Studio shows the database to be in recovery. Is there a way to monitor this to ensure progress is being made and to estimate when it might complete?
I'd like to set up a system to test all our database backups. My plan is a dedicated server that would cycle through our backups and test them by restoring and running dbcc checkdb etc. It would raise an email alert if there was a problem. The server would not be serving up data to anyone.
We have several spare SQL licenses from our developers' MSDN subscriptions. Would an MSDN license cover this server or does this count as a production server? (I thought of the Express edition but some of our databases are too big.) Please advise. Thanks.
I am using SQL Server 2012 and trying to configure database mirroring on a contained database. I have configured mirroring on other databases in the same environment without issue, but when I try to configure it on the contained database I get the following error.
Alter failed for Database ‘X’. (Microsoft.SqlServer.Smo)
Property DefaultLanguageName is not available for Database ‘[X]’. This property may not exist for this object or may not be retrievable due to insufficient access rights.
I am in the sysadmin role and have verified that 'contained database authentication' is turned on for both the principal and the mirror. What am I missing?
~M