SQL Server alwayson - part 2

In this video, you will learn SQL Server 2012 AlwaysON availability groups.

[@RadnusTechnology]

Excellent training. Very nicely taught and explained. Some folks may find your style of presentation orthodox, but I personally loved it and it gave me a feel of being in a class room in a live training. Thank you.

[@ig2947]

All your videos are Superb - cleared so many doubts. Thanks a lot..!

[@aallee125125]

Thank you very much for the video, great stuff. But I would like to point out something here, My understanding of Asynchronous or synchronous session is that in a synchronous Mirroring session the Primary server WAITS for the secondary(Mirror) server to commit the changes to its disk, then the Mirror sends a response to Principal server and then the Principal server commits changes to its disk. In an Asynchronous session , The Primary Server commits the transaction without any waits and then sends a request to Mirror server, at this point when the Primary has committed it and the change has not been committed to Mirror if the server goes down you will end up with an out of sync copy of Principal server hence the name Asynchronous. Also "Asynchronous Mirroring" option is only available in SQL Server Enterprise Edition. $$$ :)

[@opeoluwaagboola8819]

I agree with you completely. It's important you pointed it out. Thanks

[@Here2Findout]

3 years late, but yes this is 100% correct

[@nsantiago3607]

Everything you want to know about SQL Server Always ON. Thank you for creating this video.

[@ajaysql2599]

Hi thanks a lot for detailed explanation on Always on .Just wanted to Address something here at the last few seconds there was some confusion in application intent being read only and while running select @@servername why the name of the primary server is being displayed .According to me the issue is not with the settings but with the query the query is being run on the master database and system database cannot be in an AG if it was a query related to a table which is part of a database in AG then it may have directed it to VSQL instead of Node 3.

[@paulibison2598]

Great video - thanks for making this available. I saw that n the demo, the read-only application intent connection went to the primary replica. I have also seen that when connecting in SQLCMD (-k switch) when the database being connected to is not in the availability group (master in your case). The initial connection needs to reference a database in that availability group then it works :).

[@akrish5311]

Excellent. Very well explained. Thanks a lot.

[@kchennaiah5283]

Excellent Explanation

[@vikasvyas6427]

MetaManager...you are really awesome....thank you so much for this video and also for clustering session.... Your videos are really helpful for me .

[@daniel98890]

Great effort and super explanation.....A Big Thank You

[@chrgbhtt]

i liked the way you covered all aspects !! Very helpful share. - thanks

[@tajudeen2]

true

[@upwalebhaiya2477]

Thanks Ramu sir... Very well explained....

[@sanjeevpabbi5190]

Very well explained for beginners, Thx

[@braylenmateo9171]

i guess it's kinda randomly asking but does anybody know of a good site to stream newly released series online?

[@kabirjayceon5256]

@Braylen Mateo i use flixzone. You can find it by googling =)

[@jaimeboston2384]

@Kabir Jayceon definitely, I have been using flixzone for months myself :D

[@braylenmateo9171]

@Kabir Jayceon thanks, I went there and it seems like a nice service :D Appreciate it !!

[@kabirjayceon5256]

@Braylen Mateo Happy to help xD

[@reazulislam8446]

good teacher , no doubt , like the style very simple

[@charanpudota]

Nice explanation...... THANK YOU

[@syam035]

Nice presentation, really helpfull

[@techcybertraining]

Really good thorough explanation, thank you

[@varunyada5251]

Detailed Video, Thanks!! Q: In case of multiple availability groups, What happens to the app connection string if only one availability group fails and others stay on node 1?

[@BryanSwanSQLServerBI]

Because SQL Server 2012 can host multiple availability groups on a single server, you can configure AlwaysOn to fail over to SQL Server instances on different servers. This reduces the need to have idle high performance standby servers to handle the full load of the primary server, which is one of the many benefits of using availability groups.

[@metamanager]

You need to carefully plan how to failover all AGs to other node if there is any problem with any of the AG.

[@ChuTiya_TechHQ]

I have a question that since it is at database level, what about both servers' master database copies. isn't it has to be same? if yes or no ? please explain. It is wonderful explaining

[@sgopikrish]

its very nice.. thanks for sharing...

[@Abdulhafeezkalsekar]

Very Nicely described thanks. May i know your name plz

[@BryanSwanSQLServerBI]

Great Video Series!

[@dcalixte2]

