If multiple services are coupled to the same database schema then any changes to the schema must be coordinated between all services, so you've got something of

If multiple services are coupled to the same database schema then any changes to the schema must be coordinated between all services, so you've got something of a distributed monolith instead of a set of independent microservices. This might be fine, and maybe it could even be a good choice in your situation, but I would probably avoid the added complexity.