Trying to add a second replica to my SQL 2012 AG. for some reason i cant click the next button. Never seen this.
Any help?;)
Trying to add a second replica to my SQL 2012 AG. for some reason i cant click the next button. Never seen this.
Any help?;)
Hi All,
How many maximum database's can we have in AlwaysON Availability Group?
Thank you.
Sam
In my environment I have 2 azure VMs with Windows server 2012R2 which are standard alone servers. I need to setup windows active/ active cluster setup. if any having the idea, please share the details, it would great if anyone shared the complete documentation.
Thanks,
Raj K.
Hi
Is there a hard-limit with related to number of databases in logshipping in one server? I.e. say in one server, I have about 800 small databases? can all 800 databases be part of the logshipping ? My guess is no hard-limit as it is a matter of creating one job to perform trans. log backup, one job to copy and one job to restore log on secondary servers.
I'm wondering if anyone has used logshipping with large number databases (800-900 in a server).
Johnc
Hi,
In SQL Server, whether the full backup of a database includes the backup of the log? Thanks
Hi,
I make two full backups on Oct 1 and Oct 10. I want to restore the server to a state in Oct 5. So I just do as follows:
But the restore fails and SQL Server said the transaction log does not contain the point. The point is too early. Why? Also my .LDF file is about 13G, but the transaction log backup is only 200MB. Why?
Thanks
Hi All,
I my environment i observed one of the Production server startup parameter -t1800.
What is the SQL Trace Flag 1800 and the purpose of this trace flag?
Can any one please explain about this?
Thanks,
Raj K.
SQL Server 2014 enterprise on Server 2012 VM. Had a drive failure on which our SQL DB's resided. Unable to recover any of those DB's. I have reestablished a drive for the SQL DB's. We have an existing failover cluster on which SQL 2 member server are joined but when i open SQL Management Studio, of course it can not connect to the DB's. So how do i tell the existing SQL server install the location of the new SQL DB locations? If i rerun setup, select installation then install a single server to a cluster, SQL wants to install again. If i click add a node to an existing cluster, the install finds the old cluster and not the new one:
and i cant type in anywhere the new cluster. How do i add the nodes to the existing cluster?
Hi All,
I believe to configure maximum number of replicas it is required to have 5 nodes (1 Primary & 4 Secondary replicas). But how many databases can be included in one availability group, it think it is 32767. When I am referring to below URL it is mentioned something like "An availability group supports a set of read-write primary databases and one to eight sets of corresponding secondary databases. " What does this 'sets' means, is that maximum limit for only eight databases or maximum groups should be eight? Please advise.
https://msdn.microsoft.com/en-us/hh510230.aspx
Regards,
Kalyan
Grateful to your time and support. Regards, Shiva
Hi All,
Currently in my environment we are using SQL server 2012.
We setup Alwayson with synchronous commit.
Details of existing AlwaysOn: one primary and two secondary.
Primary: On-Premise server.
Secondary1: On-Premise server.
Secondary2: Azure VM.
Requirement: We need toadd Secondary3 New Azure VM on same AG with asynchronous mode or synchronous mode.
Or
We need to create one more AG on same DB and add the new replica with asynchronous.
Is it possible above 2 option in this scenario?
My cluster environment is Manual failover only not auto failover.
Could you please guide me how can I do this?
Thanks,
Raj K.
Hello,
I am encountering a strange problem in my environment and I'm wondering if anyone might have some ideas to help with troubleshooting. We have a 12 node WSFC on Windows Server 2008 (not R2, I know, its ancient but can't be helped). 6 nodes exist in the primary datacenter and 6 exist in the secondary datacenter. We have combined SQL Server 2012 FCI's with Availability Groups. So when failing over to another node in the same datacenter we would do a traditional FCI failover using FCM tool in windows and when failing between datacenters we would failover the availability group through SSMS.
The problem we have encountered on occasion is that when we failover from one node to another node in the same datacenter, the SQL Server group will failover to the new node and come online right away, however the AG does not always follow it. Sometimes it will refuse to move from the previous node, and sometimes it will move to another node completely. This results in the AG being unavailable and client machines cannot connect to the Listener. The workaround to this issue is to either stop cluster service on the node currently hosting the AG, or in rare cases, reboot the machine. This will force the AG to move to the node where the FCI is currently hosted.
This issue is difficult to reproduce because it is sporadic, and as well it will affect a customer facing database when we do, so we are treating it as a delicate matter. We were unable to reproduce this after opening a case with MS, but the issue has since started happening again. Looking for some working theories, or some further direction to investigate.
Thanks,
Bill
Hi,
I have 2 servers. On one server i install sql server 2014 and its working fine, i am able to get connected with sql with domain account.
from second machine i want to connect my sql server, for that i create udl file when i give sql server address and click refresh getting following error:
connection failed cannot generate SSPI context
Firewall is off, created fire rule too, i am able to get ping first machine by ip and servername but still getting issue. please guide what could be an issue and how to fix it.
thx
iffi
Hai,
we are using SQL2008R2 ,Fetching data to the reports using SQL procedure.Each reports taking too mcuh memmory of our server and after execution memory is not going down. How can I achive this ?Each procedure for fetching data includes many nested loops which is unavoidable..If the records are less then the reports generation is faster
Server hve 24GB RAM and if we take two huge reports then memory will reach the maximum.When I limited SQL max capacity then always for small report also we face memory issue.
Now the max server 2147483647
Shall I add these 4 lines in the procedure, Will it push down the memory after the execution?
DBCC FREEPROCCACHE
DBCC DROPCLEANBUFFERS
DBCC FREESYSTEMCACHE ('ALL')
DBCC FREESESSIONCACHE
and where should I add these lines in the below procedure?
ALTER PROCEDURE..... if @Type='Reportsec' begin Declare @Rno bigint,@CntRcCnt bigint Create Table #Tmpdailyrep1_1(RECNO int identity primary key,fahrid bigint, Datum datetime,Lon float, lat ................. end
Hi
I have configured Alwayson HA setup as following environment and versions, and working fine to client side by connected with AG Listener.
Two Node WSFC setup. Node1 (Primary), Node 2(Secondary Replica). Normal quorum(No shared disk)
Server Platform: HyperV
OS: Windows server 2008 R2 64 bit with SP1
RDBMS: MS SQLSERVER 2012 64 bit with SP2
Totally confused when I am doing testing Failover method between two nodes. automatic failover not happened.
Simulate tried as below method for worst case failure scenario
Just shutdown Node1 and try to connect at client side by using AG Listener name but not succeeded, also Cluster name and AG Listener name are not pinging, Second node2 cluster service is not started by automatically due to as below errors. So how will connect
client and overcome this issues?
Any modification need to be done on both side WSFC and AlwaysOn SQL? for achieving and automatic failover.
Thanks
I am setting up a new pair of SQL 2014 enterprise servers in HA using Availability Groups. One of the servers is located here in our local datacenter(10.0.1.x) and the other SQL server is in our remote datacenter(172.16.1.x). I was able to setup the Windows
Failover Custer without much issue. I setup the AG but when I try to setup the listener. I get the following error.
I have setup an IP for both networks on the listener. I have confirmed that there is not any DNS records created for AG listener name. But I still get this error. Can some please help me identify what I am missing?
Thanks,
TD
Hi Team,
When I execute the below query in secondary of Log shipping setup, it returns NULL in second and third column; but when checked the job history message the copy and restore steps are running successfully. Because of this issue I think, most of the time the restore job loop through all the files in the secondary backup folder. Any idea why there NULLs? The setup has monitoring server configured by using Primary server name.
select secondary_database,last_copied_file,last_restored_file from msdb..log_shipping_monitor_secondary
Thanx
Ashru
MCTS, http://asharafaliptb.wordpress.com
Greetings. I currently have a 2 node Availability Group that houses some big warehouse type of DB’s. It’s not uncommon to see DB1 populate DB2:
Use db1
Go
Insert into db2.dbo.table_1 values ‘ssfsfsfsf’
This all works as expected. However, we want to split these DB’s away from each other to reduce CPU impact on any one instance. Of course though we don’t want to have to go and change all the connection strings in our SSIS Packages. By default this would now require going to a 4 part naming convention like so:
Insert into newServerName.db2.dbo.table_1 values ‘ssfsfsfsf’
Again though, we are trying to avoid this. That said I was thinking to use synonyms. This works as expected, until a failover occurs, and the synonym is redirected to the local Read Only version of DB2.
So in other words, SQL Server is behaving exactly as it should, but I need a way to work around it.
Example below:
USE [master]
GO
/****** Object: LinkedServer [DB2] Script Date: 10/28/2015 11:43:46 AM ******/
--note this is pointed to the AG Listener name, for failover purposes.
EXECmaster.dbo.sp_addlinkedserver@server =N'DB2', @srvproduct=N'sqlserver', @provider=N'SQLNCLI', @datasrc=N'myAGListenerName', @catalog=N'DB2'
/* For security reasons the linked server remote logins password is changed with ######## */
use DB1
go
CREATESYNONYM table_1
FOR DB2.dbo.table_1
GO
--both of these insert statements work, and go to the expected DB
insertinto DB2.dbo.table_1(c1) values ('foo')
insertinto table_1(c1)values ('foo')
--do failover of the AG
--this still works, as table_1 actually resides on the new Primary of the AG
insertinto table_1(c1)values ('foo')
--this no longer works, as there is a Read Only version of DB2 on the local server
insertinto DB2.dbo.table_1(c1) values ('foo')
Msg 3906,Level 16, State 1, Line 1
Failed toupdatedatabase"DB2" because thedatabaseis read-only.
Again, SQL Server is behaving exactly as it should. However, this synonym is now fairly worthless, as it can't handle failing from one node to the other in the AG
Any ideas?
Thanks in advance! ChrisRDBA
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, I have a problem with my SQL 2005 Transactionlog backup. I get an error on the schedule job:
Message
Executed as user: TNET\sqlservice. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 01:00:00 Progress: 2008-02-15 01:00:02.56 Source: {8277BBE5-6B5E-44D1-9221-17442AB5C857} Executing query "DECLARE @Guid UNIQUEIDENTIFIER EXECUTE msdb..sp".: 100% complete End Progress DTExec: The package execution returned DTSER_FAILURE (1). Started: 01:00:00 Finished: 01:00:03 Elapsed: 2.813 seconds. The package execution failed. The step failed.
but the job goe's trough and the full backup is ok.
The version I have is 3042 and sp2. Doe's anybody regognize this?
HI experts,
1. I am looking data base solution for highly critical application. what type of HA/DR solution will suite for this.(always on, transactional , log shipping or mirroring). make sure all secondary nodes should be identical to production .
2. for any need to upgrade /patching /maintenance work, production should not be able to down. No downtime 100%.
This HA/DR solution should be able to manage online system 24*7*365
please let me know what kind of solution should be appropriate.
regards
Ashwan