Adding SQL template

SQLServer-Migration/SQLMigration-Migration-Readme.md

@@ -0,0 +1,27 @@
+
+# SQLMigration- Migration Template
+
+#### [1. Assess](v1.0/SQLMigration/Assess)
++ [Specialized assessment Optimization and Licensing Assessment OLA](v1.0/SQLMigration/Assess/Specialized%20assessment%20Optimization%20and%20Licensing%20Assessment%20OLA)
++ [Identify SQL Server database migration strategies](v1.0/SQLMigration/Assess/Identify%20SQL%20Server%20database%20migration%20strategies)
++ [Discover SQL Server Environment](v1.0/SQLMigration/Assess/Discover%20SQL%20Server%20Environment)
+#### [2. Mobilize](v1.0/SQLMigration/Mobilize)
++ [Overall Governance](v1.0/SQLMigration/Mobilize/Overall%20Governance)
++ [Security](v1.0/SQLMigration/Mobilize/Security)
++ [People](v1.0/SQLMigration/Mobilize/People)
++ [Platform planning](v1.0/SQLMigration/Mobilize/Platform%20planning)
++ [Migration Hub Strategy Recommendations](v1.0/SQLMigration/Mobilize/Migration%20Hub%20Strategy%20Recommendations)
++ [Review SQL Server Architecture](v1.0/SQLMigration/Mobilize/Review%20SQL%20Server%20Architecture)
++ [Review and finalize SQL Server database migration method](v1.0/SQLMigration/Mobilize/Review%20and%20finalize%20SQL%20Server%20database%20migration%20method)
+#### [3. Migrate](v1.0/SQLMigration/Migrate)
++ [Review learnings from the Mobilize phase](v1.0/SQLMigration/Migrate/Review%20learnings%20from%20the%20Mobilize%20phase)
++ [Tag workloads based on migration type](v1.0/SQLMigration/Migrate/Tag%20workloads%20based%20on%20migration%20type)
++ [Develop a prioritization order for migration](v1.0/SQLMigration/Migrate/Develop%20a%20prioritization%20order%20for%20migration)
++ [Rehost SQL Server to Amazon EC2](v1.0/SQLMigration/Migrate/Rehost%20SQL%20Server%20to%20Amazon%20EC2)
++ [Replatform SQL Server to Amazon RDS](v1.0/SQLMigration/Migrate/Replatform%20SQL%20Server%20to%20Amazon%20RDS)
++ [Replatform SQL Server to Amazon RDS Custom](v1.0/SQLMigration/Migrate/Replatform%20SQL%20Server%20to%20Amazon%20RDS%20Custom)
++ [Refactor SQL Server to Amazon RDS](v1.0/SQLMigration/Migrate/Refactor%20SQL%20Server%20to%20Amazon%20RDS)
+#### [4. Operate](v1.0/SQLMigration/Operate)
++ [Monitoring the migrated environment](v1.0/SQLMigration/Operate/Monitoring%20the%20migrated%20environment)
++ [Application optimization and Modernization](v1.0/SQLMigration/Operate/Application%20optimization%20and%20Modernization)
++ [Plan Operations](v1.0/SQLMigration/Operate/Plan%20Operations)

SQLServer-Migration/v1.0/SQLMigration/Assess/Discover SQL Server Environment/tasks.md

@@ -0,0 +1,14 @@
+
+# Module: Discover SQL Server Environment
+## Task 1: SQL Server database migration questionnaire
+#### Description
+Use the questionnaire in this section as a starting point to gather information for the assessment and planning phases of your migration project. You can download this questionnaire in [Microsoft Excel format](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-sql-server/samples/sql-server-migration-questionnaire.zip) and use it to record your information.
+#### Tools
+Microsoft Excel
+## Task 2: Discovering and evaluating databases for migration with AWS DMS Fleet Advisor
+#### Description
+You can use DMS Fleet Advisor to collect metadata and performance metrics from multiple database environments. These collected metrics provide insight into your data infrastructure. DMS Fleet Advisor collects metadata and metrics from your on-premises database and analytic servers from one or more central locations without the need to install it on every computer. 
+
+For databases in your inventory that you plan to migrate to the AWS Cloud, DMS Fleet Advisor generates right-sized target recommendations. To generate target recommendations, DMS Fleet Advisor considers the metrics from your data collector and preferred settings. After DMS Fleet Advisor generates recommendations, you can view detailed information for each target database configuration. Your organization's database engineers and administrators can use DMS Fleet Advisor Target Recommendations to plan the migration of their on-premises databases to AWS. Also, you can explore different available migration options and export these recommendations. Finally, you can use the AWS Pricing Calculator to further optimize the cost.
+#### Tools
+DMS Fleet Advisor

SQLServer-Migration/v1.0/SQLMigration/Assess/Identify SQL Server database migration strategies/tasks.md

