Tag Info

Hot answers tagged

20

I would like to take the opportunity to pimp a few of the posts on my own blog: Site Topology Planning Part 1 Site Topology Planning Part 2 Environments can vary quite a bit in the number of site collections they will have or how deep the site hierarchies will go. The amount of content in those site collections also can very. I once had a sub-site that ...


14

My response echo's a little of what Mike said... a lot of site collections stay pretty small, in which case it is much more efficient to keep them in a single content database so that there's not as much overhead (more about the number of objects in the instance than a performance perspective) in SQL Server associated with them from a database perspective. ...


12

It is not possible to have multiple content databases service a single site collection. You would need to find a way to actually migrate the content from your one site collection to multiple site collections. In situations where there is a single site collection that holds a bunch of sub-sites, such as in an Intranet scenario, I would look at moving the ...


9

The TechNet Article "Storage and SQL Server capacity planning and configuration (SharePoint Server 2010)" should be your first port of call: http://technet.microsoft.com/en-us/library/cc298801.aspx


8

Yes we do need it. Search indexing is really made up of two items: the actual index file which contains keyword AND the search database that contains metadata. The two are combined when a search is initiated The search database contains settings related to search (content sources, confguration, all that good stuff). In addition it will also contain the list ...


8

Try SharePoint PowerShell: Get-SPDatabase http://njbblog.blogspot.com/2011/03/sharepoint-40-powershell-get-spdatabase.html


8

As James mentions it's not a valuable comparison as it's two completely different tools. No "SharePoint is not a database" and no "SQL is not a collaboration, document management, ... platform". But to answer your question only point 7 and 8 has been changed (fixed) in SP2013. For more information: Here is my take on the eight points: Primary and foreign ...


7

There is an information worker download of a complete environment from Microsoft. This includes a pre-populated sample AD, documents, lists, libraries, profiles, etc. http://blogs.msdn.com/b/cjohnson/archive/2011/09/15/2010-information-worker-demonstration-and-evaluation-virtual-machine-sp1.aspx


6

As well as the other good information already provided by Mike and John there is also the flexibiliy you can gain from using multiple databases when you rely on the native SQL Server/SharePoint admin tools for managing your environments. For a starter it may make your content deployment/migration and backup/restore scenarios easier (from a database ...


6

In SharePoint 2010 you can add additional Content Databases to your Web Application and then use the Move-SPSite PowerShell command to move site collections from one database to the other. To add a Content Database: Goto Central Admin > Application Management > Manage Content Databases. Select your web application and add a database. To use the ...


6

SharePoint will store the full copy of any document/page for each version of that document/page. In some cases (as with Wiki pages), SharePoint will highlight content to show what changed from version to version, but with documents and pages, the entire file is stored in the content database. This is why storing multiple different versions of large documents ...


6

Apologies if this doesn't directly answer your questions, but I think the main point to be made here is that SQL databases and Microsoft SharePoint solve two completely different issues. Can you store documents and collaborate with people using SQL out of the box? Can you find colleagues with similar skills, interests who have uploaded documents you are ...


6

James is so right, it's not SharePoint vs SQL Server, it's a matter of using the right tool for the right business needs but to go deeper in these assumptions Cascading Delete / Primary & Foreign Keys are available since SP2010 and handled through built-in features like : Unique Column policy Joins between lists Projected Fields Relational ...


5

What is your feature doing? Depending on the modifications it makes in code it could touch either config and /or content databases.


5

Something to be aware of along with SQL aliasing is the SQL instance. There are instances where if patching hasn't been applied, features and services within SharePoint will not configure properly on named instances. This you can also bypass using SQL aliasing. Personally, I am a proponent of SQL Aliasing, but you should always make sure that you configure ...


5

If you want to know databases in your farm instance, use Get-SPDatabase as suggested by another answer. If you want to understand what databases sharepoint creates and what exactly sharepoint stores in them, check Databases That Support SharePoint 2010 Products


5

Why not simply using Central Admin... :-) (works even if you do NOT have access to either the physical server (console) or databases server. Central Admin -> Upgrade and Migration -> Review Database Status. By pasting /_admin/DatabaseStatus.aspx at your CA url. Rgds, Arjan Vos


5

SharePoint always stores the full file. It never tries to do diffs. I haven't seen it documented regarding Site pages anywhere but if you ON A DEV BOX tries this: Create a new Team site with relative url "Team" Modify Home.aspx in SharePoint Designer Turn on Major/minor versioning of "Site Pages" Check out Home.aspx Modify Home.aspx in SharePoint Designer ...


5

In terms of technology opportunities and capabilities you could : 1. Create your own Visual Studio BDC Model where you could create your own Entities, with relationships mirroring your configurations - additionally you could rely on Stored Procedures for various operations not available otherwise, e.g. Updates across multiple tables, View selecting from ...


4

Run the configuration wizard and disconnect the server from the farm. You may be able to run NewSID and change the identity of the machine and then re-join the domain. You certainly want to create a new farm for the test environment.


4

All queries against SharePoint data should be done through the SharePoint Object Model or Web Services. Creating solutions that access the database directly will result in an unsupported installation of SharePoint. Though you have nothing preventing you from doing direct SQL queries, you will not get any support on this site for doing anything that will ...


4

Here are the instructions for moving the databases for: Sharepoint 2007 SharePoint 2010 Also, it is a Best Practice to use SQL Aliases when referencing any instance of SQL server from a SharePoint farm. Doing so makes all future database moves a great deal easier.


4

AFAIK, using the existing services; it is not possible to access the content database informations from Client Object model or services. As a work around you can create your own WCF service and deploy it in SharePoint, which can provide your required data. How to Customize WCF Services in SharePoint 2010 SharePoint 2010: Create Custom WCF Service


3

It's make me to laugh sometime when i look at SharePoint the way programmed. My scenario really sucks, We have a huge 1.3 Tera (single) content database, and we thought we need reduce the size the share point be faster, We planned to create a custom to archive old content/documents to the separate record center and it's archived, here comes the truth the ...


3

SharePoint will NOT shrink the actual SQL Server database files. Removing items in SharePoint will delete the files (after passing the recycle bin procedure as Lori says) and free up space within the file which makes room for new files - without expanding the database files. You can shrink the database files if you need to (probably get shot by saying this ...


3

Making a Web Part that adds, updates or deletes item from a database is just standard ASP.NET programming. For instance if you want to insert a record to a database then you probably would like to add a button to your Web Part that has a click-handler method in which you make the database operations.


3

To rename the SharePoint_AdminContent_[some guid] database the process is the same as under SharePoint 2007. Run as a user with the appropriate privileges to make these changes. stsadm.exe -o deletecontentdb -url http://[ca server]:[ca port] -databasename SharePoint_AdminContent_[some guid] -databaseserver [Your DB Server] Rename the database using a tool ...


3

It's impossible to answer in general terms. It all depends on the nature of the SQL connectivity issues, and also the specifics of the farm topology. Also the usage profile of SP activity is very important here. You will have noticed "cannot connect to SQL" flooding you SharePoint server event logs, but it could well be the case that end users are not ...



Only top voted, non community-wiki answers of a minimum length are eligible