Tag Archives: specific

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

Service Pack 1 for SharePoint 2010 Products documentation

After months of planning and hard work, Service Pack 1 for SharePoint 2010 Products is live and available for download. Service Pack 1 provides additional functionality and specific fixes, such as the ability to recover site collections and sites from the Recycle Bin, granular management and insight into storage using StorMan.aspx (Storage Space Allocation), and many others.

The SharePoint documentation team has published new and updated articles that were available as of June 28. For more information about these articles, as well as to learn what’s new in this service pack, download the Service Pack 1 for SharePoint Foundation 2010 and SharePoint Server 2010 white paper.

The following SharePoint team blog post provides more information about the contents of the service pack, such as its contents, how to download it, and FAQs: http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=984

You can also visit the Updates for SharePoint 2010 Products Resource Center (http://technet.microsoft.com/en-us/sharepoint/ff800847.aspx) to get detailed information about installing the service pack.


Read More

How do you create a macro to only refresh certain sheets in an Excel workbook?

I have some external references to a Sharepoint list. There are certain sheets that have these connections that must be refreshed on the press of a button.

How can I only refresh certain sheets?! Please help
Can I refresh the sheets one at a time in the command…?

Something like ActiveWorkbook.Refresh.Sheets(“SheetA”) ???

I’m creating a button to refresh specific worksheets and their connections. So it could be multiple lines of code to refresh one worksheet. Please help!

Chosen Answer:

Given that the only available commands are either

activeworkbook.refreshall

or

workbooks(index).refreshall

it seems you can’t directly.

Reading around it looks like you can’t refresh when sheets are protected.

It may be a lot of hassle, but I suppose you could have each sheet linked to a separate workbook and you only refresh those you want to refresh.
by: flyingtiggeruk
on: 5th August 11

SP 2010: How To – Event Receivers and Custom Error Pages

Author: Tobias Zimmergren http://www.zimmergren.net | http://www.tozit.com | @zimmergren
Introduction
SharePoint 2007
Many of you are aware that in SharePoint 2007, you can create Event Receivers (aka. Event Handlers) to take care of things for you when specific things happen. For example, yo … (More)
Read More

Take 2: Lists as Native SQL Server Tables in SharePoint 2010? #spc09 #SP2010

Last week, while at the SharePoint Conference in Las Vegas, I wrote a blog post on being disappointed that SharePoint 2010 does not seem to include a critical feature promised by Bill Gates and Tom Rizzo in their keynote speech at last year’s (2008) SharePoint Conference.

The feature promised was a one-to-one relationship (as needed for specific applications) between a SharePoint List and a native database table (SQL Server, Oracle, etc.). I explain in my first blog post why I think this is an extremely important feature to have.

Turns out that this feature IS included in SharePoint 2010! It is just that it did not receive the level of coverage in this year’s keynote speech that I was expecting based on the expectation that Microsoft built up in last year’s keynote speech. So, I missed it even though I was sitting in the audience during last week’s keynote.

I discovered that the new feature exists (and truly looks outstanding) after getting back home and starting to watch some of the recorded breakout sessions that I didn’t get a chance to attend.

The specific new features that enable this are named External Content Types and External Lists. These two new features fall into the overall category of the new Business Connectivity Services feature-set of SharePoint 2010.

The way this works is that you can now create (using SharePoint Designer 2010 or Visual Studio 2010) External Content Types which are really just a definition of an external database table (or web service). Once an External Content Type is defined for the external database table, an External List can be created (using the SharePoint 2010 browser UI, SharePoint Designer 2010 or Visual Studio 2010). The External List behaves just like any first-class List in SharePoint 2010. Anything you can do with a native List in SharePoint 2010 (workflows, permissions, views, etc.) can be done with External Lists.

But, the data that is displayed and stored for an External List is not stored in the SharePoint 2010 content database. The data in the External Lists lives in the external database table – and, only there. Therefore, if it is updated by a non-SharePoint application (think an ERP system or CRM system for instance), the data that is displayed in the SharePoint External List will update immediately.

This is totally different from the way the MOSS 2007 Business Data Catalog worked. In the MOSS 2007 BDC, the business data brought into SharePoint was stored in a List column(s) in the SharePoint Content Database. So, if the data changed in the external database, the values in the corresponding SharePoint List did not get updated immediately.

Futhermore, in the MOSS 2007 BDC it was not really possible to update data in the external database from within SharePoint. With External Content Types and External Lists in SharePoint 2010, all of that has changed. If you change a value of a column in a SharePoint 2010 External List, the new value is immediately written to the external database.

The last, but certainly not the least, important announcement is that External Content Types and External Lists are “baked-in” to SharePoint 2010 Foundation (the new name for WSS 4.0). This means that all of this goodness is now available to any organization that chooses to use SharePoint 2010, regardless of whether you are using a free or premium version of SharePoint.

Very exciting!

Read More

SPMetal – Specified cast is not valid

Problem:  I am using LINQ to SharePoint to retrieve data.  A specific SPMetal list request generates the error “Specified cast is not valid”.  Additional error information shown in the UI:
Web Part Error: Unhandled exception was thrown by the sandboxed code wrapper’s Execute method in the partial trust app domain: An unexpected error has occurred.
From the stack trace:
“at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcess.ExecuteDelegate.EndInvoke(IAsyncResult result)”
Hypothesis: The error message is a standard error thrown in a SharePoint sandbox solution. The underlying issue is that the proxy is working on lists using SPMetal however only 1 list is causing the problem.  I remembered that I had altered the list using Powershell.   Obviously the entity proxy class generated is based on the old list.  Generate the proxy with the latest lists.
Resoultion: Run SPMetal again to correct the proxy code as the proxy classes do not match the backend SharePoint lists. 

Read More

Working with Microsoft Dynamics(TM) CRM 3.0

Get a practical, hands-on introduction to the fundamentals of adapting Microsoft CRM 3.0 to meet your specific business needs. With topics that include developing new functionality, designing implementations, and integrating Microsoft CRM with other business applications#151;including Microsoft Office Outlook- and Microsoft SharePoint- Products and Technologies#151;this is the only book written for both developers and those who implement business solutions. Authored by experienced practitioners, this book provides case studies, integration and performance guidelines, and toolsets#151;the information you need to help you create successful CRM solutions. This book also explains how to maintain Microsoft CRM, making it of interest to IT professionals who support Microsoft CRM users. And power users will learn how to customize individual Microsoft CRM experiences. This introduction includes a 120-day evaluation copy of Microsoft CRM 3.0, as well as sample data and code samples on the Web.

Buy Now!

List Price: $ 49.99
Price: $ 3.89

What is the best SharePoint Analytics tool?

Chosen Answer:

For comprehensive SharePoint Analytics, I recommend using CardioLog. Unlike Google Analytics, CardioLog will provide you with SharePoint specific stats for example reports for portal page views, navigation, growth, visitors, search and more.

Check out the CardioLog homepage-> http://www.intlock.com/

You can do a free 30 day full enterprise trial here -> http://www.intlock.com/intlocksite/Downloads/
by: Sharepoint Usage
on: 12th February 11