You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 19, 2024. It is now read-only.
I would like to know if GraphView will ever support Azure SQL Elastic Pool/Tools so we can apply sharding and multi-tenancy (maybe using RLS?) to the GraphView.
Thanks!
The text was updated successfully, but these errors were encountered:
A short answer is: we already have. GraphView does not create a new type of databases. A graph database in GraphView is a regular SQL DB. You create any number of Azure SQL DBs and add them to an elastic pool. An application connects to an individual DB and executes graph operations through GraphView. A DB experiencing a high volume of graph workloads will consume more resources, which is controlled by the elastic pool.
As for sharding, GraphView connects to an Azure SQL Database instance, which does not scale out. Hence, you have to do sharding manually.
As for the elastic database jobs service that runs T-SQL scripts across all DBs in the pool, our view is that this is mainly for DB administration scripts, scripts that are unrelated to graphs. It is possible that you want to run same graph operations across all DBs. If there is a strong demand on this scenario, we will support this. Before that, the current hack is to intercept the T-SQL scripts GraphView generates before it sends to the SQL DB, and then to submit such T-SQL scripts through the elastic database job service manually.
GerHobbelt
pushed a commit
to GerHobbelt/GraphView
that referenced
this issue
May 25, 2021
Awesome work Guys!
I would like to know if GraphView will ever support Azure SQL Elastic Pool/Tools so we can apply sharding and multi-tenancy (maybe using RLS?) to the GraphView.
Thanks!
The text was updated successfully, but these errors were encountered: