For EF6, I can check whether a database exists in the following way:
context.Database.Exists()
How can I do this in EF Core?
Add a comment
|
4 Answers
I have found the solution on my own:
(context.GetService<IDatabaseCreator>() as RelationalDatabaseCreator).Exists()
It works for EF 7.0.0-rc1-final version for SqlServer
UPDATE:
Entity Framework Core 2.0:
(context.Database.GetService<IDatabaseCreator>() as RelationalDatabaseCreator).Exists()
6 Comments
Marcel
Entity Framework Core 2.0:
(context.Database.GetService<IDatabaseCreator>() as RelationalDatabaseCreator).Exists()
Jeroen
For EF Core 2.0: There is no need for casting, just use context.Database.GetService<IRelationalDatabaseCreator>() instead
michasaucer
I had wierd problem with EF Core 3.1. I needed to add manually
using Microsoft.EntityFrameworkCore.Infrastructure; in my code. Intellisense didnt tells me what i need to do to get GetService() method.
Ramil Aliyev 007
It don't correct working in EF 3.1 for me. For example database exists but Exists() method return false
DonBoitnott
Note that this will also report false if the database is simply offline or inaccessible to the user due to permissions. In other words, this is really not "exists", but instead more like "can I connect to it right now".
|
UPDATE .Net Core 3.1
To check if a database exists and can be contacted:
dbContext.Database.CanConnect()
7 Comments
Rachanee Saengkrajai
This throw
SqlException error if the database does not exist.
emp
@RachaneeSaengkrajai It would throw an exception if it cannot connect with the SQL server. If the database does not exists but the server is accessible, it just returns false.
Augusto Barreto
For me it returns false in both cases. No exceptions are thrown.
DonBoitnott
Frankly I like this answer better than the accepted one simply because it's clear what you're asking. The Exists() method is really no better than this.
John Pittaway
This works on EF Core 7 with SQL Server
|
The other solutions tell you whether the database is connectable:
context.Database.GetService<IRelationalDatabaseCreator>().Exists(); //true
context.Database.EnsureDeleted();
context.Database.GetService<IRelationalDatabaseCreator>().Exists(); //true
I want to know whether the database exists:
context.Database.GetService<IRelationalDatabaseCreator>().HasTables(); //true
context.Database.EnsureDeleted();
context.Database.GetService<IRelationalDatabaseCreator>().HasTables(); //false
Note this weird behavior:
context.Database.EnsureDeleted();
context.Database.GetService<IRelationalDatabaseCreator>().HasTables(); //false
context.Database.EnsureCreated();
context.Database.GetService<IRelationalDatabaseCreator>().HasTables(); //true
context.Database.EnsureDeleted();
context.Database.GetService<IRelationalDatabaseCreator>().HasTables(); //true !!
So it's not perfect, but depending on your use case it could be useful.
1 Comment
James Poulose
Exists() does return false for me after EnsureDeleted() is called.Entity Framework Core 6.0.7:
dbContext.GetService<IDatabaseCreator>().CanConnect();
works for NpgsqlDatabaseConnector - the Npgsql.EntityFrameworkCore.PostgreSQL 6.0.5 provider and probably for all RelationalDatabaseCreator descendants since it tests if database really exists as the default/base implmentation.
1 Comment
Barabas
for Npgsql.EntityFrameworkCore.PostgreSQL 7.0.0 I defined the method in my class
AlternativeContext : DbContext with the if statement Database.CanConnect().