## The problem
Issue vercel/storage#114 (closed, 13 comments): When creating new migrations after having created the first one already, Prisma errors because the database schema isn't empty. This is because Prisma needs a separate database to be used as a shadow database. While it's not a bug per se, it's still a limitation in Vercel since you can only connect one Postgres storage per project environment. To work around this you'd have to create another Postgres storage and manually set a new environment variable to be used as `shadowDatabaseUrl`. ``` Error: P3005 The database schema is not empty.
## What fixed it
Prisma error P3005 ('database schema is not empty') on Vercel Postgres migrations was solved by Neon: the shadowDatabaseUrl workaround is no longer recommended and it should work by default now. If you're still carrying a manually created second Postgres storage just for the shadow database, you can remove that config. Note that migrations count toward your Written Data limits, which is a separate thing.