Remove saga migration sample (#6409)

* remove saga migration sample

* remove reference to sample

* few more

Author: lailabougria

persistence/sql/index.md

@@ -6,7 +6,6 @@ related:
  - samples/sql-persistence/simple
  - samples/sql-persistence/transitioning-correlation-ids
  - samples/saga/sql-sagafinder
- - samples/saga/migration
  - persistence/upgrades/sql-2to3
  - persistence/upgrades/sql-1to2
  - persistence/upgrades/sql-1.0.0-1.0.1

persistence/sql/migrating-from-nhibernate.md

@@ -33,7 +33,7 @@ NHibernate has an `OutboxRecord` table shared by all endpoints, where in later v
 
 ## Outbox retention
 
-If the outbox retention period is set to a very large period and the message throughput is high then such a migration will take a while to complete. It is recommended to keep the retention period as low as possible. 
+If the outbox retention period is set to a very large period and the message throughput is high then such a migration will take a while to complete. It is recommended to keep the retention period as low as possible.
 
 - [NHibernate Deduplication record lifespan](/persistence/nhibernate/outbox.md#deduplication-record-lifespan)
 - [SQL Persistence Deduplication record lifespan](/persistence/sql/outbox.md#deduplication-record-lifespan)
@@ -54,16 +54,4 @@ Downtime migration that uses custom scripting with deep knowledge on saga state
  - Requires custom saga migration mappings
  - Downtime is relative to the size of the data set
  - Pretty easy if the saga state schema is fairly flat
- - Required for outbox,  timeouts, and subscriptions
- 
-### Runtime migration
-
-Runtime migration means that both NHibernate and SQL Persistence are used. New saga instances are created via SQL Persistence while legacy instances stored using NHibernate eventually will be removed once these saga instance complete.
-
-The [Saga migration from NHibernate to SQL Persistence sample](/samples/saga/migration/) shows how this can be achieved.
-
-- Complex deployment
-- Requires saga logic to be mainted for both persisters
-- Does not require serialization knowledge
-- No downtime
-- Not very suitable for saga instances that never complete or when instances complete far into the future
+ - Required for outbox,  timeouts, and subscriptions

persistence/sql/saga.md

@@ -6,7 +6,6 @@ related:
  - samples/sql-persistence/simple
  - samples/sql-persistence/transitioning-correlation-ids
  - samples/saga/sql-sagafinder
- - samples/saga/migration
  - persistence/sql/saga-concurrency
  - persistence/sql/sqlsaga
 redirects:
@@ -37,7 +36,7 @@ NOTE: Using [delimited identifiers](https://technet.microsoft.com/en-us/library/
 ### Columns
 
 
-#### ID 
+#### ID
 
 The value of `IContainSagaData.Id`. Primary Key.