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.
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.
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?
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.
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.
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
+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
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.
Wonderfully explained, thanks a lot for sharing!
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.
This was awesome...well explained and very easy to understand
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.
Great stuff -- keep making these awesome videos
your videos all ways rock-out for every one
Thank yo sir for your tutorials They are great help for Oracle DBA like me.
You are the best for us! a Life saver
Great work Sir...
This is just wow. Very simple to understand. Thanks for the video.
Thanks So much, Very Very helpful, Thanks for your time, appreciated so much
Very nicely explained. Keep up your good work.
Really good explanation in simple terms
Thanks! Its very useful for me.
Dear ramu superb explication thanks a lot
superb video!
easy, detailed and easy to understand. thank you
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?
You the best, you help me a lot, thank you so much sir.
Thank you so much for your wonderful explanation
Ramu Garu You are Awesome
Excellent explanation.
Thanks a lot :)
Thank you so much.
Thank you...useful video
awesome information - thank you
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.
Thank you ... 😊
Excellent
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.
So useful video :-)
awesome
GOOD ONE
Thanks a lot
Thanks alot..
Well explained! Though funny how he pronounces the word 'Down' Scottish
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
it is helpfull
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???
+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
Thanks for your videos,it really helps me..
Please make a video on SQ Azure as well..
Thanks in advance..
please watch : czcams.com/video/uvCgWInHntM/video.html
How to setup Active-Active-Active topology in sql server setup between 3 Datacenter? Please help me on this
plz provide replication...it's really very helpful........
Is it possible to keep sql express instance as witness server
yes
ох уж этот индусский английский язык. Даже у меня кровь из ушей :)
Око Сибири зато четко понятно, что говорит
its not about always ..started with alwayson heading and explaining Replication mirroring and logshipping...bala bla ///
dear sir please share your contact to us, I want to join in training
your explanation on SQL Replication was very weak.
VERY LAZY VIDEA...20MINUTES OF SLOWNESS....DIZZY