Tag Archives: server

June 2011 Cumulative Update Refresh

​The June 2011 Cumulative Update has been refreshed with additional updates and fixes that resolve specific issues (see below) that were not included in the June 2011 Cumulative Update published between June 28th, 2011 and July 8th, 2011.  We recommend customers install the latest June 2011 Cumulative Update to take advantage of these updates and fixes.

The latest June 2011 Cumulative Update will install on server farms with an existing June 2011 Cumulative Update installed, Service Pack 1 installed, or on environments where previous or no Cumulative Updates are installed.  To learn more about updating SharePoint 2010 Products see the Updates for SharePoint 2010 Products Resource Center at http://technet.microsoft.com/en-us/sharepoint/ff800847.
 

Issues resolved in the June 2011 Update Cumulative Update Refresh:

• Install fails on environments with .NET 4.0 installed
• Some services do not start when the June 2011 Cumulative Update is installed on environments following a least   privileged model

June 2011 Cumulative Update Downloads

 

Read More

Data Storage Changes for SharePoint 2010

​Today we are announcing two related changes to the way we describe data storage in SharePoint. First, by taking advantage of performance and reliability improvements in SP1 and by defining specific requirements for large data storage in SharePoint, Microsoft is able to increase the supported limits for data storage in SharePoint.

 Additionally, we are announcing that the SQL Server FILESTREAM RBS provider is now supported for use with SharePoint so that lower cost iSCSI connected NAS disk can be used. This post outlines the new data storage support limits and guidelines for scaling to those limits and it defines RBS including the new FILESTREAM RBS provider.

 

The SharePoint Content Database Data Size Limit

With the release of SharePoint 2010 SP1 and some new guidance we are changing the supported data size limits for SharePoint content databases. Prior to SP1 the content database limit was 200 GB for collaboration and 1 TB for document archive. The content database size includes both metadata and BLOBs regardless of where the BLOBs are located and use of RBS does not bypass or increase these limits.
 
The new guidance for supported content database size details outlines specific guidance for SharePoint administrators as the data size grows. If this new guidance is followed SharePoint can support up to 4 TB of data in all usage scenarios and has no imposed size limit for document archive scenarios.  The details are in the TechNet document SharePoint Server 2010 capacity management: Software boundaries and limits and the primary changes are:
 
  1. For a SharePoint content database up to 200 GB there are no special requirements and this limit is included for consistency.
  2. For a SharePoint content database up to 4 TB you need to additionally plan for the following two requirements:
    • Requires disk sub-system performance of 0.25 IOPS per GB, 2 IOPS per GB is recommended for optimal performance.
    • Requires the customer to have plans for high availability, disaster recovery, future capacity, and performance testing.
    • And you need to review additional considerations in the TechNet Boundaries and Limits article.
  3. For a SharePoint content database over 4TB specifically for a Document Archive scenario you are required to additionally plan for the following:
    • SharePoint sites must be based on Document Center or Records Center site templates and must be an archive scenario where less than 5% of content is actively read from each month and less than 1% of content is actively written to.
    • Do not use alerts, workflows, link fix-ups, or item level security on any SharePoint objects in the content database. Note: document archive content databases can be the recipient of documents as a result of Content Routing workflow.
  4. Other specific limits changes being made at the same time:
    • A new limit of 60million items in any one SharePoint content database
    • The specific 5 TB limit per SQL Server instance has been removed.  Instead you should work with a SQL Server professional to plan for database storage.

Please review the full TechNet Article SharePoint Server 2010 capacity management: Software boundaries and limits document.  We have also published a guide on SharePoint 2010 scalability here: http://go.microsoft.com/fwlink/?LinkId=223599. In the near future we will publish a test report of large scale testing that supports these new size limits.

The Value of Remote Blob Store with SharePoint

RBS (Remote Blob Store) is a set of standardized APIs that allow storage/retrieval of BLOBs (binary large object data) outside of your main SQL database where a dedicated BLOB store is desirable. RBS uses a provider model for plugging in any dedicated BLOB store that implements the RBS APIs. RBS was introduced in SharePoint 2010 and providers can be installed into SharePoint and are used to store BLOBs. Documents in SharePoint document libraries are BLOBs and with RBS they can be stored remote to the SQL Server database. This commonly means the BLOBs are stored on the same machine as SQL Server though they may be on a network connected SQL Server machine.
 

