FWIW I think the database is an integral part of one's service, and should often be included in unit tests (depending on the size of the unit of course).
E.g. if you have CRUDObject and want to test GET and PUT of that...and that is the unit you want to test.. mocking away the DB is (IMO) not as good as including a real database with no data in it (they come in Docker images and making a fresh DB namespace within a running sql server for a single test can be very cheap / cheap enough).
E.g. if you have CRUDObject and want to test GET and PUT of that...and that is the unit you want to test.. mocking away the DB is (IMO) not as good as including a real database with no data in it (they come in Docker images and making a fresh DB namespace within a running sql server for a single test can be very cheap / cheap enough).