SQL Tran Docs
  • Overview
    • About
    • Getting started
    • Object lifecycle
    • Why is there no AI inside?
    • Performance considerations
    • Security considerations
    • Assessment
    • Unlocking projects
    • Interface walk-through
    • Translation scenarios
    • Prerequisites for Azure Marketplace deployment
  • Emulation Scenarios
    • Emulation in SQL Tran
    • SQL Server to Fabric Warehouse
      • Data types
      • Case sensitivity
      • Cursors
        • Basic cursor loop
        • Cursor types
        • Fetch direction modes
        • Cursors in control flow
        • Nested cursors
        • Data modification cursors
        • Multiple cursors
        • Subqueries and filtering
      • Named procedure parameters
      • Result set limiting
      • MERGE statements
      • Computed columns
      • External tables
      • Materialized views
      • Identity columns
      • Unsupported system objects
    • Synapse Analytics to Fabric Warehouse
      • Emulations
      • Limitations
    • SQL Server to Synapse Analytics
    • Oracle to PostgreSQL
  • Project wizard
    • Source database
    • Target database
    • Wrapping up
  • Projects
    • Project list
    • Overview
    • Workspace
    • Reports
    • Tests
    • Scratch pad
    • Settings
      • Project name
      • Mapping
      • Database connections
    • Navigation
    • Object complexity
    • Static analysis
    • Translation errors
    • Exporting and importing projects
  • Workspace
    • Object tree
    • Data lineage
    • Code
    • Actions
      • Overriding source
      • Overriding target
      • Ignoring objects
  • Tests
    • Workflow
    • Configure SQL Tran
    • Connecting to databases
      • Fabric Warehouse
      • Synapse Dedicated SQL Pool
      • Azure SQL Database, Azure SQL Managed Instance, Microsoft SQL Server
    • Tables
    • Views
    • Procedures
    • Functions
    • Triggers
    • Performance tests
  • Scripter
    • About
    • Supported databases
    • SQL Server
    • Azure SQL
    • Synapse Dedicated Pool
    • Oracle
    • PostgreSQL
    • MySQL
Powered by GitBook
On this page
  • Quota for the web application
  • Database quota
  1. Overview

Prerequisites for Azure Marketplace deployment

PreviousTranslation scenariosNextEmulation in SQL Tran

Last updated 3 months ago

To deploy SQL Tran on Azure Marketplace, one needs to have quota in the region where they plan to deploy:

  1. Quota for our web application

  2. Quota for the managed Postgres database we use to keep track of the projects

Quota for the web application

Unfortunately, AppService web application quota cannot be provisioned using the Azure portal. You need to ask support for it.

First, open a support request.

Then, pick Azure services, Service and subscription limits (quotas), select the desired subscription, and choose the "Web app" quota type.

In request details, specify that you need "P3mv3", which means a 8-core vcpu with 64 GB of RAM.

Database quota

For Postgres database, you do not need to raise a support ticket, fortunately.

Search for Quotas in Azure portal.

Click the "Azure PostgreSQL" button.

We need a "Standard_D2s_v3" instance, so let's search for DSv3. Once that's listed, select your region and click on the tiny pencil icon on the right end of its row to edit the region quota.

Change the limit. We only need two, but if you are at zero, perhaps set it to 4 or 8.

Open a support request
Specify it's about the Web App
In details, specify you need P3mv3
Select Postgres quotas
Edit your region
Do not forget to click Submit :)