CONFIGURED. >> HELLO, EVERYONE. 
GOOD MORNING. THANK YOU SO MUCH 
FOR COMING HERE, 9:00 A. M. ON TIME 
SO WE START. THIS SESSION IS ABOUT 
THE SQL MANAGE INSTANCE DATABASE 
AND THE DISASTER RECOVERY BEST PRACTICES 
ARCHITECTURE. WE ARE GOING TO COVER 
TODAY THE TEN BASIC STEPS, FROM 
STEP NUMBER 1, TO DESIGNING YOUR 
FAILOVER. THE DEMONSTRATION I'LL 
DO TODAY WILL BE ABOUT -- WILL BRING 
TOGETHER THE FAILOVER GROUP. YOU 
ARE GOING TO DESIGN AND DEPLOY THIS 
TOGETHER. MY NAME IS HUGO. I'M A 
PRINCIPLE CLOUD SOLUTION ARCHITECT 
HERE AT MICROSOFT. THANK YOU SO 
MUCH FOR YOUR TIME, ONCE AGAIN. 
SO YOU START IN HERE. I PROMISE, 
THIS IS THE ONLY MARKETING SLIDE 
IN THIS PRESENTATION. SO MANAGED 
INSTANCE IS UNDERNEATH THE AZURE 
SQL DATABASE FORM AS A SERVICE FAMILY. 
SO THE SESSION TODAY IS GOING TO 
BE ABOUT THE MANAGING INSTANCE ONLY. 
WE ARE GOING TO DESIGN THIS ARCHITECTURE 
BASED ON THE MANAGED INSTANCE ONLY. 
OKAY? GOING FORWARD, AS I SAID, 
WE PUT TOGETHER TEN BASIC STEPS 
OF THESE SQL MANAGED INSTANCE DATABASE 
EMPLOYMENT. WE START IN HERE WITH 
THESE DEFINE YOUR ENTIRE ARCHITECTURE, 
GOING ALL THE WAY TO CREATE THE 
FAILOVER GROUP. WE ARE GOING TO 
DO STEP BY STEP OF EACH ONE OF THOSE 
STEPS. LAST BUT NOT LEAST, AT THE 
END I WILL SHARE WITH YOU THE GITHUB 
WITH EVERY SINGLE CLICK YOU NEED 
TO DO IN ORDER TO MAKE THIS DEPLOYMENT. 
IS THAT OKAY? STARTING WITH THE 
NUMBER 1, DEFINE YOUR ENTIRE ARCHITECTURE. 
BE SURE THAT ALL POINTS RELATED 
TO NAMES, DOMAINS, REGION NETWORKING, 
IP ADDRESS, ARE ALL UNDER YOUR HANDS, 
SOS, YOU START YOUR DEPLOYMENT. 
SOS, YOU HAVE THE DEPLOYMENT. SO 
GOING FORWARD TO STACK NUMBER 2 
TO STACK NUMBER 10, WE ARE GOING 
TO DO THESE TOGETHER. STEP NUMBER 
2, USE THIS SAME RESEARCH GROUP. 
YOU HAVE TO BE SURE THAT YOUR BOTH 
MANAGED INSTANCE NEEDS TO BE UNDER 
THE SAME RESEARCH GROUP. THIS IS 
KEY FOR YOU. OTHERWISE THIS IS NOT 
GOING TO WORK. THIS IS THE FIRST 
STEP OF THIS IMPLEMENTATION. HAVE 
THE SAME RESEARCH GROUP FOR BOTH 
MANAGED INSTANCE. THE THIRD POINT, 
AZURE PAIR REGIONS, DEFINE YOUR 
PAIR REGIONS. BE SURE YOUR PAIR 
REGIONS ARE DEPLOYED IN ORDER TO 
SHACK IT WITH THE PAIR REGIONS. 
IT MEANS AZURE GUARANTY FOR YOU 
THE CONNECTION BETWEEN REGION NUMBER 
1 AND REGION NUMBER 2 HAS THE ALL 
KALABILITY IN TERMS OF NETWORK, 
DISASTER RECOVERY, AND SO ON. THAT'S 
THE REASON YOU HAVE TO CHECK THE 
REFERENCE HERE IN ORDER TO BE SURE 
THAT YOU ARE ABLE TO UNDERSTAND 
WHICH PAIR REGIONS YOU HAVE TO USE. 
FOR THE DEMO PROPOSED, I PUT TOGETHER 
THE NORTH AND WEST EUROPE. IS IT 
WORKING? WE ARE GOING TO DEMONSTRATE 
FOR YOU RIGHT NOW. STEP NUMBER 4. 
THE DOS. THIS IS THE WAY TOO GUARANTY 
DATA. I SO WILL STEP BACK HERE JUST 
A LITTLE BIT. THERE ARE TWO TYPES 
OF DOS INSIDE OF AZURE. BASIC DOS 
AND THE THUNDER DOS. THUNDER DOS 
GIVES YOU ADDITIONAL TELEMETRY USING 
THE AZURE MONITOR IN ORDER TO GUARANTY 
THAT YOU HAVE THIS UNDER -- YOU 
HAVE THE CAPABILITY TO UNDERSTAND 
UNDER ATTACK WHAT IS HAPPENING WITH 
YOUR NETWORK. THAT'S THE REASON 
FOR THE SQL MANAGED INSTANCE IMPLEMENTATION. 
WE STRONGLY RECOMMEND TO USE THE 
THUNDER DOS. NETWORK CONFIGURATION, 
AS YOU CAN SEE, THE DIFFERENCE BETWEEN 
STEP NUMBER 4 AND STEP NUMBER 5 
ARE THE VIRTUAL NETWORK ON BOTH 
REGIONS. NUMBER 6, KECKED THE REGIONS. 
TO CONNECT THE REGIONS, DEPLOY A 
VIRTUAL NETWORK GATEWAY IN REGION 
NUMBER 1 AND ANOTHER VIRTUAL NETWORK 
GATEWAY IN REGION NUMBER 2 AND MAKE 
THE CONNECTIONS BETWEEN THE REGIONS. 
DURING THE DEMONSTRATION, I WILL 
TAKE TIME IN ORDER TO SHOW THE VIRTUAL 
NETWORK GATEWAY AND THE CONNECTION. 
THIS IS REALLY IMPORTANT. THIS IS 
THE WAY TO GUARANTY THE SYNCHRONOUS 
BETWEEN REGION NUMBER 1 AND REGION 
NUMBER TWO. DEDICATED SUBNETS. SO 
THE KEY OF THE SQL MANAGED INSTANCE 
IS TO GUARANTY THAT WE HAVE TWO 
LEVELS OF ISOLATION. THE FIRST LEVEL 
OF ISOLATION IS RELATED TO THE TENANT 
RING. I'M GOING TO SHOW YOU THE 
TENANT RING THERE DURING OUR DEMONSTRATION. 
AND THE NETWORKING LEVEL. THE NETWORKING 
LEVEL, AS YOU CAN SEE, WE DEPLOYED 
HERE A DEDICATED SUBSETS PLUS THE 
NETWORK SECURITY GROUP DEDICATED 
FOR THIS SUBNET WHERE WE ARE GOING 
TO HOST OUR SQL MANAGING INSTANCE. 
HUGO, I HAVE A QUESTION. CAN I DEPLOY 
DEPLOY MY APPLICATION IN THIS SUBNET? 
NO. YOU ARE DENIED TO DO THAT. THIS 
IS FULL ENVIRONMENT FOR YOUR SQL 
MANAGING INSTANCE. THIS IS THE WAY 
AZURE GUARANTY YOUR ENVIRONMENT'S 
SECURITY. IS THAT CLEAR? WE DEPLOYED 
HERE ON THE NORTH EUROPE AND WEST 
EUROPE. NUMBER 8, SO AT THIS STAGE, 
FINALLY, AS YOU DEFINE YOUR BASE 
FOR THIS ARCHITECTURE, THIS IS THE 
TIME TO DEPLOY THE SQL MANAGING 
INSTANCE. THE SQL MANAGING INSTANCE 
IS HERE. YOU CAN SEE HERE THE TENANT 
RING. YOU HAVE THE ABILITY BY DEFAULT 
IN THE SQL MANAGING INSTANCE, BUT 
IF THERE IS NO DISASTER RECOVERY 
YET, THE HIGH AVAILABILITY IS GUARANTIED 
WHEN YOU HAVE THE SQL MANAGING INSTANCE. 
HOWEVER, THE DISASTER RECOVERY, 
NOT. THAT'S THE REASON WE ARE DESIGNING 
THIS ARCHITECTURE. OKAY? HIGH ABILITY 
HERE. THE TENANT RING IS HERE READY 
TO GO. LAST BUT NOT LEAST, THIS 
IS LIKE -- THIS POINT, WE HAVE IT 
HERE. SSMS. SOS YOU ALLOW TO YOUR 
SQL MANAGING INSTANCE. WAIT AND 
TO COMPLETE THE ENTIRE PROCESS, 
WHICH WILL TAKE AROUND TWO HOURS 
AND A HALF, THREE HOURS TO COMPLETE 
THE CONFIGURATION AND EVERYTHING. 
THIS HAPPEN BEHIND THE SCENES. YOU 
DON'T NEED TO DO NOTHING RELATED 
TO THE HIGH VAILABILITY. THIS IS 
AUTOMATICALLY FOR YOU. SOS, YOU 
HAVE THESE FULL, READY TO GO, HAVE 
A GREEN SIGN FROM AZURE, SAY THIS 
RESEARCH IS READY TO DEPLOY. INSTALL 
YOUR VIRTUAL MACHINE HERE. THERE 
IS A WAY TO DO THAT THROUGH THE 
QUICK START INSIDE OF THE SQL MANAGING 
INSTANCE BLADES. SO IT'S READY FOR 
YOU, READY TO CONSUME. NINE, THE 
SECOND MANAGED INSTANCE. THIS IS 
THE TIME TO DEPLOY YOUR SECOND MANAGING 
INSTANCE ON THE SAME WAY YOU DID 
ON THE FIRST TIME. HOWEVER, REAL 
IMPORTANT, REAL IMPORTANT MEANS 
THAT I DID THIS MISTAKE BEFORE. 
SO ALL THE TIME I SAY REALLY IMPORTANT, 
BECAUSE I FAILED BEFORE. SO I'M 
SHARING WITH YOU. REAL IMPORTANT 
HERE. CLICK, USE THIS INSTANCE AS 
A FAILOVER GROUP SECONDARY. I HIGHLIGHT 
THIS GITHUB. I'LL SHOW YOU THERE. 
PLEASE DO IT. THIS IS THE ONLY WAY 
TO GUARANTY WE HAVE THE SAME FULLY 
QUALIFIED DOMAIN NAME LIKE DNS FOR 
THIS ENVIRONMENT. OTHERWISE YOU 
ARE GOING TO MISS COUPLE OF HOURS 
HERE. ALL RIGHT? SO IF YOU NEED 
TO HAVE A TAKEAWAY FROM THIS PRESENTATION, 
HAVE THESE, PLEASE DO IT. I FAIL 
A FEW TIMES. SO NUMBER 10. FAILOVER 
GROUP. THIS IS THE TIME, AS YOU 
CAN SEE, DIFFERENCE BETWEEN 9 AND 
10. THIS IS THE TIME TO HAVE YOUR 
EXTERNAL USER APPROACHING YOUR ENVIRONMENT 
THROUGH THE FAILOVER GROUP. I HAVE 
IT HERE AT THIS LINE, PRIMARY REGION, 
ALL THE TIME. HOWEVER, MYSQL MANAGING 
INSTANCE WRITES TO THE END POINT 
WILL BE ALWAYS THE SAME. IF SOMETHING'S 
HAPPENED WITH NORTH EUROPE , YOUR 
APPLICATION WILL GO THROUGH WEST 
EUROPE. WHAT WE ARE GOING TO DO 
NOW TOGETHER, WE ARE GOING TO CREATE 
THAT ONE FOR YOU. OKAY? SO ALL RIGHT. 
AS I SAID, HERE, AS YOU CAN SEE, 
I HAVE ONE MANAGING INSTANCE CALLED 
IGNITE 2019 SQL MI. THIS IS THE 
REGION WE HAVE FOR YOU, READY FOR, 
THE RESEARCH GROUP. I'M GOING TO 
CLICK THERE. AND WHAT I HAVE -- 
NAME -- IS GOING TO BE ALL GUYS. 
NO RECORDS. TAKE THE RISK HERE. 
WE HAVE TWO MANAGED INSTANCE UNDER 
THE SAME RESEARCH GROUP. THE STEP 
WE WILL REMEMBER, SQL MANAGING INSTANCE 
WEST, SQL MANAGING INSTANCE NORTH. 
I'M GOING TO CLICK HERE, SQL MANAGING 
INSTANCE NORTH. YOU HAVE INSTANCE 
FAILOVER GROUP. CLICK THERE. HERE, 
NORTH EUROPE. I DON'T HAVE THE FAILOVER 
GROUP YET. LET'S DO IT. LY CLICK 
HERE. ADD A GROUP. THE LAST BLADE 
WILL COME AND WILL COME TO MISSING. 
YOUR PRIMARY MANAGING INSTANCE IS 
SQL MI NORTH EUROPE. IT'S READY 
TO GO. AND THE FAILOVER GROUP NAME. 
LET'S PUT HERE. FAILOVER -- SORRY 
. FAILOVER IGNITE. IGNITE, ACCEPT 
THIS FULLY QUALIFIED DOMAIN NAME. 
IT WILL BE READY TO GO. IT WILL 
BE MUNICH. SECONDARY MANAGING INSTANCE, 
BECAUSE THE PREVIOUS STEP, I CRIBBINGED 
THAT BOTTOM THAT I TOLD YOU, I HAVE 
NOW THE OPTIONS TO SELECT MY SECONDARY 
MANAGING INSTANCE. I'M DOING THAT. 
READ AND WRITE FAILOVER POLICY. 
I'M GOING TO DO MANUAL. I DON'T 
WANT TO FLIP OVER, BECAUSE THIS 
IS NOT MY BUSINESS REQUIREMENT, 
BUT IF YOU ARE BUSINESS OWNER AND 
IT IS NECESSARY TO FAILOVER AUTOMATICALLY 
OR NOT. OKAY? AND THEN, LAST BUT 
NOT LEAST, CREATE. SO I'M STILL 
MEETING THESE REQUESTS. DEPLOYMENT 
IN PROGRESS. AND MEANWHILE, INSTANCE 
YOU SEE HERE, BECAUSE E-MAIL NOT 
GOOD SINGER, I'M GOING TO SHOW SOMETHING 
ELSE HERE THAT I PROMISED TO YOU 
BEFORE. THE NORTH EUROPE, I WILL 
CLICK HERE. HOW MANY DATABASES I 
HAVE THERE? I HAVE TEN MANAGED INSTANCE 
DATABASE DEPLOYED AT NORTH EUROPE. 
OKAY ANY HAVE TEN THERE. LET'S CHECK 
WEST EUROPE, HOW MANY DATABASES 
I HAVE THERE. I HAVE ZERO. I HAVE 
ZERO DATABASE DEPLOYED WEST EUROPE 
REGION. IS THAT OKAY? LET'S SEE 
WHAT'S GOING TO HAPPEN AFTER CREATE 
THE FAILOVER. THAT FINE? LET'S SEE 
IF IT'S GOING TO WORK OR NOT. WE 
WILL. ANOTHER POINT I WOULD LIKE 
TO SHOW, GOING TO THE RESEARCH GROUP, 
AS YOU CAN SEE, I HAVE ONE RESEARCH 
GROUP CALLED IGNITE 2019 SQL MI 
AND ANOTHER CALLED NETWOKRING. IT'S 
TOTALLY FINE TO KEEP YOUR NETWOKRING 
RESEARCH GROUP UP AND RUNNING THERE 
IN SEPARATE ENVIRONMENT. THE ONLY 
REQUIREMENT IS TO HAVE THE SQL MI 
ON THE SAME RESEARCH GROUP, NOT 
THE NETWOKRING. OKAY ANY WILL CLICK 
HERE THE NETWORK. ALT RE: SEARCH 
IS FOR THE NETWORKING. AS YOU CAN 
SEE, I HAVE THE VIRTUAL NETWORK 
GATEWAY IN NORTH EUROPE AND WEST 
EUROPE. REMEMBER? I HAVE VIRTUAL 
NETWORK GATEWAY HERE AND HERE. I 
DO HAVE, AS WELL, THE CONNECTION 
-- NORTH EUROPE. I CAN SEPARATE 
IT HERE BY NAME . BY NAME. YOU ARE 
ABLE TO SEE I HAVE IT HERE , WEST 
EUROPE AND NORTH EUROPE. OKAY? THOSE 
ARE CONNECTIONS. SO BACK IN THERE 
TO OUR DEPLOYMENT, SQL MI 2019. 
WHAT IS HAPPENING NOW? HOW BEAUTIFUL 
IS THAT?
WE ARE SEEING THE CONNECTION 
BETWEEN NORTH EUROPE AND WEST EUROPE 
HAPPENING. SO AT THAT TIME, I'M 
CREATING THE FAILOVER READ AND WRITE 
AND LISTEN AND END POINTS. LET'S 
SEE THAT. OH! NOW INTACT TO YOUR 
DEVELOPER -- INSTANT TO YOUR DEVELOPER 
USE THE SQL MI. I WOULD LIKE TO DO SOMETHING
HERE. 
INSTANT TO YOUR DEVELOPER, USE THE 
SQL MI ON THE PRIMARY REGION, THEN 
WE USE THIS SQL MI, LISTEN AND READ 
END POINTS. I'M GOING TO SHOW YOU 
HERE. THIS IS GOING TO BE YOUR READ 
AND WRITE, LISTEN ENDPOINT FAILOVER 
IGNITE WE JUST CREATED. EVEN TO 
USE THE FIRST ONE. YOU'RE A DEVELOPER. 
ALWAYS USE THE SAME ONE. LET'S BACK 
THERE , TO THIS SCENARIO. IT WILL 
TAKE MORE -- FEW SECONDS. AGAIN, 
INSTANT FAILOVER GROUP. DONE. I 
HAVE CREATED THE FAILOVER GROUP 
BETWEEN THE BOTH REGIONS. READY 
TO GO. NOW IT'S TIME FOR DEVELOPER 
-- YOUR DEVELOPER OF YOUR ORGANIZATION, 
CHANGE THE APPLICATION INSTANT TO 
POINT TO THE FIRST REGION, POINT 
TO THE FAILOVER GROUP. THE REST, 
AZURE WILL TAKE DARE OF YOU -- FOR 
YOU. FEW THINGS I WOULD LIKE TO 
HIGHLIGHT HERE. FIRST ONE. HERE 
YOU ARE ABLE TO FIND A TUTORIAL 
OF EVERYTHING WE TALKED HERE. IT 
IS A KIND OF -- I WILL SAY SUMMARY 
OF WHAT WE DID. AT THIS POINT, WE 
HAVE THE FULL SCRIPT FOR ONE CLICK 
DEPLOY EVERYTHING WE NEED. HOWEVER, 
THEY STARTED THE DOS AS NOT PART 
OF THIS SCRIPT. JUST A WARNING HERE. 
THE THIRD ONE, I PUT TOGETHER A 
GITHUB WITH EVERY SINGLE CLICK OF 
EVERYTHING WE DID. IF YOU GO THERE, 
IT'S UNDER MY GITHUB, AND WE HAVE 
HERE THE STEP-BY-STEP IMPLEMENTATION 
FOR EVERY SINGLE STEP. ALL THOSE 
TEN STEPS, YOU CAN COME HERE AND 
DOWNLOAD THE VISUAL DIAGRAM FOR 
YOU, ADAPT TO YOUR NETWORKING QUARTERBACK 
HAVE THIS READY TO GO. AS I SAID, 
EVERY SINGLE STEP OF THIS IMPLEMENTATION. 
LAST BUT NOT LEAST -- JUST A SECOND. 
SS CREATED THE SECOND MANAGING INSTANCE 
ON THE SECONDARY REGION. I WOULD 
LIKE TO CLICK THERE. THAT ONE. THIS 
CLICK THAT IS SO IMPORTANT. USE 
THIS INSTANCE AS A FAILOVER GROUP 
SECONDARY. AS I SAID, THIS IS THE 
TAKEAWAY OF THIS SESSION. BACK IN 
HERE TO OUR DEMONSTRATION, I HAVE 
TO PROVE TO YOU THAT IT'S WORKING. 
IT'S NOT ABOUT THE DESIGN ON THE 
GRAPH. SO I'M GOING TO NOW -- GOING 
TO MORE WEST EUROPE REGION , AND 
WE HAVE THE ENTIRE TEN DATABASES 
READY TO GO. COULD BE 20, COULD 
BE 80. WHATEVER YOU HAVE THERE. 
WE DID THIS TOGETHER , GUYS, IN 
LESS THAN TEN MINUTES. THIS IS WHAT 
WE ARE TALKING ABOUT. IT'S NOT COMPLEX. 
JUST FOLLOW THE GUIDES. FOLLOW THE 
STEP-BY-STEPS. THAT'S THE REASON 
WE ARE SHARING WITH YOU THE BEST 
PRACTICES FOR THAT. NOW, AND SOMEHOW, 
YOU GETTING CRAZY AND YOU WANTED 
TO DO THE FAILOVER, THE OTHER TWO 
TESTS USING YOUR POC OR SO ON, OR 
YOU RECEIVE A NOTIFICATIONS THAT 
SOMETHING IS GOING TO HAPPEN IN 
NORTH EUROPE AND WOULD LIKE TO
COMMIT TO 
WEST EUROPE. SO WHY NOW TO DO THIS IN LIFE? 
WHAT ARE WE GOING TO DO NOW.
AS YOU CAN 
SEE THE BLUE HERE MEANS PRIMARY 
MANAGING INSTANCE. THE GREEN MEANS 
SECONDARY MANAGING INSTANCE. LET'S 
SWEEP THAT ONE. I WILL CLICK HERE. 
FAILOVER.
ARE YOU SURE YOU WANT 
TO FAILOVER? I'M NOT SURE BUT LET'S 
DO IT. YES. DOING THE FAILOVER. 
AT THIS TIME, WE ARE SWEEPING THE ENVIRONMENT IN 
ORDER TO ALLOW THE FAILOVER . GUYS, 
REALLY SORRY ABOUT THAT. I'M GOING 
TO JUST GRAB MY PEN. I FORGOT, BECAUSE 
I WOULD LIKE TO HIGHLIGHT ONE POINT 
FOR YOU. I'M SORRY ABOUT THAT. OKAY. 
NOW I HAVE. REMEMBER, WHAT WE HAVE 
BEFORE, MY DEVELOPER COME HERE, 
EXTERNAL USER, AND GOING TOWARDS 
THE FIRST REGION. WHAT WE ARE DOING 
NOW WHEN SOS, WE PUSH THIS FAILOVER 
GROUP. I'M HERE. I'M BASICALLY GOING 
TO THE SECONDARY ONE. LET'S SEE 
THAT. REFRESH. IT'S WORKING. THE 
GREEN ONE NOW IS MY SECONDARY REGION 
-- NORTH EUROPE IS MY SECONDARY 
REGION AND NORTH EUROPE IS MY FIRST 
REGION. ADDITIONAL RESEARCH, FIND 
THIS SESSION AFTER FOR THE EIGHT 
HOURS AT THIS LINK, AND PLEASE, 
IT'S REALLY IMPORTANT FOR US. EVALUATE 
THIS SESSION. THANK YOU SO MUCH 
FOR COMING. IT WAS AMAZING TO HAVE 