Above are two diagrams showing common architectures for SharePoint using RBS. Both show the RBS Client Provider which is installed on the SharePoint Web Front End. The left diagram shows the generic RBS implementation where a third party has implemented RBS to access their storage. The right diagram shows the SQL Server FILESTREAM RBS provider which stores blobs in the Windows file system.
 
By storing BLOBs outside of the SQL Server database there can be certain advantages such as:
·  RBS enables SharePoint Foundation 2010 running on SQL Express to store more data than the SQL Express limit of 4 GB. In SQL Express 2008 R2 this limit was increased to 10 GB.
·  Some operations can be performance optimized with average blob sizes over 1Mb. This result is from tests with the SQL RBS Provider. Ref: http://msdn.microsoft.com/en-us/library/cc949109(SQL.100).aspx
· There could be storage optimizations with potential disk space and disk cost savings from differential backups or tiered storage.
·  We have completed testing on the SQL RBS FILESTREAM provider which can enable iSCSI connected storage for RBS use. Using iSCSI allows for the use of lower cost NAS storage.
·  Other potential data optimizations may be developed by ISV’s using the supported public RBS APIs and SharePoint APIs.
There are a few things to be careful with when implementing RBS:
·  Backup strategy must be carefully considered. Both document metadata and document BLOBs must be backed up at exactly the same point in time. This means any third party backup solution needs to be capable of restoring both the SQL database used by SharePoint and the BLOBs used by SharePoint as a set where no variance occurs which would have the database reference BLOBs that are not available from the same backup.
· RBS is most likely to be used for document archive scenarios where documents are written and not updated. BLOBs in RBS are never updated once they are written; instead a new BLOB is created for any update. BLOBs are immutable, old BLOBs    are garbage collected later. You can read more about RBS garbage collection in this article: http://technet.microsoft.com/en-us/library/ff628583.aspx 
· RBS providers are required to return the first byte of data in a request in 20ms. This applies for all requests between SharePoint and the RBS provider storage layer.
· The SharePoint database is not intended to be read from or written to except by SharePoint. RBS providers don’t have separate access to the data. This includes direct access to blobs. Ref: http://support.microsoft.com/kb/841057/en-us
· Performance may decrease for smaller BLOB sizes when using RBS. This is also shown in the “FILESTREAM Storage in SQL Server 2008” article referenced above.
· There are many RBS providers available and customers should evaluate them for suitability for their implementations.

