From 658fc200edd7955c78fdc020068cf136a9af325e Mon Sep 17 00:00:00 2001
From: Alper Ebicoglu <ebicoglu@users.noreply.github.com>
Date: Fri, 29 May 2020 16:33:09 +0300
Subject: [PATCH] add sample connection string

---
 docs/en/Entity-Framework-Core-Oracle.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/docs/en/Entity-Framework-Core-Oracle.md b/docs/en/Entity-Framework-Core-Oracle.md
index ed15ae79ea..94b7b45f04 100644
--- a/docs/en/Entity-Framework-Core-Oracle.md
+++ b/docs/en/Entity-Framework-Core-Oracle.md
@@ -27,6 +27,11 @@ Oracle connection strings are different than SQL Server connection strings. So,
 
 You typically will change the `appsettings.json` inside the `.DbMigrator` and `.Web` projects, but it depends on your solution structure.
 
+A sample connection string for Oracle:
+```
+Data Source=localhost;User Id=myuser;Password=mypassword;
+```
+
 ## Re-Generate the Migrations
 
 The startup template uses [Entity Framework Core's Code First Migrations](https://docs.microsoft.com/en-us/ef/core/managing-schemas/migrations/). EF Core Migrations depend on the selected DBMS provider. So, changing the DBMS provider will cause the migration fails.