Hot answers tagged sql
8
I'd go for the SQL database. For several reasons:
Storing into SharePoint list adds a lot of overhead that you don't need.
With 20K items per day you'll reach the supported max in 15000 days and list throtling limit in 6 hours
But most important with that amount of data what you want to get out is aggregate to make sense of the data. And this is the area ...
6
First of all you should just rule out the use of SQL. You should not use SQL directly against SharePoint content databases. If you ever do modifications directly using SQL that SharePoint Farm becomes unsupported for ever. Even just doing reads makes your SharePoint Farm unsupported as long as they are occuring and may cause any kind of problems as ...
5
I would, and have in the past, use a separate SQL database to store all of that data. This will require additional work for the presentation of the data, but using BCS, SSRS and/or PowerPivot, you can pretty easily pull that into SharePoint. I wouldn't put that much into a SP content database and expect good things ;)
4
I'd highly discourage doing this kind of operation.
Even though reads from the content database only makes your installation unsupported as long as they are occuring, you shouldn't do them.
The problems you'll run into are:
You are very likely to affect SharePoints operations in unsupported ways remember you can't even read without introducing locks
You ...
4
SharePoint Search will return the url to the document in Path when it thinks a file is a document (isDocument == 1), but if the file isn't a recognized file type SharePoint will treat it as a list item and return the url of the display form in Path.
You can add support for more file types by adding IFilters (see here for PDF: How to configure PDF iFilter ...
3
A simple way would be to make either a SharePoint list that contains all of the fields you need or an external sql table then have a timer job cache the results daily (or more?).
You could also (either in additional, or only) have the call on the page write the results to a table/list and query that table/list before making the expensive call.
The second ...
2
well, state service just use SQL DB to store user session data so Guids are most probably refers to current User session. Lock on a SQL table can appeared after too many requests at the same time. Probably your State Service is a performance bottleneck for a bigger farm? Could you please enable SQL profiling on State DB and check its performance and locks?
...
2
You'll likely want the SharePoint Products and Technologies Protocol Documentation. These contain descriptions about the database structure, including table schema, sprocs, and so forth... Along with a lot of other information. And as everyone else has noted, making changes is, for the most part, unsupported. Check out KB841057 for more information on ...
2
What you are looking at IS the URL needed.
Forms/DispForm.aspx?ID=45
Let's break that URL down.
"Forms/" It's a form.
"DispForm.aspx" That's the form used to display results; which is what the search spider used. But with out an ID entry, you won't get any form results, just the form.
"?ID=45" that's the particular form results to pull up and display.
So ...
2
Yes it is possible. (based on readings, I never done it myself)
You will need to create WCF web services and then use them as external content in your BCS to create an external list in your SharePoint environment (which I assume is SP 2010).
Or you can utilize StreamAccessor as explained in article below,
Accessing BLOB Data from External Systems Using ...
1
You have two questions here:
1) You can display the page via a Page Viewer Web Part. It renders as an <iframe> tag.
See Page Viewer Web Part
2) You might want to look into External Content Types and Business Connectivity Services, but this will require custom code. So if that isn't an option for you, you're probably best off sticking with option 1.
1
step by step guide:
In this walkthrough we will demonstrate how to integrate DB2 database
with Microsoft SharePoint 2010 through ODBC and display DB2 data on
SharePoint 2010 page. In order to do that we will describe how to
create a new external content type by means of BCS Meta Man.
1.Prerequisites:
1.Microsoft SharePoint Server 2010
...
1
What John said is true. You ought not directly interact with the SharePoint databases.
However, when you state "Now I was asked to have all the data available in a 2007 Sharepoint Server" what it sounds like you actually need here is the Business Data Catalog service available in SharePoint 2007. It allows you to surface and interact with the data in your ...
1
You need to follow this guide:
http://technet.microsoft.com/en-us/library/cc512725(v=office.14).aspx
or
1) Run this stsadm command:
stsadm -o renameserver -oldservername oldservername -newservername
newservername
2) Rename and reboot server.
3) Enter Central Admin and look over all your Alternate Access Mappings (you’ll have to change to the new ...
1
Another option would be to hook into the list via SQL Server Reporting Services and create a reporting endpoint. This would then allow you to secure the data as you want, fetch the data in a supported way and provide the users the functionality they need.
Access to the report is secured through SSRS and then within the report itself, you can dictate who is ...
1
Microsoft does not support accessing SharePoint database directly via SQL. As @Trevor said, it will put your environment in an unsupported state and we (in this community) cannot provide you any guidance that would result in such.
Sometime ago I did write a blog post about how to access SharePoint data via the SharePoint object model in an SQL CLR ...
1
daZza,
Yes Business Connectivity Services is the key here, and you have set up External Content Type and External List that is perfect solution to sync with SQL Server table!
Now what you can do is create a View in your database and write a SQL Query to provide a column as StatusForSharePoint or something and using CASES in T-SQL send information like ...
1
You just need the Database Engine Services (not even its children features). The management tools (basics) are recommended to quickly & visually manage your instance but they can be installed on a separate machine.
Anything else is optional and not required / used by SharePoint Foundation 2010 and it's always a good practice to limit your installation ...
1
If you're querying multiple Site Collections use FullTextSQLQuery since it searches across the farm and if you plan to query Pages Library of a single Site Collection, use SPSiteDataQuery instead. I think you might need SPSiteDataQuery?
SPSiteDataQuery queryObj = new SPSiteDataQuery();
//query Pages libraries
queryObj.Lists = "<Lists ...
1
For SharePoint 2010, I'd recommend using the Client Object Model. It allows for development without having to resort to installing SharePoint on the developer's PC (or developing ON the SharePoint server).
http://msdn.microsoft.com/en-us/library/ee857094.aspx
Only top voted, non community-wiki answers of a minimum length are eligible
