1
vote
Serving large file (dozens of GB) to client from a server-side query to the Azure SQL database?
No, you should NOT expose the database publicly. This is very difficult to do safely, and is difficult to integrate directly with a HTTP-based API.
So what you're doing – having a web app backend that ...
- 135k
1
vote
Caching or in-memory table in Azure for performance
The answer, as with most performance related questions, is to measure. With 3G speeds in mind, the data transmitted between server and client is your bottle neck.
Do whatever is quickest from a ...
- 41.9k
1
vote
Should we do data migration from Oracle via the microservices, or should we do direct data migration from Oracle to Azure SQL DBs?
Clone and cut
Give every team an exact duplicate of the database. It is their job to prune and transform this data as fits their needs.
They can achieve this transformation via their own database ...
- 16.3k
1
vote
Continuous Deployment Database Project VSTS
Here's how we do it...
Any simple changes that can be made via DACPAC deployment are handled in that manner
For any other changes, an individual SQL script is created which makes the change and ...
- 3,123
1
vote
Should I move to In-Memory tables and stored proc or NoSql (CosmosDB)
It really depends on your data and how much of it you have. A very common approach these days is to have a hybrid approach. The SQL database is the store of record, and then something like ...
- 46.3k
1
vote
Accepted
Should I move to In-Memory tables and stored proc or NoSql (CosmosDB)
Ok. I think the slowness is mainly a factor of your sql. Which can be streamlined.
First, examine whether you really need the database generated id rather than a guid. or in the case of your parent ...
- 79.8k
Only top scored, non community-wiki answers of a minimum length are eligible