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.
Related
We have an Access 2016 database with lots of tables, forms and reports from a client. The client would like other people to access the data in this database but doesn't want to spend the money to convert the forms and reports to a website. They would rather have Access 2016 as a frontend with it's forms and reports and store the data in a centralized location. The issue is the users who will access this data won't be on the same LAN or network.
The solution I came up with was to use SQL Azure as the database backend and keep the forms and reports in the Access 2016 database frontend. Can anyone think of an alternative? Does Microsoft have some kind of online hosting with Office 365? I have nothing at all against SQL Server and use it frequently but just don't want to go through the effort of upsizing the database when a simpler solution existed.
You can certainly place the back end on SQL Azure. However given that a typical internet connection is about 100 times slower, then MUCH effort is required to optimize the application. So you need significant experience on how to optimize an Access application to work with SQL server. This setup is thus doable, but will take significant amounts of work to achieve decent performance.
Another possible solution is to use a SharePoint or office 365 back end (which supports SharePoint tables). This setup only works well if table’s sizes are in general below 5000 records. You also have to ensure all table relations are standard auto number PK and child tables use a standard long number column to relate back to the parent table.
Likely the best solution is to setup a server and run remote desktop. This gives the best performance, and the end users don’t need to install access nor your front end part.
I explain in detail the “slowness” with using SQL server over the internet in this article of mine along with some suggestions and possible solutions.
http://www.kallal.ca//Wan/Wans.html
Working on migrating documents out of the document library and into a different system and I want to export out of the SQL server the metadata associated with the documents into the new system.
I'm using SQL Management Studio and HIEDISQL to look and find these records but I cant find them anywhere via searching.
This is SQL server 2008 running Sharepoint 2010.
Any help would be greatly appreciated.
I have googled a lot for the last week and have not been able to come up with anything since Google is trying to be smarter than my "exact phrase" searches so its been pretty frustrating :(
I had this same issue, but ended up using the .Net Client Side Object Model. Pluralsight has some excellent training videos on this. I'm not certain but I think the actual storage structure for the metadata is in a varbinary or some other sort of blob field, so it might not even be feasible to access by direct query. Also, direct querying of the sharepoint database could void your support agreement with MS.
Hope this helps...
I want to kow what is the different between Sharepoint fast search service and Sql server fulltext search?
Or Can I abstract the Sharepoint fast search from the Sharepoint platform as a isolate component?
Thank you.
David
Well they have nothing in common and FAST is a search engine either implemented and integrated in SharePoint or used standalone. In SharePoint 2010 FAST was sold as an additional component while it is standard in SharePoint 2013. Microsoft purchased the company building FAST a couple of years ago and have kept some 70-80% of the technology in SharePoint 2013.
I believe you still can buy the FAST Search Server as a standalone product but would not quite understand why since the SharePoint version of FAST is way easier to work with.
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.
After reading through some articles on LightSwitch, I'm left wondering what prevents a LightSwitch user creating queries that over load the data-source, mainly SQL databases.
From my initial understanding, a LightSwitch user is not a developer or DB admin, and may little understanding of the impact a seemingly simple query can have on a multi-user database.
Does LightSwitch have built in governance, caching etc, is it safe to let the user have access to the last years sales data?
I don't believe there is anything built into LightSwitch for this, however this should be able to be handled on the DB server.
If you're running SQL Server 2008 they've got resource governance built in.
MSDN SQL 2008 Resource Governance
Specific example