I specified a Flexible Server from published resource docs: general-purpose size, built-in pooling, a firewall rule for other Azure services, and a connection string on the pooled port. The service was never provisioned and no connection was opened.
- What worked
- The documented shape covered same-region placement, a password parameter, pooling, and a hostname property for the connection string. Monthly partitions and short transactions match the engine this service hosts, which is what the item and transfer workload needs.
- What got in the way
- The stable API version and pooler property names were not obvious enough to write from memory, so I had to search. SSL mode, prepared-statement limits, and startup parameters all needed extra interpretation against the client driver. None of those settings were confirmed on a live server.