The current image I am using for MSSQL is the Azure SQL Edge image and according to official docs, this image doesn't support Full-Text Search.
Since the above mentioned image doesn't support Full-Text Search, is there another way to run the MSSQL container with the Full-Text Search on M1 Mac?
Related
We came with a requirement to Search SQL table which contain documents data in Image/binary column type. we are trying to do this with Elastic-search and Azure Search. we can able to proceed with Elastic-search but hit roadblock on Azure Search as indexing is not possible for these data types thru indexer.
can any body help us, is there any possibilities to achieve this with Azure Search?
Please see my response to your question on MSDN.
In short, currently, in order to use Azure Search built-in document extraction capabilities, the files need to be stored in Azure blob storage. Then, you can use the blob indexer.
Does anyone know of a tool to visualize a graph created in Cosmos DB Graph?
I'm looking for something like Gephi (https://gephi.org/), or the tool that OrientDB or Neo4j use.
I'm looking for something that will "connect" to the database. Gephi appears to require an export, and then it uses the exported file. The tools for OrientDB & Neo4j will connect to the server instance and provide graphical results of queries.
BTW, I'm working with the Azure Cosmos DB Emulator at the moment. So I need something that will work on a local development website (localhost).
Download Cosmos DB extension for vscode.
It works well with gremlin API (with some known issue), check below link
https://github.com/Microsoft/vscode-cosmosdb
There is actually a pretty decent web app for graph visualizations available in the Azure Portal. Inside your Cosmos account just click the QuickStart button and then select the Guided Gremlin Tour:
Create the SalesGraph (you can point the app at any of your graph enabled collections later) and then download the package and run the solution file. You might have to modify the connection strings in appsettings depending on which graph you want to talk to.
My site is not written for sharepoint.
It runs on IIS(aspmvc) interacts over http request/response and fetches db data.
Does it make sense to install and use Microsoft 2013 sharepoint search for the db indexing and free text querying (ms sql) ?
(I know I can use MS Full Text Search but the features and performance are too poor)
(I know I can use Solr/Lucene. It is a great solution indeed. I just wonder if I can do it in MS technologies)
Can I install it not as a part of Sharepoint? as a standalone indexer?
How? will it require sharepoint foundation search?
Should I install Microsoft Search Server 2010 instead for this feature? Is it as good as 2013 sharepoint search?
Thanks.
Not going to answer your questions one by one, so just skimming through them:
You will not be able to use any of SharePoint's searches without installing SharePoint. There is no separate search server for SP2013 anymore, it's all one product.
So to answer your question three: SP2013 is better than using Search Server 2010 as it includes some FAST features which you previously had to pay for. For a complete comparison what you get with the free version (foundation) see this page:
SharePoint 2013 feature comparison chart all editions
You can search through any publicly available website with the default SharePoint search, you can also use it to search using webservices or using GET parameters. It would also be possible to directly search through your database using BCS (Business data connectivtiy services), but the foundation version is a bit limited there.
I think the main problem is that you would have to install the whole SharePoint and maintain it as well. I'm not sure it's worth the hassle installing the whole product if you only want to use search. This is exactly Microsoft had inteded for the Search Server 2010 product, but they discontinued it.
Your questions quickly answered:
Sure, it's a number one product for search. See Garnters analysis about this.
Search Server 2010, yes you can. SP2013, no.
2013 includes the FAST search component, you previously had to pay a lot for. It's better.
My 2 cents: If you only want search, go with a search product like Lucene based products. If you want "more" than just search, or you don't want to get into yet another technology (if you already know some SharePoint) - go with SP.
I am trying to group points of geospatial data based on density and relative distance. Is there a way that this can be done in SQL Server 2008 using the spatial features or would it be better to translate the data into graph data and use a graph clustering algorithm?
As far as I know there are no inbuilt spatial methods for clustering points in SQL Server 2008. I've never come across any examples of this done in T-SQL / at the database level.
It would be far easier to go with your second approach and do these calculations at the application level - using R, GRASS, MapServer depending on your needs / development preferences.
If it is just for displaying clusters of points (rather than associated analysis) then check out the following links:
OpenLayers
http://openlayers.org/dev/examples/strategy-cluster.html
Google
http://googlemapsapi.martinpearman.co.uk/articles.php?cat_id=1
http://econym.org.uk/gmap/example_clusterer.htm
Python / PostGIS
http://wiki.osgeo.org/wiki/Point_Clustering
Does anyone know if the problems that have been affecting Stack Overflow with regards to SQL Server 2008 Full Text Search performance have implications for the search in SharePoint? As far as I understand it SharePoint search uses SQL Server full text search.
SharePoint 2007 has its own search database, to store items such as search scopes and other things.
The actual search index does not use full text search, but stores it's information inside a file based index.
So any search queries run on SharePoint will not cause the issue.
Search crawling of a site is another story, the implementation of which I am not completely sure of. However, most SharePoint sites are not subject to the same transactional throughput that a site such as StackOverflow are hit with.
Morevoer, if a SharePoint site was used to host data as transactional as StackOverflow, very serious performance issues would likely result.
So search in SharePoint 2007 is not going to have the same issue as StackOverflow.
I would not completely rule out some performance hits while a search crawl is running with a SQL 2008 back end, but with decent scheduling and sub 100gig databases, issue should not be noticed by users.
I'm not aware of any problem with SQL Server under 2008, but I'm sure it won't affect SharePoint 2007.
Since 2007, SharePoint search no longer user SQL Search.
If you're running SharePoint 2003, I'm not sure SQL 2008 is supported.