Hash Shard Map with SQL Azure - sql-server

I've been doing some reading about sharding SQL Azure databases with Azure Elastic Scale. The article discusses two types of shard maps: List and Range. What about Hash shard maps? My application requirements are to evenly distribute data across shards which would seem to require a hashing of the shard key. Is this possible with SQL Azure and Azure Elastic Scale?

At this point in time Elastic Database tools (formerly known as Elastic Scale) doesn't support hash shard maps.
Thanks
Silvia Doomra

Related

How to create autosuggestion with Azure Cosmos Document DB?

I want to create autosuggestion within Azure Cosmos Db.
I can see that there is Azure cognitive search and Elastic stack services that can be used to achieve this. However, I have couple 1000 records only, and they are not expected to grow very large.
Now Cognitive search and Elastic stack feels like overkill.
So How can I create autosuggestion (index and queries) with Azure cosmos DB?
The Source of my NOSQL Cosmos DB data is SQL DB. I switched from SQL to NOSQL only for autosuggestion thing only because FullText search and LIKE on SQL side are not faster. dotnet core api is responsible for syncing of SQL to NOSQL Db Data.

How do I check the data integrity after migrating a Cassandra database onto AWS Keyspaces

I am trying to migrate Cassandra cluster onto AWS Keyspaces for Apache Cassandra.
After the migration is done how can I verify that the data has been migrated successfully as-is?
Many solutions are possible, you could simply read all rows of a partition and compute a checksum / signature and compare with your original data for instance.Then iterating through all your partitions, then doing it for all your tables. Checksums work.
You could use AWS Glue to perform an 'except' function. Spark has a lot of usefull functions for working with massive datasets. Glue is serverless spark. You can use the spark cassandra connector with Cassandra and Keyspaces to work with datasets in glue. For example you may want to see the data that is not in Keyspaces.
cassandraTableDataframe.except(keyspacesTableDateframe).
You could also do this by exporting both datasets to s3 and performing these queries in Athena.
Here is a helpful repository of Glue and Keyspaces functions including export, count, and distinct.

Do Azure Elastic Database Pools allow Cross Database transactions?

We have Stage database, which contains stored procedures, and transfers data into an OLTP Database.
Do Elastic SQL Databases reside on same server, and give ability to conduct cross-db stored procedure transactions?
Would Elastic databasepool allow this?
https://learn.microsoft.com/en-us/azure/sql-database/sql-database-elastic-pool
You can achieve elastic transactions spanning across databases using .NET client applications. This is currently under preview.
Elastic transactions at server side are planned in future.
for more information

Azure Cosmos DB indexing for gremlin queries

I have gone through many documents where indices are created but the APIs used are SQL API for Azure cosmos but no example for Gremlin API. Any help would be appreciated. Thanks!!
Azure Cosmos DB is a schema-agnostic database that allows you to iterate on your application without having to deal with schema or index management. By default, Azure Cosmos DB automatically indexes every property for all items in your container without having to define any schema or configure secondary indexes.
For more details, we can see Indexing policies in Azure Cosmos DB.
Azure Cosmos DB support Gremlin API. You can use the indices for your Gremlin queries.
Reference: Querying with indexes
Hope this helps.

How to enlarge the storage size Azure SQL Database greater than 4 TB?

We are in the process of developing a web application that we want to host on Azure, where the storage size of the SQL database database is expected to reach 100 TB.
The issue is the max size of the Azure SQL database is currently 4 TB which too small in our case.
Knowing the fact that we are using DTU pricing model, is there any workaround for this issue?
You need to scale out by using SQL elastic pool. You will be using shard database, in other words creating different Azure SQL databases. Azure SQL elastic pool will make it easier to manage the database and query the data in a simple way using one Azure SQL Database elastic query.
I recommend reading the following documents from Microsoft docs:
sql-database-elastic-scale-introduction
sql-database-elastic-scale-shard-map-management
sql-database-elastic-query-overview

Resources