Hi everyone,
I’m facing an issue while running my Shopify app on Azure. Although the deployment was successful, I’m seeing this error in the logs:
“Error: The table session does not exist in the current database.
at PrismaSessionStorage.pollForTable (/node_modules/@shopify/src/prisma.ts:162:11)”
Do I need to set up an SQL database on the server for this? I’m not storing any data in the app, so I’m not sure if it’s required.
Hey @amit_kumar1 
- are you using our React library to get the app set up initially?
This guide here should help you set up the Prisma table if you’re using the library. One thing that could potentially cause that error would be if you haven’t added an auto-migration to the boot sequence for your app in Azure.
If you double check to make sure your app’s Prisma schema is created properly, you still do have to run the DB migration when the app is first initialized: like this
npm run prisma migrate dev -- --name add-app-name-here
You would still need to include Prisma even if you’re not storing data, as this is where apps using our library store the tokens for each store that installs your app, and is used by the @shopify/shopify-app-session-storage-prisma package to manage sessions.
Hope this helps - let me know if I can clarify anything on my end here 
Hlw @Alan_G Thanks for your reply
I am having dev-sqlite file in my project. So do I need to create additional database in my server to store session data, If yes then how can I configure it?
Here is the screenshot for the file
Hey @amit_kumar1! Thanks for following up.
I noticed in your screenshot there that you have a dev-sqlite file in your project.
SQLite works great for local development, but I can’t provide specific guidance on implementing it in production since our Shopify app library uses Prisma for session storage - so that would be my recommendation for your Azure deployment.
The session storage package we provide in our app template (more info here) needs to reliably store authentication tokens for each shop that installs your app, and Prisma handles all that complexity for us, which is why we recommend sticking with it.
For production on Azure, I’d suggest following Prisma’s deployment patterns and using either Azure Database for PostgreSQL or MySQL (Azure’s guide here). You’d generally update your prisma/schema.prisma file to use the right provider and set up your DATABASE_URL environment variable in your Azure App Settings to point to your production database.
That said, I’m limited to providing support for implementations using our libraries and templates, but hopefully this points you in the right direction!
Let me know if I can clarify anything about the Prisma setup