Migrating Your Existing SQL Server Estate to Amazon's RDS

You won't need many items to take this course. Even better, all the items you do need are free.

Script libraries allow us easy access to important files we need to troubleshoot critical issues.

They are also good for performance tuning. All the tier one SQL Server DBAs I know use a script library. I've included some tips and tricks on creating one.

A look at what we've covered in this section.

How SQL Server and RDS behave. Amazon's OLTP service was designed specifically for relational databases like SQL Server.

This is how we benchmark the computing power we need. Recall the big three? (IO, Memory and CPU) These instances classes cover two of them. (memory and CPU)

This is easily one of the most confusing areas in moving anything to the cloud. Ryan discusses an approach to benchmarking your costs.

When we provision an instance we create an instance. Another term is to spin up an instance. In this lecture we create our first instance.

Let's wrap up what we've covered in this course.

In this lecture we highlight a few important items we need to take into account before we dive head first into moving our estate to the cloud.

These are easily committed to memory once you've migrated your first instance to the RDS.

I'm using the term native here to mean that we need no third party tools to move schema and cloud to RDS. This approach will serve you well for small databases.

We have the option to script data and schema together or separately. Some DBAs like to see the schema alone prior to scripting or moving the data.

In this lecture we are moving a larger more complex database to RDS. It's only complex compared to our initial example but it does add keys and other objects that need to be scripted.

In this lecture we script our the schema separately and then use a component of SSIS to push our data to RDS.

I'm with you. This course is focused on AWS why would we use a tool for Azure? Well, it might have been written for Azure but it works flawlessly with RDS.

Let's take a look at how this tool brute forces our databases to RDS. This might not always be the best choice but it's a great first swipe at testing what we can move to RDS without major complications.

Most database will have objects that aren't cloud compatible and we will have to sift through them before the application goes live in RDS.

A quick review of what we covered in the section.

Logins and permission are *NOT* moved automatically. You must move them manually. Thankful, this script provided by Microsoft will easily move the logins.

The performance monitor in the cloud. Another component of RDS you'll be using often. It's really well integreated into the instance.

You run out of cpu or memory and you have to scale up. It's very easy to do but it does incurr an outage.

SQL Server Agent is included with every version except for express. Let's walk through a simple example and add a stats rebuild job.

Let's wrap up what we've covered.

Let's wrap up this course. Thanks for taking it.