Is it okay to implement "a synchronous" alwaysON with the passive node located in a different data center? what will be the impact on performance? I know that the synchronous setup affect the day to day operation performance. If I decide to go async for that matter is it safe to say that maybe 30 mins (max) of data is lost?

[@jimmyvivimegan]

Great tutorial! Would I be able to fail over to my secondary in DR site if my main data center which has the Windows Cluster configured goes down? Thank You.

[@genius747]

Hello, i have Windows Server 2016 with SQL 2016 Enterprise. We have a failover cluster configuration. We have 2 nodes , SQL01 and 02. We have created an availability group which has 3 db's inside it. It is with Synchronous and readable on Secondary for both SQL servers. Automatic failover has been configured. currently jobs have been created on the SQL01 only. No jobs have been created on SQL02. Now when the failover happens: 1. Will it start writing data on the secondary SQL02 ? If yes , will that data be synchronized to SQL01 ? 2. What happens to the jobs ? if the jobs are processed will the data be replicated back to SQL02 ? Please help as i am trying to find a solution for this.

[@fahdbahoo1]

windows cluster do not show after restart of windows ? why ? Windows server 2019 Data center edition

[@13yasar]

Well Explained ... Thank you so much,

[@ChuTiya_TechHQ]

what about if we have added more users ? how on secondary replica, new users will have authentication ? is it a manual job we need to perform ?

[@kanyohaye]

thanks very much that is amazing lecture!!!

[@asifjanjua4238]

Great Tutorial...Super

[@rajuavula6477]

excellent sir....

[@diushyant]

How many times you will keep repeating same lines

[@piyusworld2550]

Hi Sir y you don’t post anything on this channel..

[@Deekudla]

Do we need to create windows cluster before installing SQL SERVER on both the nodes?

[@metamanager]

Yes Deepak, you need to put all replicas(servers) in windows cluster first and then configure always on. But in 2017, you can configure alwayson without cluster. You can select NONE as cluster type while configuring always on but automatic failover will not be possible without cluster.

[@sivakumarcherukuri9556]

can you make video for AG 2017, new features

[@ChuTiya_TechHQ]

how application will have credential on secondary replica ? how we can configure applications for AlwaysOn technology what if master database is corrupted, can we failover on secondary replica while we restore master db on primary

[@afzzaps]

chan Liu we can't failover if the master database is corrupted because system databases can't be part of an availability group.

[@metamanager]

First, you need to manually create logins on primary and secondary replicas. logins are in master database which is not part of availability group. So, logins wont be propagated to secondary. If master database is corrupted, sql may go down and in that case there is possibility of automatic failover (if you have configured one). I have not tried master database corruption scenario. Good question, try it out and let me know.

[@grusso1970]

thanks very much very useful!

[@dswijesundera5054]

Great stuff

[@PushpaLatha-tc3bq]

Can you please tell me how have you created cluster instance

[@metamanager]

I have created SQL Server 2012 cluster videos, you may have to check

[@PushpaLatha-tc3bq]

Could you share the link here

[@narendramallu1931]

Great JOB...

[@fredericovargas5963]

Great video!

[@jimsprstel1]

Good job

[@abdulfareed9476]

EXCELLENT

[@shashankmore2128]

gr8 tutorial !!! 👍

[@36revanth]

excellent

[@sehbdusa]

please upload recent tutorials in respective chapters Thanks a lot

[@Banghhhhhhh]

explain by hear !! thanks :)

[@Avatar-cv9nv]

This is Called -- Deep Dive Always On ..

[@rajadevarapu2205]

good one but there is so much redundant information, repeating same statements.. had slept off twice :D

[@metamanager]

I will do better job next time.

[@jasjeetsingh9652]

explanation is good, but try to make all things fast. it is very slow.

[@metamanager]

I create videos for beginners. So, at times you have to be patient Jasjeet.

[@Krishna-pk9up]

Sir speed is very less...

[@mb9234]

KUDOS Man ---/\---

[@hamzaliaqat5390]

Good Lectures but you just stretched thing :(

[@metamanager]

I agree with you. I stretched sometimes, probably should have edited the video better.

[@anubhavasatiGurgaon]

Some disappointment with your presentation. important things u skip like Backup preference,listeners etc. Many imp points u r skipping.Needs improvement.

[@upwalebhaiya2477]

Hi

[@mallavarapuajaykumar7582]

great job but poor presentation...totally disappointed