@@ -0,0 +1,72 @@
+
+# Module: Identify SQL Server database migration strategies
+## Task 1: Homogeneous database migration for SQL Server
+#### Description
+AWS offers you the ability to run SQL Server databases in a cloud environment. For developers and database administrators, running SQL Server database in the AWS Cloud is very similar to running SQL Server database in a data center. You have below options for running SQL Server on AWS. Visit the below links to learn more.
+* **[SQL Server on Amazon RDS](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-sql-server/rds-sql.html)** - Managed service, provides easy provisioning and licensing, cost-effective, easy to set up, manage, and maintain.
+* **[SQL Server on Amazon RDS Custom](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-sql-server/rds-custom-sql.html)** - Managed service, but you retain administrative rights to the database and the underlying operating system.
+* **[SQL Server on Amazon EC2](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-sql-server/ec2-sql.html)** - Self-managed, provides full control and flexibility.
+* **[SQL Server on VMware Cloud on AWS](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-sql-server/vmware-sql.html)** - Set up, scale, and operate your SQL Server workloads on VMware Cloud on AWS 
+## Task 2: Heterogeneous database migration for SQL Server
+#### Description
+Because of the innovations and improvements in open-source databases and cloud computing platforms like AWS, many organizations are moving from proprietary (online transaction processing or OLTP) database engines such as SQL Server to open-source engines. SQL Server databases are mission-critical systems for any organization, but being locked into a particular vendor is a risky and costly situation. Low operating cost and no licensing fees are compelling reasons to consider switching the underlying database technology to open-source or AWS Cloud-native databases.
+
+Other reasons for migrating off SQL Server are vendor lock-in periods, licensing audits, expensive licensing, and cost. For this reason, many organizations choose to migrate their SQL Server databases to either open-source databases (such as PostgreSQL, MySQL, or MariaDB) or AWS Cloud-native databases (such as Amazon Aurora or Amazon DynamoDB) when they migrate to AWS.
+
+You can also migrate your SQL Server data warehouse database to Amazon Redshift, which is a fast, fully managed cloud data warehouse. Amazon Redshift is integrated with your data lake, offers up to three times faster performance than any other data warehouse, and costs up to 75 percent less than any other cloud data warehouse. You can find various tools from AWS which can helps you with heterogeneous migration.
+#### Tools
+Babelfish
+#### Tools
+AWS DMS
+#### Tools
+AWS SCT
+## Task 2: Subtask 1: Explore the AWS Purpose Built databases
+#### Description
+AWS offers 15+ purpose-built engines to support diverse data models, including relational, key-value, document, in-memory, graph, time series, wide column, and ledger databases. In this Migration Journey we will focus on **Relational databases** for heterogeneous target.
+
+**Relational** Traditional applications, ecommerce, OLTP transactions 
+
+ Amazon Aurora - MySQL and PostgreSQL compatible
+ Amazon RDS - SQL Server, MySQL, PostgreSQL and MariaDB
+ Babelfish for Aurora PostgreSQL : Babelfish for Aurora PostgreSQL is a new capability for Amazon Aurora PostgreSQL-Compatible Edition that enables Aurora to understand commands from applications written for Microsoft SQL Server.
+  
+**Key-value ** High-traffic web applications, ecommerce systems, gaming applications, financial trading 
+
+ Amazon DynamoDB
+ Amazon Keyspaces
+
+**Document** Content management, catalogs, user profiles 
+
+ Amazon DocumentDB
+
+**OLAP** Traditional data warehousing, multi-tenant BI applications 
+
+ Amazon Athena
+ Amazon Redshift
+
+**In-memory** Caching, session management, gaming leaderboards, geospatial applications 
+
+ Amazon Elasticache
+ Amazon MemoryDB for Redis
+
+**Search** Consolidated logging, personalized search 
+
+ Amazon OpenSearch
+
+**Graph** Fraud detection, social Networking, user profiles 
+
+ Amazon Neptune
+
+**Ledger** Systems of record, supply chain, registrations, banking transactions 
+
+ Amazon QLDB
+
+**Time series** IoT, DevOps, industrial telemetry 
+
+ Amazon Timestream
+
+
+#### Tools
+AWS Purpose Built Databases
+#### Acceptance Criteria
+Understand the different open source relational database engine.

SQLServer-Migration/v1.0/SQLMigration/Assess/Specialized assessment Optimization and Licensing Assessment OLA/tasks.md

