I'm trying to restore a database using SSMS GUI. In "Select backup devices" window if I click the Add button there the window and the whole process hangs like it will never work.
I tried to clear backup history, but that didn't solve it.
I tried with a couple of other databases, but same thing.
It was working fine!
Any advice please!
Is there any way to track/monitor alwayson group failover from system log (windows,application etc) using event id..
Ideally i want to get notified if failover happened by tracking event id related to alwayson group failover.
When I was researching, i can only see cluster failover related logs in windows level. Alwayson group failover related logs are withing the sql instance itself (either by sql agent alert or extended events). But I need to check if i can just track event id from windows log when alwayson group failover occurs if that is available.
Could anyone assist on this please. Thanks in advance
vijayasarathi
May I know why Always-on Xevent has no data when using what live data ?
what it is used for ?
What's the other possible value of Always-on Dashboard : cluster type ??? the other options are for Linux ?
What's the difference for the following
primary_role_allow_connections_desc : ALL vs Read-write
secondary_role_allow_connections: Read-only and all ?
why last_sent_lsn can be lower the last_received lsn ?
and the last harden time is much later than the last received time ??
and the last redone lsn is less than last_received lsn
and what about the end_of_log_lsn and last_commit_lsn ? how is it related to last_harden_lsn??
what's the meaning of low_water_mark_for_ghosts??
Hi there,
Do you have any other idea for this process?
Hi
SQL Server 2016 SP2 EE
I am trying analysis the log block Latency report through SSMS 18. But Still no luck . Please note extended event "always on data movement trace" already enabled. and secondly the AG job AlwaysOn_Latency_Data_Collection
already run. Any one explain why this error?
in the xevent about always on there is an event :Availability_replica_manager_state_change
what's Availability replica Manager ?? And how the event is triggered?
Dear all,
I have a big issue with a new availability group installation/configuration. It does an error and do not create the group...
It seems that the group goes online and then is killed by the failover cluster... But I don't see why. I do have searched the web about my issue but I have tried everything proposed :
1. Grand privileges to NT AUTHORITY\SYSTEM (Connect SQL to, View server state to, Alter any availability group to
2. Local admin for the agent /engine service account on Windows and on the SQL database
3. Delete my cluster and recreated it
4. Tried creating the group without the listener
5. Have exactly the same Hardware configuration (HDD / RAM / CPU)
Here the log from the SQL Server (from SSMS)
08/13/2019 09:07:01,spid55,Unknown,Always On: WSFC AG integrity check failed for AG 'AG-SQLIPSN-DEV' with error 41044<c/> severity 16<c/> state 1. 08/13/2019 09:07:01,spid55,Unknown,Error: 19435<c/> Severity: 16<c/> State: 1. 08/13/2019 09:07:01,spid55,Unknown,The state of the local availability replica in availability group 'AG-SQLIPSN-DEV' has changed from 'RESOLVING_NORMAL' to 'NOT_AVAILABLE'. The state changed because either the associated availability group has been deleted<c/> or the local availability replica has been removed from another SQL Server instance. For more information<c/> see the SQL Server error log<c/> Windows Server Failover Clustering (WSFC) management console<c/> or WSFC log. 08/13/2019 09:06:01,spid55,Unknown,The state of the local availability replica in availability group 'AG-SQLIPSN-DEV' has changed from 'NOT_AVAILABLE' to 'RESOLVING_NORMAL'. The state changed because the local availability replica is joining the availability group. For more information<c/> see the SQL Server error log<c/> Windows Server Failover Clustering (WSFC) management console<c/> or WSFC log. 08/13/2019 09:04:39,spid15s,Unknown,Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required. 08/13/2019 09:04:39,spid15s,Unknown,Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
Here the logs from the Cluster :
EVENT ID : 1254 Error - Clustered role 'AG-SQLIPSN-DEV' has exceeded its failover threshold. It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state. No additional attempts will be made to bring the role online or fail it over to another node in the cluster. Please check the events associated with the failure. After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it online again after the restart delay period. EVENT ID : 1205 Error - The Cluster service failed to bring clustered role 'AG-SQLIPSN-DEV' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role. EVENT ID : 1069 Error - Cluster resource 'AG-SQLIPSN-DEV' of type 'SQL Server Availability Group' in clustered role 'AG-SQLIPSN-DEV' failed. Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.
I am totally lost on why it doesn't work. My previous AlwaysOn configuration went fine without any issue and we did the same thing for this one...
The only thing I could think of is to begin the all process again (deleting everything -> DNS records, AD records, Quorum share , Cluster) and start again... But I am not sure it would work...
Hope anyone can help,
Best Regards,
Jon
Hi Team,
Hope someone can help.
we have got a SQL Server 2017 Availability group on a multi subnet AG.
we are trying to configure linked server connection to the availability group from another stand alone SQL server (SQL server 2014).
The Linked server is giving a timeout and i think its trying to resolve the listener name to the IP which is not active. can someone help in this?
is there a way we can configure multisubnetfailover=true for the linked server?
skv
Hi
I have a VLDB database (3.2 TBs) that is an Availability group that is going to run out of ids soon on a couple of tables. I need to check but I am guessing at least one of these tables is over TB. I need to convert the int to bigint and the column is not a "clustered" index but it is the primary key. I still need to check to see if there are foreign keys on the id as well but assume there are.
The SQL Server is getting upgraded to 2016 in the next week or two. I've read most recommendations advocate for copying over the data into a new table with bigint as the primary key, etc. and re-applying the indexes and foreign key constraints.
Some questions:
Is there any scenario that would allow you to keep the database in the AG group?
Could you use the "Alter Table" online that is available starting in SQL Server 2016 to change the primary NON-Clustered key from int to bigint?
If yes, would you need to drop the DB out of the availability group? What are the ramifications to the db logging and how much would it cause the database mdf/ndfs and ldfs to grow? Can you keep the application online and users connected if you can use this method? Any other considerations?
Thanks,
Sue
Sue
so in my log directory, I have a directory called Polybase... and there's THOUSANDS of dmp memory log files... each about 500mb. they get created by the hundreds every day. I don't have polybase configured... I don't even have any databases other than the regular adventureworks demo db.... any idea what these are?
What's the better way to compress blob data in a database backup?
The scholarly article below demonstrates easy ways to create data references to the files in filetable.
https://www.databasejournal.com/features/mssql/filestream-and-filetable-in-sql-server-2012.html
Question - how can this data be compressed?
R, J
Hi We have SQL Server 2016 EE Always on enterprise edition two nodes Async mode. Both servers are VM Servers .
Q1.If One of SQL servers are required to restore from VM backup (SRO) level, do we have to rebuild the all configuration again or Always on will be working again normal after VM level restore is done.
highly appreciate your expert advise .
Many thanks
I would like to know why clusterless AG in sql 2017 not a DR solution? Is there a reason that i am missing?
I am ok with async & no auto failover - It's like one type of mirroring option of old.
Pretty much if it came after db mirroring it would be a hit. mirroring + read_only secondaries is what I am seeing it as with no requirement of clustering. So if mirroring was a viable DR solution for so long than why isn't clusterless AG a DR solution.
I want to know as I would like to set it up & use for DR+read_only reporting copies.
I know all about AG etc, but it needs clustering and that is not a option on one of my apps so lets not get into AG & its advantages (ha, dr, grp failovers, listener, read-only routing etc etc.. i know) but my question pertains to one of my apps where i have a mixture of a clustered env & non windows clustering enabled server which needs to be used for reporting and i have tested that I am able to use clusterless ag there where i can add both env as replicas.
https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/configure-read-scale-availability-groups?view=sql-server-2017
we are good with:
Please don't reply about adv of AG, keep your answers to why read-scale AG is not a DR option, thanks.
D
I have two node always on, and the secondary replica is a sync-commit replica.
I am checking for the column of last_harden_lsn and last_received_lsn , I am wonder why last_harden_lsn is greater than last_received_lsn, why they are not the same ?
select * from sys.dm_hadr_database_replica_states