Additional Documentation from Microsoft on RBS in SharePoint

 
TechNet Documentation RBS Links:
· Plan for RBS (SharePoint Server 2010) [http://technet.microsoft.com/en-us/library/ff628583.aspx]
· Overview of RBS (SharePoint Server 2010) [http://technet.microsoft.com/en-us/library/ee748649.aspx]
· Maintain RBS (SharePoint Server 2010) [http://technet.microsoft.com/en-us/library/ff943565.aspx]

Q & A

·  Q: How come you couldn’t provide these increased data limits when SharePoint 2010 launched?
·   A: We have learned more about how customers implement document archive solutions on SharePoint in the past 12 months. Now by providing specific guidance around data size scaling and focusing supportability around those we can have an increased data size limit for SharePoint and avoid having a data size limit for the document archive scenario.
 
·   Q: What is the new data size limit for document archives on SharePoint
·    A: There isn’t a data size limit, though the new guidance factors for building supportable large scale systems must be followed. If the additional factors are not properly addressed then the lower supportability limit applies.
 
·   Q: What if I really need more than 4 TB on a SharePoint farm and it isn’t document archive?
·    A: You should use a scale out topology. This involves having multiple content databases in a single farm and spread sites out amongst them. Each content database can grow to 4 TB by following the guidance.
 
·  Q: What if I had incorrectly assumed the 200 GB limit could be avoided by moving BLOBs to a Remote Blob Storage provider thereby reducing the amount of SQL Server stored data for SharePoint?
· A: We recommend that you upgrade to SharePoint 2010 SP1 and follow the new guidance for the total size you have. Consult the company you purchased your RBS provider from to ensure they are tested with SharePoint 2010 SP1. If you have a deployment that falls outside of the new and old limits we recommend you to contact Microsoft Support and request a supportability review. This is a paid support review and the support engineer will be able to tell you if your current implementation can be supported or if changes to reduce the data per content database are recommended.
 
·  Q: Since NAS is supported, does the SQL Server RBS FILESTREAM provider allow use of a network share to store BLOBs on?
·  A: No, NAS must be connected using iSCSI and appear as a local drive on the SQL Server machine.
 
·  Q: Will the content database size limit or the 20mS TTFB limit be enforced in the software?
·  A: No. These are support limits that we recommend customers stay within for best performance and in order to get the best support from Microsoft. They are not hard boundaries that are measured by the SharePoint software.
 
·  Q: Where was the old 200 GB limit detailed on TechNet?
· A: It was listed on the SharePoint Capacity Planning Boundaries and Limits page on TechNet. Whilst RBS and BLOBs were not previously specifically called out, the limit of 200 GB was clearly stated for a SharePoint Content Database which includes metadata and BLOBs. This article has been updated for the new limits and to list RBS to be more explicit and to avoid any future misinterpretation.
 
·   Q: Can a large document archive have multiple SharePoint sites collections?
·   A: Yes. However our guidance is that if you have a site collection over 100 GB, it should be the only site collection in a content database.
 
·   Q: Can a large document archive have multiple document libraries?
·   A: Yes. You can have multiple document libraries with different permissions set.
 
·  Q: Is SharePoint 2010 SP1 required to take advantage of these new content database limits?
·   A: No. The limits apply to SharePoint 2010 regardless of whether SP1 is applied. However due to improvements in SharePoint 2010 SP1 you are strongly encouraged to install it.

 

Read More

End of License for Microsoft Office SharePoint Server 2007 for Search

For any customers who might be using Microsoft Office SharePoint Server 2007 for Search, this is a reminder that in 2008, it was replaced with Microsoft Search Server 2008. At that time, Microsoft discontinued support for Office SharePoint Server 2007 for Search. This is especially important to note if you plan to install Service Pack 2 (SP2) for SharePoint Products and Technologies on a server that is running Office SharePoint Server 2007 for Search. This can cause Office SharePoint Server 2007 for Search to incorrectly register as a trial version.

We recommend that you do one of the following instead:  

 


Read More

SharePoint Lifecycle Management Solution with Project Server 2010

Author: Christophe Fiessinger , Senior Technical Product Manager, Microsoft Corporation

I am excited to announce the release of SharePoint Lifecycle Management Solution with Project Server 2010. Microsoft SharePoint Server 2010 provides a vast number of capabilities that empower both business users and IT to create solutions quickly. For this reason, many organizations consider implementing SharePoint as a central platform to address a wide array of business solutions. For those organizations, it is likely that they will need a good way to track, manage, and prioritize those business requests. The SharePoint Lifecycle Management Solution with Project Server 2010 provides a framework and guidance for managing SharePoint business requests and includes two white papers and a sample dataset.

This no-code solution includes:

  • Business Decision Maker/Technical Decision Maker white paper containing a business evaluation of how Microsoft Project Server 2010 can be employed to help manage your SharePoint Lifecycle through enhancement requests and project proposals.
  • Technical white paper contains step-by-step instructions on how to install and customize the SharePoint Lifecycle Management solution, along with basic instructions on how to use it.
  • Project Server 2010 sample databases and templates that can be used to illustrate concepts. The sample dataset requires a farm that has a working installation of Microsoft SharePoint 2010 with Project Server 2010 fully configured (please refer to Project Server 2010 Tech Center); and the Dynamic Workflow and Workflow Visualization web part solutions from Microsoft Project 2010 Solution Starters.
For an overview of the solution produced by Jornata, please watch this recent recording from Tech.Ed last week: http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/OSP202

BDM white paper Table of Content
Why Customers Choose SharePoint
SharePoint as a Central Service
SharePoint Lifecycle Management
Introducing the SharePoint Lifecycle Management Solution with Project Server 2010
    Managing SharePoint Requests
    Discovery and Further Definition
    SharePoint Project Selection
    Project Planning and Management
    Evaluating SharePoint Project Success
SharePoint Lifecycle Management Solution with Project Server 2010: Key Benefits
About the Solution
    Solution Artifacts
Conclusion

Last but not least do not forget to check out other existing white papers on Microsoft Project Portfolio Management offering on our Project site at http://www.microsoft.com/project/en/us/articles-white-papers.aspx.
 

Read More

Take advantage of SharePoint Server 2010 search capabilities from SharePoint Server 2007 by doing a search-first migration

Upgrading to Microsoft SharePoint Server 2010 from SharePoint Server 2007 provides significant enhancements in enterprise search capability. This includes many improvements for end users when they issue search queries and view search results. You can find a summary of these enhancements in  What’s new in enterprise search (SharePoint Server 2010).

However, due to policy or resource constraints, organizations sometimes aren’t in a position to complete an upgrade all at once. If this sounds like your organization, you can still set your end users up to take advantage of search capabilities of Microsoft SharePoint Server 2010 from your existing SharePoint Server 2007 deployment by performing a search-first migration.  

To perform such a migration, you deploy a new SharePoint Server 2010 farm and configure it for search. You reproduce the existing SharePoint Server 2007 farm search settings in the new farm, and then configure the SharePoint Server 2007 farm to forward search queries to the new farm. For this migration you don’t migrate content databases to the new SharePoint Server 2010 farm, for example, or configure any functionality in the new farm that isn’t related to search.

After the search-first migration, your users can take advantage of SharePoint Server 2010 query features and search-results features right from your SharePoint Server 2007 farm! These new query features include prefix matching, Boolean query syntax, phonetic name matching, and query suggestions. Search-results features include results refinement, social tags integration, and relevance improvements. And your users continue to use the existing SharePoint Server 2007 deployment for SharePoint functionality other than search.

Your organization can complete the remainder of the product upgrade at any time that is convenient, but the enhancements that your users gain in search capability will probably give your business decision makers an incentive to fully adopt SharePoint Server 2010 as soon as possible!

You can find a full description of the search-first migration process in this series of articles on TechNet. Read the articles, try out the process, and let us know how it goes!


Read More

SharePoint 2010 Developer Virtual Labs Online

Three new MSDN Virtual Labs are live running SharePoint Server 2010 and Visual Studio 2010. You can work on these labs and learn SharePoint 2010 development without having to install SharePoint 2010 or Visual Studio 2010 on your machine. All you need is a web browser that can support our remote desktop ActiveX control and you can run these labs on our servers.

 

MSDN Virtual Lab: Developing a Visual Web Part in Visual Studio 2010

After completing this lab, you will be better able to work with existing Web Parts and Linq and also you will be more familiar with connecting two web parts.

MSDN Virtual Lab: Developing a BCS External Content Type with Visual Studio 2010

After completing this lab, you will be better able to build a BCS External content type, create a Business Data Catalog Model project, configure the External Content Type for offline use, and open the list using Outlook.

MSDN Virtual Lab: Developing SharePoint 2010 user interface with Silverlight in Visual Studio 2010

After completing this lab, you will be better able to create a basic Silverlight application that displays a SharePoint list inside a datagrid and deploy the Silverlight application to SharePoint, and also create a Silverlight application that displays SharePoint list data in a graph using the Silverlight Graphing controls.


Read More

FILESTREAM with SharePoint 2010

​Author: Bill Baer, Senior Technical Product Manager, Microsoft Corporation – SharePoint

FILESTREAM is a new feature in SQL Server 2008 that enables the storage of unstructured data on a NTFS file system. FILESTREAM (local or remote) is supported in SharePoint 2010 as one mechanism of reducing capital expenditures through enabling the storage of large binary unstructured data on content addressable or commodity storage.

Unstructured Data
Unstructured data refers to information that does not adhere to a defined model or does not fit well into relational tables in SharePoint unstructured data can refer to Microsoft Office document file formats, video, audio, and related file types.
 
Structured Data
Structured data in SharePoint refers to the metadata associated with its corresponding unstructured data or BLOB. Relational databases are most often cited as examples of structured data.
 
SQL Server and Unstructured Data Storage
There are three (3) approaches to storing unstructured data with SQL Server, RBS, SQL BLOB, and FILESTREAM:
  • Remote BLOB Storage (RBS) in which SharePoint relies on a new layer in SQL Server to read or update BLOB data stored outside of the database on separate BLOB Stores (file system or dedicated BLOB stores)
  • SQL BLOB which refers to traditional BLOB storage with SharePoint, BLOB data is stored along side the structured metadata in the Content Database
  • FILESTREAM
 
FILESTREAM Overview
FILESTREAM is implemented on the varbinary(max) datatype instructing the database engine to store unstructured data on the file system through a FILESTREAM filegroup that contains file system directories instead of the files themselves also known as data containers. Data containers are the interface between database engine storage and file system storage. varbinary is the binary data type designation for binary large objects stored in SharePoint 2010 content databases and refers to variable-length binary data. (MAX) refers to a value that max indicates that the maximum storage size is 2^31-1 bytes or otherwise 2GB. Remote BLOB Storage does not provide a mechanism to exceed to the 2GB file size limit imposed by SharePoint.
 
In SharePoint 2010 remote BLOB data is referenced by a unique identifier in content databases configured for RBS (see illustration).
 
 
 

 
 
FILESTREAM offers several benefits as related to performance 1) FILESTREAM uses the NT system cache for caching file data reducing the effect that FILESTREAM data has on Database Engine performance and 2) the SQL Server buffer pool is not used; therefore, memory is available for query processing.
 
FILESTREAM provides optimum value in scenarios where SharePoint is used to storage large BLOB data such as video files that will benefit from FILESTREAM or BLOB data that exceeds 1MB.
 
Special Considerations
 
FILESTREAM and Business Continuity Management
 
Database mirroring does not support FILESTREAM since a FILESTREAM filegroup cannot be created on the principal server and database mirroring cannot be configured for a database that contains FILESTREAM filegroups. If the FILESTREAM provider is used to store BLOB data locally (within the same content database) the database cannot be configured for database mirroring.
 
If the FILESTREAM provider is configured to store the BLOB data within a separate SQL database or when using a 3rd party BLOB store, the content database can be mirrored; however, database mirroring will apply only to the content database and not the BLOB data. The BLOB data needs to be handled separately and kept in sync with the associated metadata (content database). For FILESTREAM BLOB databases, this can be done through log shipping.
 
To learn about the differences between FILESTREAM and SQL Server Remote BLOB Store see also http://blogs.msdn.com/b/sqlrbs/archive/2009/11/18/sql-server-remote-blob-store-and-filestream-feature-comparison.aspx.
 
FILESTREAM and the Office Web Applications Cache
 
The Office Web Applications cache is used by Word and PowerPoint Web Applications to create a version of a document requested for viewing through the browser improving performance and reducing resource consumption on server machines by making cached versions of a document or presentation available in cases where there are multiple requests for the same document. 
 
The Office Web Applications cache occurs in two (2) distinct tiers, on the server file system and within a “specialized” site collection hosted on a per Web application basis. Document or presentation requests made through the Office Web Applications are served through both caches as the images are rendered for client consumption. Both cache locations are used by all site collections within a Web application where the Office Web Applications features activated.
 
Content databases where FILESTREAM is configured will store the cached versions of the document or presentation in the configured provider location.  It is recommended to configure the Office Web Applications cache on a database that is not configured for FILESTREAM.
 
Configuring FILESTREAM with SharePoint 2010
The instructions that follow are designed to be used on a single-server deployment for demonstration purposes and implements the local FILESTREAM Provider.
 
Enable FILESTREAM on the target SQL Server Instance
 
1.       On the Start menu, point to All Programs, point to Microsoft SQL Server 2008 (R2), point to Configuration Tools, and then click SQL Server Configuration Manager.
2.       In the list of services, right-click SQL Server Services, and then click Open.
3.       In the SQL Server Configuration Manager snap-in, locate the instance of SQL Server on which you want to enable FILESTREAM.
4.       Right-click the instance and then click Properties.
5.       In the SQL Server Properties dialog box, click the FILESTREAM tab.
6.       Select the Enable FILESTREAM for Transact-SQL access check box.
7.       If you want to read and write FILESTREAM data from Windows, click Enable FILESTREAM for file I/O streaming access. Enter the name of the Windows share in the Windows Share Name box.
8.       If remote clients must access the FILESTREAM data that is stored on this share, select Allow remote clients to have streaming access to FILESTREAM data.
9.       Click Apply.
10.    Click Start, click All Programs, click Microsoft SQL Server 2008 (R2), and then click SQL Server Management Studio.
11.    In SQL Server Management Studio, click New Query to display the Query Editor.
12.    In Query Editor, enter the following Transact-SQL code:
 
EXEC sp_configure filestream_access_level, 2
 
In Query Editor, enter the following Transact-SQL code:
 
RECONFIGURE
Provision the RBS Data Store
 
1.       Click Start, click All Programs, click Microsoft SQL Server 2008 (R2), and then click SQL Server Management Studio.
2.       Expand Databases.
3.       Select the content database for which you want to create a BLOB store, and then click New Query.
4.       In SQL Server Management Studio, click New Query to display the Query Editor.
5.       In Query Editor, enter the following Transact-SQL code:
 
use [Database Name]
 
if not exists (select * from sys.symmetric_keys where name = N’##MS_DatabaseMasterKey##’)create master key encryption by password = N’Admin Key Password !2#4′
 
In Query Editor, enter the following Transact-SQL code:
 
use [Database Name]
 
if not exists (select groupname from sysfilegroups where groupname=N’RBSFilestreamProvider’)alter database [Database Name] add filegroup RBSFilestreamProvider contains filestream
 
In Query Editor, enter the following Transact-SQL code:
 
use [Database Name]
 
alter database [Database Name] add file (name = RBSFilestreamFile, filename = ‘c:\BlobStore’) to filegroup RBSFilestreamProvider
Install the Microsoft SQL Server 2008 R2 Remote Blob Store
 
Download the x64 package for the Microsoft SQL Server 2008 R2 Remote Blob Store from the Microsoft SQL Server 2008 R2 Feature Pack at http://www.microsoft.com/downloads/en/details.aspx?FamilyID=ceb4346f-657f-4d28-83f5-aae0c5c83d52&displaylang=en.
 
Open a Command Prompt with Administrator permissions and execute the following command to install RBS.MSI downloaded in the previous step:
 
msiexec /qn /lvx* rbs_install_log.txt /i RBS.msi TRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME="<Database Name>" DBINSTANCE="<Instance Name>" FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1
 
NOTE
Specify the full path to RBS.MSI in the above state, i.e. C:\Users\Administrator\Desktop\RBS.MSI. Replace the values for DBNAME and DBINSTANCE to match your environment.
 
Enable Remote BLOB Storage
1.       On the Start menu, click All Programs.
2.       Click Microsoft SharePoint 2010 Products.
3.       Click SharePoint 2010 Management Shell.
4.       In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statement to set the content database to be configured:
$database=Get-SPContentDatabase –Identity “Database Name”
In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statement to gets the object that holds settings that determine how the content database uses Microsoft SQL Server Remote Blob Storage:
$rbs=$database.RemoteBlobStorageSettings
In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statement to determine if RBS has been installed for the selected content database:
$rbs.Installed()
NOTE
The result of $rbs.Installed() should be True, if the result is False, verify RBS.MSI has been installed successfully by reviewing rbs_install_log.txt. Ensure the install statement was running In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statement to enable RBS for the selected content database:
 
$rbs.Enable()
In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statements to set the RBSprovider for the selected content database:
$rbs.SetActiveProviderName($rbs.GetProviderNames()[0])
 
$rbs
 

NOTE
The result of $rbs should be:
Table 1

 
Appendix for Table 1
 
Enabled specifies whether or not RBS has been enabled for the selected content database.
 
ActiveProviderName is name of the SQL Remote Blob Storage provider new files will be stored in. This will be null if new files will not be stored using SQL Remote Blob storage.
 
MinimumBlobStorageSize refers to the minimum size a BLOB may be to be considered RBS storage worthy, BLOB data exceeding the specified MinimumBlobStorageSize will be stored in the RBS data store.
 
FILESTREAM performance data shows BLOB data exceeding 1MB provides the most efficient streaming performance. See also http://msdn.microsoft.com/en-us/library/cc949109(SQL.100).aspx.
 

 
To configure the MinimumBlobStorageSize:
1.       On the Start menu, click All Programs.
2.       Click Microsoft SharePoint 2010 Products.
3.       Click SharePoint 2010 Management Shell.
4.       In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statements to configure the MinimumBlobStorageSize at 1MB:
$database = Get-SPContentDatabase “Database Name”
 
$database.RemoteBlobStorageSettings.MinimumBlobStorageSize=1048576
 
$database.Update()
UpgradePersistedProperties specifies the collection of field names and values for fields that were deleted or changed.
 
Validate Installation
To validate the FILESTREAM configuration and RBS installation:
 
1.       Click Start, click All Programs, click Microsoft SQL Server 2008, and then click SQL Server Management Studio.
2.       Expand Databases.
3.       Select the content database for which you want to create a BLOB store, and then click New Query.
4.       In SQL Server Management Studio, click New Query to display the Query Editor.
5.       In Query Editor, enter the following Transact-SQL code:
USE [Database Name]
SELECT * FROM dbo.DatabaseInformation
Confirm that both the RBSCollectionId and RBSProvider rows are available.
 
Test the RBS Data Store
1.       Select a desired Document Library on a site in the configured content database.
2.       Upload a file that is greater than 1 MB.
3.       On the computer that contains the RBS data store, click Start, and then click Computer.
4.       Browse to the RBS data store directory.
5.       Browse to the file list and open the folder that has the most recent modified date (other than $FSLOG). In that folder, open the file that has the most recent modified date. Verify that this file has the same size and contents as the file that you uploaded. If it does not, ensure that RBS is installed and enabled correctly.
The data store directory structure will appear similar to that in the following diagram.
 

 
NOTE
In the event error "The URL ‘<Document Library>/File’ is invalid. It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web.” is displayed when uploading documents greater than the configured MinimumBlobStorageSize open SQL Server Configuration Manager and enable Enable FILESTREAM for file I/O streaming access and restart the SQL Server (MSSQLSERVER) service.
 
Additional Resources

 

 

Read More

Just Released – Best Practices Resource Center for SharePoint Server 2010

Hi – the Best Practices articles and the Best Practices Resource Center for 2007 were some of our most popular content for that release. We’re pleased to announce that we now have a 2010 version of the Best Practices Resource Center. Like in 2007, this was a joint effort between the SharePoint Customer Engineering team and Microsoft Consulting Services team for SharePoint. They drew on real customer experiences to help us bring you a set of guidelines that lay out the best practices for success with SharePoint Server 2010. Following these practices will help you avoid some of the common deployment pitfalls and keep your SharePoint environments available and performing well. Get the details now from the Best Practices Resource Center.

More best practices articles are in the works and will appear in the coming weeks and months on the Resource Center and in the Best Practices section of the Technical Library, so keep checking back for more info.

– Samantha Robertson


Read More

Export your own TechNet book

You can now build your own book of TechNet articles! For several product versions, the SharePoint IT Pro content team has published collections of TechNet articles as downloadable books that you can read offline and print. We’ve been able to cover only the most basic content sets. Each SharePoint Server or SharePoint Foundation environment is different, and none of the basic books exactly matches any environment.

Happily, our partners at TechNet have introduced a beta release of a new feature that you can use to build your own custom collections of articles! You can choose any articles (up to 100 per collection) from the TechNet library. That means that you can mix content from SQL Server, SharePoint Foundation, Windows Server, Office — any content in the TechNet library. The functionality is in Beta testing right now, but it’s accessible for public use and we encourage you to try it out. Here’s how.

You’ll need a recent browser. Internet Explorer 8 and Internet Explorer 9 work, as do the recent versions of other browsers. You’ll also need a Live ID for signing in to TechNet to export your collection.
Make sure you’re looking at the Lightweight view of the TechNet library. Go to the TechNet library home page. If you’re in Lightweight view, you should see something like this in the upper right corner:
If you don’t, click Lightweight in that corner to switch views.

To build a collection:

  1. Click the arrow next to the printer icon in the upper right corner, and then click Print Multiple Topics.
     
    The Help page will open.
  2. Read the overview on the Help page, and then click Start. The Print Multiple Topics toolbar will appear at the top of the window.
  3. Browse through the TechNet library, picking topics for your collection. Right-click a topic in the left pane to add it or it and its children to your collection.
  4. When you’re finished, click Collection on the Print Multiple Topics toolbar.
  5. On the Manage Collection page, you can change the order of topics and organize them into chapters.
  6. To download or print your collection, choose your file format (XHTML or PDF) and click Export. (Here’s where you sign in to TechNet by using your Live ID if you’re not already signed in.)
  7. Right-click the link to your collection to download it, or click the link to open it.

To start a new collection, click Delete on the Manage Collection page. There’s no way to have multiple active collections yet, so be sure you have a copy of the HTML or PDF file of your existing collection if you want to save it.

We hope you find this Beta functionality useful. Let us know!

 


Read More

Troubleshooting resources for SharePoint Server 2010

This post provides tools, techniques, and links to other resources that can assist you in troubleshooting issues you might encounter with SharePoint Server 2010.

Universal Logging System (ULS) logs

One of the most helpful tools for troubleshooting problems with SharePoint Server 2010 is the Universal Logging System (ULS) logs. You can use data from the ULS logs in SharePoint Server 2010 to troubleshoot problems in the farm. The ULS log can collect data at varying levels depending upon the logging settings. You can use Windows PowerShell to filter the data, display it in various ways, and output the data to a data grid with which you can filter, sort, group, and export data to Excel Services. For more information, see View diagnostic logs (SharePoint Server 2010).

For additional information about how to use Windows PowerShell to filter, display, and output ULS log data, and how to use the Correlation ID displayed in an error message to help troubleshoot the error, see Microsoft Press: Using Windows PowerShell to Perform and Automate Farm Administrative Tasks.

You can also use the ULS Viewer tool to open a ULS log file and display its contents in a user friendly format. To download the ULS Viewer tool and its user documentation from MSDN, go to ULS Viewer.

SharePoint Health Analyzer

SharePoint Server 2010 includes a new tool named SharePoint Health Analyzer  that enables you to diagnose and resolve configuration, performance, and usage problems. SharePoint Health Analyzer runs predefined health rules against servers in the farm. A health rule runs a test and returns an alert that tells you the outcome of the test. You can use Central Administration to view alerts and resolve problems. For more information, see Viewing and resolving SharePoint Health Analyzer alerts (SharePoint Server 2010) and SharePoint Health Analyzer rules reference (SharePoint Server 2010).

Configure verbose-level logging

You can configure diagnostic logging to record verbose-level events. This means that the system will log every action that SharePoint Server 2010 takes. You can use verbose-level logging to record a greater level of detail when you are making critical changes and then re-configure logging to record only higher-level events after you make the change. For more information about how to configure verbose-level logging, see Configure diagnostic logging (SharePoint Server 2010).

Use verbose-level logging sparingly because it can quickly use drive space and adversely affect drive and server performance. For more information about how to troubleshoot a trace log that has reached its maximum size, see ULS trace log reaching maximum size – Event 8094 (SharePoint 2010 Products).

Check features and services

If you get errors when using any SharePoint feature, it is often a good first step to ensure that a necessary SharePoint feature is activated and any related services are running, if only to rule out the feature or service as a cause of the problem. For more information, download the “Understanding and troubleshooting SharePoint 2010 technology features and services” white paper .

Additional resources

For TechNet documentation, see Troubleshooting (SharePoint Sever 2010) (http://technet.microsoft.com/en-us/library/gg609831.aspx)

To search for additional solutions for an issue, go to the following sites:.

 

 


Read More