@@ -0,0 +1,56 @@
+
+# Module: Specialized assessment Optimization and Licensing Assessment OLA
+## Task 1: Arrange a session to introduce Optimization and Licensing Assessment
+#### Description
+When planning an executive strategy for cloud adoption and infrastructure modernization, customers can feel lost when looking for a starting point. Which workload should they move to the cloud first? How do they ensure they're choosing the right services? What do they do with their existing Microsoft software licenses? Can they bring them along, or is it smarter to rent them leveraging our pay-as-you go (license included) model and break free from the Microsoft Enterprise Agreement? 
+
+In this session, customers get to know to the OLA process, tools and benefits of running OLA assessment. This will help to identify a migration strategy that meets their TCO and ROI requirements as well as moving faster towards their digital transformation strategy.
+## Task 2: OLA Secure customer agreement
+#### Description
+As part of the OLA process, secure a customer agreement that includes the following: 
+
+1) Migration project scope
+2) Business objective 
+3) Project contacts
+4) Security and privacy
+5) Project-timeline review
+
+
+#### Acceptance Criteria
+• Customer confirms readiness to kick-start the OLA project. 
+## Task 3: OLA Kick off project
+#### Description
+After the customer confirms readiness to kickstart the OLA project, do the following:
+
+1) Kick off the OLA project
+2) Install the data collector tool (Migration Evaluator or RDS Tools, depending of the type of OLA selected) on the desired migrating environment infrastructure.
+3) Use the tool to collect utilization data
+4) Identify application dependencies
+#### Tools
+Migration Evaluator
+#### Tools
+RDS Tools
+#### Acceptance Criteria
+• Provisioned the data collector tool with the desired migrating environment infrastructure
+#### Acceptance Criteria
+• Used the Migration Evaluator collector tool to collect utilization data for the migrating environment
+## Task 4: Request an OLA through Assessment Central
+#### Description
+
+#### Tools
+Assessment Central
+#### Acceptance Criteria
+OLA request created in Assessment Central 
+## Task 5: [For AWS practitioners and Partners] Complete the OLA
+#### Description
+To evaluate the current migrating environment to AWS, you need to collect the inventory and performance data of the environment that needs to be migrated. To collect this data, you will work with an AWS-sponsored team to determine the right choice for your environment. We will collect your environment data with a high level of accuracy, which helps to analyze and suggest the appropriate approach for migration.
+#### Tools
+Assessment Central
+## Task 6: Review OLA results with customer
+#### Description
+After you use the data collector tool (Migration Evaluator or RDS Tools, depending of the type of OLA selected) to collect the data, do the following:
+
+1) Prepare the final output presentation based on the collected data
+2) Move to the next steps to engage with partners and Proserve teams
+#### Acceptance Criteria
+• Generated the OLA report using the collected data

SQLServer-Migration/v1.0/SQLMigration/Migrate/Develop a prioritization order for migration/tasks.md

@@ -0,0 +1,53 @@
+
+# Module: Develop a prioritization order for migration
+## Task 1: Prioritize application migration order
+#### Description
+Application prioritization is the process of determining the order in which applications must be migrated to the cloud. Assess priority based on the complexity of migrating the application to the cloud and the rules that are defined.For more information, see [Large Migration Portfolio playbook prioritization](https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-portfolio-playbook/prioritization.html)
+#### Tools
+Portfolio playbook templates
+#### Tools
+AWS Migration Evaluator
+#### Tools
+AWS Migration Competency Partners
+#### Tools
+AWS Application Discovery Service
+#### Acceptance Criteria
+• A list of application components prioritized based on the business and technical rules.
+## Task 1: Subtask 1: Define the application prioritization process
+#### Description
+There are three process options for prioritizing applications:
+
+1) Manual complexity scoring: Use complexity scoring criteria to assess the difficulty of migrating each application
+2) Application nomination: Application owners nominate applications for migration
+3) Discovery tool: Define criteria within the parameters of the discovery tool, and then the tool analyzes the applications and provides a final complexity score.For more information, see [here](https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-portfolio-playbook/prioritization.html#prioritization-1)
+#### Tools
+AWS Application Discovery Service
+#### Tools
+Portfolio playbook templates
+#### Tools
+AWS Migration Competency Partners
+#### Tools
+AWS Migration Evaluator
+#### Acceptance Criteria
+• Prioritization process based on discovery tools
+## Task 1: Subtask 2: Define the application prioritization rules
+#### Description
+Define application prioritization rules, to determine the migration order of the applications. 
+
+Create rules to assess the priority of each application so you can schedule the application in the appropriate wave. 
+
+Common business and technology rules include the following: 
+1) Specifying the order and schedule for migrating data centers 
+2) Prioritizing business units 
+3) Capturing deadlines for critical business applicationsFor more information, see [here](https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-portfolio-playbook/prioritization.html#prioritization-2)
+#### Tools
+Portfolio playbook templates
+#### Acceptance Criteria
+• Defined prioritization rules
+## Task 1: Subtask 3: Finalize the application prioritization process
+#### Description
+Define how the portfolio workstream uses the rules and processes to prioritize applications. This is the process that the portfolio workstream references in the implementation stage of the migration.
+#### Tools
+Portfolio playbook templates
+#### Acceptance Criteria
+• Finalized process for prioritization