SQL Server alwayson - part 1

[@Niravgandhi]

I had been struggling with this concept, Now thanks to your explanation, I made a video about it in Azure. Glad I subscribed to you.

[@ajiteshmalhotra]

I partially agree with you , mirroring is perfect for DR but mirroring need more bandwidth.so that is the reason not in all projects using mirroring for DR prospective.

[@hteka]

This is just wow. Very simple to understand. Thanks for the video.

[@nagesh46s]

Very nicely explained. Keep up your good work.

[@priyankavadlamudi8226]

Dear ramu superb explication thanks a lot

[@sridhar369]

Really good explanation in simple terms

[@eliasberhe975]

You the best, you help me a lot, thank you so much sir.

[@David_Plane_Spotting]

This was awesome...well explained and very easy to understand

[@thesonglover03]

Hi, Thanks for the great tutorial. I have one doubt, in the always on setup you have configured VSQL and node1 in sql server failover clustering and kept node3 as standalone..any specific reason for that?

[@priyankavadlamudi8226]

your videos all ways rock-out for every one

[@lamusic8791]

awesome information - thank you

[@sagaya23]

Thank you so much for your wonderful explanation

[@PraveenKumar-co3id]

sir , lazy writer is very confusing topic to me , when it will invokes , what its does exactly , , difference between checkpoint and lazwriter , how it releases space by deleting the dirty pages , please do a video for it with examples

[@tayyabshahzad5721]

Thank yo sir for your tutorials They are great help for Oracle DBA like me.

[@Deekudla]

Awesome explanation. Thanks a lot! I would like to know how SQL agent jobs will behave in always-on setup? Can you please explain or make video? It is real time requirement and will help the community. I have manually disabled few jobs in primary node, now do I have to manually disable jobs in node 2? how it will synch? Thanks in advance.

[@mohammadhoque51]

easy, detailed and easy to understand. thank you

[@casualinfoguy]

Excellent explanation.

[@inbedf]

SQL clustering / failover. I have query: 1) I need 4 SQL Server can access sing Data store and databases in replication mode. 4 SQL I can cluster togather (2 per site cross other 2 at other site under singe vcenter) but logically we define seperate site. I dont assigned luns but I have big 5TB Lun active/active mirroring and I am giving all VM 500GB each as D: drive partition volume from that 5TB Lun. All SQL VM have 500GB from same 5TB. so how I ensure that independent 500GB volumes each can be a part of SQL cluster and access same database if any of that server fails or crashed? any idea. If I can creat SQL_Lun1 2TB and that SQL_Lun1 give virtual RDM's volume to all SQL that will good idea but for that I have to make space and create lun, because I am asking question, I dont have more space to create luns, if I create luns I have to destroy lun and recreate space. But if any idea or technique to do volume partition to partition clustering than that helps. Any idea.

[@lidiagaravaglia4277]

Wonderfully explained, thanks a lot for sharing!

[@daniel98890]

Great work Sir...

[@35123]

Thank you, I was looking for a high level explanation of the options in SQL Server for DR and HA, I am Oracle DBA, but I have been asked to look after a few SQL Server databases and offer some recommendations for HA and DR, excellent begiging. We already migrated the databaes to SQL Server 2012, I think AlwaysOn will offer what we are looking for.

[@mohamedyusuffs4388]

Is it possible to keep sql express instance as witness server

[@gajendra-419]

yes

[@harshalphutankar606]

How to setup Active-Active-Active topology in sql server setup between 3 Datacenter? Please help me on this

[@aminex]

Great stuff -- keep making these awesome videos

[@naz4663]

Ramu Garu You are Awesome

[@asimkumarrout5966]

You are the best for us! a Life saver

[@mjkreddy]

Ramu , is that true during mirroring and in SYNC mode records first commit in secondary and then primary ??? and then sends back the reply back???

[@Cyan3boN]

+Jay Munnangi True, I looked it up in MSDN After synchronization finishes, every transaction committed on the principal database is also committed on the mirror server, guaranteeing protection of the data. This is achieved by waiting to commit a transaction on the principal database, until the principal server receives a message from the mirror server stating that it has hardened the transaction's log to disk

[@sas7883]

Thank you...useful video

[@yclem2610]

Thanks So much, Very Very helpful, Thanks for your time, appreciated so much

[@dmitrysemyrjazhko1938]

Thanks! Its very useful for me.

[@rorymcmanus3017]

Well explained! Though funny how he pronounces the word 'Down' Scottish

[@saketerrawada0815]

Excellent

[@dudley20330]

superb video!

[@sivasankar2745]

plz provide replication...it's really very helpful........

[@prasannamohanty1738]

So useful video :-)

[@hotdog75rus]

ох уж этот индусский английский язык. Даже у меня кровь из ушей :)

[@HomosErectus87]

Око Сибири зато четко понятно, что говорит

[@swethasql3500]

Thank you so much.

[@srikanthreddy3251]

its not about always ..started with alwayson heading and explaining Replication mirroring and logshipping...bala bla ///

[@mdhosen1520]

it is helpfull

[@mamillamadhu1608]

Thank you ... 😊

[@whymizan]

awesome

[@chandrab6115]

Thanks for your videos,it really helps me.. Please make a video on SQ Azure as well.. Thanks in advance..

[@Niravgandhi]

please watch : kzbin.info/www/bejne/q6emmIp_o62hqq8

[@AKHILESHKUMAR-sz7il]

GOOD ONE

[@tayof8593]

Thanks a lot :)

[@webstartechnology1995]

dear sir please share your contact to us, I want to join in training

[@kryptorNITE]

your explanation on SQL Replication was very weak.

[@wannavijay1]

VERY LAZY VIDEA...20MINUTES OF SLOWNESS....DIZZY

[@13yasar]

Thanks alot..

[@hatemmegaly9613]

Thanks a lot