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...
Related
I have recently started working with SQL databases of which I have no previous experience with. I have added the datasource to my project using the Visual Studio wizard and the DataSet appears in my solution explorer.
Everything that I have read thus far has shown connecting to the SQL server and then sending query commands, but since I have added the direct reference to my project is this necessary. I thought since I had added the reference to my project I would have direct accesbility to it, but it appears that is not so.
Also to help the searching process a view has been created on the SQL server that polls all of my desired fields in a single shot. I have linked this view to my dataset after utilized the datasource wizard. Any recommendations on how I can access the data from that view?
I apologize for the vagueness of my questions, but I am not really 100% sure the questions I need to be asking. I appreciate the help.
Thanks
Turns out the best means to solve this problem was to ditch the Data Source Wizard and use standard SQL queries.
I can't believe that I have not yet found the answer to this question.
All I want to know is where to start in terms of using SQL tools (queries or SSIS I assume) to query CRM online (2013) and bring data into a table.
Is this even possible?
I want to download data, then I want to transform then I want to put it back. I'm sure I can work out that once I know to start!!!
Many thanks, Warren
Unfortunately, CRM Online doesn't give you direct access to the database layer via SSMS.
There are some good samples in the CRM SDK that show how to retrieve data if you are up for writing some C#. This is their intro sample for how to connect to your CRM instance, gather some data, display it, and then update the entities. http://msdn.microsoft.com/en-us/library/hh675400.aspx
Once you manage to connect to your CRM instance, you will have access to all of your CRM data objects.
What I can suggest you based on my experience is you can get Data From CRM Online to your SQL using SSIS and you can use SSIS Integration Toolkit for CRM for it.
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.
Fellow Developers I have been working on creating a Database with SQL Server 2005, now I finished that step, its a huge and massive one. Now the company wants me to export their data from their Access 2007 db to this sql 2005 database I created.
I know that I will be using field mapping, but is it actually possible to do that ?
Any Suggestion ?
A major portion of my job is converting data from one data source into another. I am actually doing a Filemaker Pro to SQL Server conversion right now. I have tried some of these Automatic solutions and they are hit or miss depending upon the complexity of the data involved. Usually, I do it by mostly by hand writing scripts (I do automate some of the scripts using a VB6 application I created many years ago).
I have found that doing the scripts by hand always produces the best conversions.
This fellow describes how he did it. There is a tool called "SQL Server Migration Assistant (SSMA) for Access" that you can download from Microsoft. The blog also has a Word document that you can download for a step-by-step description of what to do.
You can download SSMA here and possibly just figure out how to do it without searching further.
It depends on the complexity of the import. Try using SQL's import wizard first. If that's too limited, you may need to create an SSIS package.
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.