Removed all references to DB analysis (#268)

* Removed 'analyze dbs' step from 'six steps' docs

* Removed DB analysis from main sidebar

* Deleted main db analysis page

* Removed various references to db analysis

Author: SamDesmondKing

_data/sidebars/main_sidebar.yml

@@ -73,9 +73,6 @@ entries:
           - title: Performing Code Analysis
             output: web
             url: analyze-source-code.html
-          - title: Database Analysis
-            output: web
-            url: analyze-database.html
           - title: HTTP Web Log Analysis
             output: web
             url: analyze-logs.html

book/discover.md

@@ -14,7 +14,7 @@ documentclass: report
 This book will cover all the discovery steps you will need to perform for your cloud migration project.
 
 ```{.include shift-heading-level-by=1}
-pages/user guides/six_steps.md
+pages/user guides/five_steps.md
 ```
 
 The remaining will now go through the discvory process step by step. Starting with installing Tidal Tools.
@@ -56,12 +56,6 @@ pages/tidal tools/analyze.md
 pages/user guides/discover_nmap.md
 ```
 
-# Database analysis
-
-```{.include}
-pages/tidal tools/analyze_database.md
-```
-
 # Source code analysis
 
 ```{.include}
@@ -82,8 +76,7 @@ We hope that this book helped you to get yourself familiar with **Layering Disco
 2. Scheduling synchronizations across your hypervisors such as VMWare or Hyper-V
 3. Server usage statistics aggregation
 4. Discovering and fingerprinting your running web applications
-5. Performing databases analysis
-6. Analyzing your source code
+5. Analyzing your source code
 
 That was the beginning of your journey towards the transformative cloud migrations. And now, we hope, you are ready to move forward!
 

pages/tidal tools/analyze_database.md

@@ -30,8 +30,7 @@ If you'd prefer to use a cloud shell, you can watch how to get setup in the [AWS
 
 ### Dependencies
 
-If you plan to use the `tidal analyze code` command to analyze your source code
-or `tidal analyze db` to analyze your databases, you will need to install
+If you plan to use the `tidal analyze code` command to analyze your source code, you will need to install
 Docker Community Edition. To install Docker on your system you can check
 [Docker's documentation directly](https://docs.docker.com/install/). Once
 installed you can [verify it is installed and working
@@ -44,7 +43,7 @@ containers](/troubleshooting.html#docker-linux-containers).
 
 
 ## Why Docker?
-You need to install Docker in order to complete the database analysis. This is because the analysis uses several system dependent software libraries, so by using Docker the analysis can use those libraries without you requiring to install the correct dependencies with the correct versions.
+You need to install Docker in order to complete the source code analysis. This is because the analysis uses several system dependent software libraries, so by using Docker the analysis can use those libraries without you requiring to install the correct dependencies with the correct versions.
 
 ## Using Tidal Tools
 

pages/tidal tools/getstarted.md

@@ -115,20 +115,6 @@ This will save the result to an output zip file, called `code_stats.zip` by defa
 
 Send this file to [Tidal support](mailto:support@tidalcloud.com), and they'll upload it to your Tidal workspace for you.
 
-## Database Analysis
-
-Follow [these instructions](#tidal-tools) to install Tidal Tools on your offline server. 
-
-You can now run the database analysis without any external network connectivity, except to your database host itself:
-
-`tidal analyze db --offline databases.yaml`
-
-This will output a zip file called, `tidal-dba-results_DATE.zip` that can then be uploaded (on the online server) to the application for a given database in order to complete the analysis:
-
-`tidal analyze db --upload tidal-dba-results_DATE.zip`
-
-You should receive confirmation that the upload has completed and can navigate to Tidal to see the results.
-
 ## Gather Machine Stats (For Unix-Like Systems)
 
 ### Installation

pages/tidal tools/tidal_offline.md

@@ -152,15 +152,6 @@ You may need to configure Docker to use your proxy server. You can follow the st
 
 {% include note.html content="If you need to authenticate with the proxy, be sure to include the username and password in the value, ie. 'http://proxy_userid:proxy_password@proxy_ip:proxy_port'" %}
 
-### PostgreSQL database fails to analyze with `tidal analyze db` {#postgres}
-
-Check the [PostgreSQL Server
-User](https://guides.tidal.cloud/analyze-database.html#postgresql-server-user)
-script to verify that the all the necessary permissions were granted. Pay
-attention that different permissions should be applied to different PostgreSQL
-versions.
-
-
 ## Windows specific troubleshooting {#windows}
 
 ### Setting up Docker for Windows to use Linux containers {#docker-linux-containers}

pages/tidal tools/troubleshooting.md

@@ -9,7 +9,7 @@ folder: userguides
 permalink: index.html
 ---
 
-{% include_relative six_steps.md %}
+{% include_relative five_steps.md %}
 
 ---
 

pages/user guides/discovery_techniques.md

@@ -1,12 +1,12 @@
 Cloud migration is the process of moving your data, applications, and other
 elements to the cloud. However, the path to the cloud can be long and painful
-without proper planning and execution.  By following Tidal's six
+without proper planning and execution.  By following Tidal's five
 discovery layering techniques, you will be migrating to the cloud with ease!
 
-{% include image.html file="layered_discovery_expanded.png" caption="Tidal'
+{% include image.html file="layered_discovery_expanded.png" caption="Tidal's
 layered approach to application discovery, for cloud migration." %}
 
-# Six Steps To Discovery Bliss
+# Five Steps To Discovery Bliss
 
 ## 1) Import Your Spreadsheets
 
@@ -90,29 +90,7 @@ checkout this [guide](analyze.html).
 
 ---
 
-## 5) Analyze Your Databases
-
-Analyze all of your databases in minutes and _measure_ the migration
-difficulty.
-
-After running `tidal analyze db your_config.yml` against your databases ([see
-guide](/analyze_database.html)), you will understand which database features in
-your Oracle,SQL Server, MySQL, or PostgreSQL installations make it difficult to
-adopt cloud-native database offerings and also identify which applications are
-connecting to your databases.
-
-With over 100 unique characteristics considered, comparisons are made with the
-data platforms available in the cloud(s) you are migrating to which provide you
-with _data-driven insights_ for planning your cloud migration.
-
-Follow the steps in [the guide](/analyze_database.html), and you will be able
-to quantify the difficulty in migrating your database from Oracle to PostreSQL;
-or from SQL Server to AWS Aurora etc.
-
----
-
-
-## 6) Analyze Your Source Code
+## 5) Analyze Your Source Code
 
 Finally, to find the applications which will migrate more easily to
 cloud-native technologies you can analyze your source code and rank your