Data in sql azure, we have an existing webapi expose the data with odata. Issue is client want to make a call with filters with substring query on a few columns, which making performance really slow. we are debating at this point whether to use full text search index or use the azure search service, thoughts please?
Some of the considerations and tradeoffs between hosting search in Azure Search vs. using SQL Server FTS are captured here.
As pointed out above, Azure Search can index in-database data - see Connecting Azure SQL Database to Azure Search using indexers.
You can point Azure Search at your AzureSQL database and it will index it without you having to write code, but Azure Search is a service you have to pay for on hourly basis and you can learn more information about it here.
Azure Search is recommended for performing searches on various sources and application
Azure search can be used instead of Full-Text search, but If you need to join search results with other tables, then Full-Text Search is recommended.
Hope this helps.
Related
Moving from AWS Glue to Azure Purview and i am confused about something
Its is possible to query Azure purview data catalog/assets in the same way we can query from AWS Glue data catalog using AWS Athena?
Unfortunately, you cannot query data from Azure Purview.
The Purview search experience is powered by a managed search index. After a data source is registered with Purview, its metadata is indexed by the search service to allow easy discovery. The index provides search relevance capabilities and completes search requests by querying millions of metadata assets. Search helps you to discover, understand, and use the data to get the most value out of it.
The search experience in Purview is a three stage process:
The search box shows the history containing recently used keywords
and assets.
When you begin typing the keystrokes, the search suggests
the matching keywords and assets.
The search result page is shown with assets matching the keyword entered.
For more details, refer to Understand search features in Azure Purview.
We need to implement search functionality on a table which might contain more than 100 000 records.
What is the best approach for the search when thinking about performance? Our product is a multi tenant with single database and search data may grow in future. What are the limitations of both searches?
As always - it depends (e. g. which queries you perform, indexes etc...). In gernal if you only have simple queries, I would stick to Azure SQL Database. If you need more complex search features like geospatial search or ranking, you can try Azure Search.
I would like to use our azure search index as data source for Power BI dashboard/report. Is there any azure search service connector available for power bi like document DB connector ?.
I don't know where the data is stored in the Azure Search? Please suggest me a way for connecting the data with power BI.
Note: Not asking about the Azure Search Traffic Analytics.https://powerbi.microsoft.com/en-us/blog/visualizing-azure-search-data-with-power-bi/
Thanks in Advance!
I understand you are not interested in traffic analytics. I am also assuming that you are not interested in displaying index statistics.
The actual structure of the "inverted index" created using Azure Search is not exposed, so there is no way for you to visualize it in PowerBI.
Luis Cabrera
Program Manager
Cloud AI Platform - Microsoft
I am new to Azure Search and I have just seen this tutorial https://azure.microsoft.com/en-us/documentation/articles/search-howto-dotnet-sdk/ on how to create/delete an index, upload and search for documents. However, I am wondering what type of database is behind the Azure Search functionality. In the given example I couldn't see it specified. Am I right if I assume it is implicitly DocumentDb?
At the same time, how could I specify the type of another database inside the code? How could I possibly use a Sql Server database? Thank you!
However, I am wondering what type of database is behind the Azure
Search functionality.
Azure Search is offered to you as a service. The team hasn't made the underlying storage mechanism public so it's not possible to know what kind of database are they using to store the data. However you interact with the service in form of JSON records. Each document in your index is sent/retrieved (and possibly saved) in form of JSON.
At the same time, how could I specify the type of another database
inside the code? How could I possibly use a Sql Server database?
Short answer, you can't. Because it is a service, you can't specify the service to index any data source. However what you could do is ask search service to populate its database (read index) through multiple sources - SQL Databases, DocumentDB Collections and Blob Containers (currently in preview). This is achieved through something called Data Sources and Indexers. Once configured properly, Azure Search Service will constantly update the index data with the latest data in the specified data source.
We're looking to move a database from a local SQL 2008 server to SQL Azure however we use FREETEXTSEARCH which is currently unsupported. Is there an alternative to FREETEXTSEARCH that we could use that is supported on AZURE, and/or can you write a custom function that does the same thing?
I would take a look at Lucene.Net. It is great free text search engine. There is a Azure version available. It powers the search on StackExchange network. Lucene on Azure.
You can use FULLTEXT search Azure SQL just doesn't provide you an interface to create full indexes, you'll have to create them via script.