SQL Query: Set All Dbs AutoGrowth



The following are recommendations to proactively manage the growth of data and log files:

When possible, increase all data files and log files to their expected final size, or periodically increase these at set periods, for example, every month or every six months, or before rollout of a new storage-intensive site such as during file migrations.

Enable database autogrowth as a protective measure to make sure that you do not run out of space in data and log files. Consider the following:


You must factor in the performance and operations issues associated with using autogrowth. For more information, see Considerations for the “autogrow” and “autoshrink” settings in SQL Server.

Default Settings

The default settings for a new database are to grow by 1 MB increments. Because this default setting for autogrowth results in an increases in the size of the database, do not rely on the default setting. Instead, use the guidance provided in Set SQL Server options.


Set autogrowth values to a fixed number of megabytes instead of to a percentage. The bigger the database, the bigger the growth increment should be.

NoteNote:  Use care when you set the autogrowth feature for SharePoint databases. If you set a database to autogrowth as a percentage, for example at a 10-percent (%) growth rate, a database that is 5 GB grows by 500MB every time that a data file has to be expanded. In this scenario, you could run out of disk space. or the db could be 100gb and growth would be 10gb every time the file needed space

Consider for example, a scenario where content is gradually increased, say at 100MB increments, and autogrowth is set at 10MB. Then suddenly a new document management site requires a very large amount of data storage, perhaps with initial size of 50 GB. For this large addition, growth at 500 MB increments is more appropriate than 10MB increments.

For a managed production system, consider autogrowth to be merely a contingency for unexpected growth. Do not use the autogrow option to manage your data and log growth on a day-to-day basis. Instead, set the autogrowth to allow for an approximate size in one year and then add a 20 percent margin for error. Also set an alert to notify you when the database runs low on space or approaches a maximum size.

Maintain a level of at least 25 percent available space across drives to accommodate growth and peak usage patterns. If you add drives to a RAID array or allocate more storage to manage, monitor capacity closely to avoid running out of space. Setting autogrowth to use MB verse %  along with changing the autogrowth MB size will create less fragmentation than using the defaults, this SQL Query makes it easier to modify a large number of Dbs.

-- Query to Set File AutoGrowth

    DB_NAME(mf.database_id) database_name,
    mf.name logical_name,
    CONVERT(DECIMAL(20, 2), (CONVERT(DECIMAL, size) / 128)) [file_size_MB],
    CASE mf.is_percent_growth
        WHEN 1 THEN 'Yes'
        ELSE 'No'
    END AS [is_percent_growth],
    CASE mf.is_percent_growth
        WHEN 1 THEN CONVERT(VARCHAR, mf.growth) + '%'
        WHEN 0 THEN CONVERT(VARCHAR, mf.growth / 128) + ' MB'
    END AS [growth_in_increment_of],
    CASE mf.is_percent_growth
        WHEN 1 THEN CONVERT(DECIMAL(20, 2), (((CONVERT(DECIMAL, size) * growth) / 100) * 8) / 1024)
        WHEN 0 THEN CONVERT(DECIMAL(20, 2), (CONVERT(DECIMAL, growth) / 128))
    END AS [next_auto_growth_size_MB],
    CASE mf.max_size
        WHEN 0 THEN 'No growth is allowed'
        WHEN -1 THEN 'File will grow until the disk is full'
        ELSE CONVERT(VARCHAR, mf.max_size)

    END AS [max_size],
FROM sys.master_files mf
ORDER BY database_name


Download: Set_AutoGrowth4AllDbs.sql



SharePoint 2013 Unable to Open Documents from Ribbon when WOPI is Configured and Library Default open behavior for browser-enabled documents is Open in the client application

It appears to be an IE issue when clicking on the New Document Drop down from the ribbon using fiddler4 there are not any results returned, probably jscript or jquery … I am running IE11 and I have tested IE10 which exhibits the same behavior. I haven’t tested on earlier versions yet.

However, if you open with Mozilla the Microsoft Office is blocked until you Allow Mozilla to open Office Documents and then Default open behavior for browser-enabled documents works as expected. In other words when the library is set to open ion the browser (via WOPI) the documents open in the browser, when set to open in the client application, the docs open in the client as expected..

1. Click On Allow



2. Then choose to Allow remember


3. Then choose OK,



4. Click on New Document one more time to open from the ribbon



Note: this only occurs if you have WAC installed and configured WOPI with SharePoint. Also, you only have to go to library settings to set the Default open behavior for browser-enabled documents: to Open in the client application, you don’t have to set the site collection… I will resolve as time permits




Embed a PowerPoint Presentation into a SharePoint 2013 Page with Multiple Farms

It seems like everyone NothingButSharePoint and Microsoft Office and Microsoft Bogs states that you can not embed unless your using Office 365 (this may have been due to using SharePoint 2010). There are many more post and articles that require you to use Onedrive.. There are probably many better ways to sharing Content using WAC with multiple farms and SharePoint On-Prem and I would enjoy hearing about how you have solved this issue

Embed a PowerPoint Presentation from a source SharePoint Farm and render the presentation in a target SharePoint Farm using CEWP


1. Go to http://focalpoint.cotoso.com and search for PPTX

2. Use the Drop Down, Choose embedded information, and Copy All

3. Go to http://learning.fabricam.com

5. Add Content Editor WebPart


6. Click Inside the WebPart Choose the Orange Insert, Click Embed Code


7. Insert (Paste CTRL+V) the Code you copied from http://focalpoint.contoso.com


8. Then Click the Insert button,

9. Next Edit the WebPart, and change the Width to 540px, then click OK


10. Click Check-in, then Publish this Draft


Note: The Site Collection Feature – Cross-Farm Site Permissions is activated on both Farms, the cross-farm site permissions feature to allow internal SharePoint applications to access websites across farms.



Metalogix Content Matrix PowerShell Copy Jobs “Failed to Find the main assembly”

If you have upgraded from a previous version of Metalogic Content Matrix SharePoint edition or have multiple Content Matrix editions (SharePoint, Fileshare, Blog) deployed you may receive the error “Failed to find the main application assembly” when attempting to run any of your PowerShell Copy Job Scripts. If you are not running the Metalogix copy jobs in PowerShell you will not be affected by this issue.



The resolution that worked for me was to uninstall Metalogix Content Matrix Consoles, Content Organizer and the Content Matrix WSPs. Open a command prompt in admin mode and run Gacutil /lr > E:\Apps\gacutil.txt to pipe the contents of the GAC to a txt file to review. In one environment I found two assemblies were not being removed Metalogix.System.Commands.dll and Metalogix.SharePoint.Adapters.StoragePoint.dll. The setup uses Installutil and was unable uninstall the two assemblies listed previously.

From the open command prompt run the followingimage

  • gacutil /u Metalogix.System.Commands.dll
  • gacutil /u Metalogix.SharePoint.Adapters.StoragePoint.dll

substitute any assemblies you found for the ones I used as necessary


Download gacutil as part of the Microsoft Windows SDK for Windows 7 http://www.microsoft.com/en-us/download/details.aspx?id=8279. I spoke with Bill Wilcock the Western Regional Support Manager for Metalogix and “Metalogix has determined it is definitely the GAC assemblies and the issue should be resolved in the next hotfix release coming out in a week or two.” 

As I mentioned above, If you are not running the Metalogix copy jobs in PowerShell you will not be affected by this issue. But if your not running the copy jobs in PowerShell you should be; the jobs run at least 2x faster and you can set up a schedule in Task Scheduler to run your incremental jobs daily. This means that when its time to cut over,its very anticlimactic as the site admins, department admins, and end users have verified their content has been successfully migrated, they have time to get used to the new look and feel, and started using the new features prior to Go Live.





Blog: http://blogs.msmvps.com/ivansanders/

clip_image001[4] clip_image002[4] clip_image003[4] clip_image004[4] clip_image005[4] clip_image006


See you in Helsinki March 14th for SharePoint Saturday

SharePoint 2013 Migrations, Are you having fun yet??

Wow what an incredible couple years SharePoint 2013 is still rockin on premise and online

Time Consuming Steps

However, there were two time consuming steps that didn’t have anything to do with the mechanics of the migration or the technology like moving WebParts, Pages, Items, Documents and creating Site Collections from Sites in Additional Content DBs.

  1. 1.The conversion of the Binary File Format documents to the OpenXML File Format.
  2. 2.Teaching folks why managed metadata is important and the creation of a Global Taxonomy, that includes Navigation

Luckily, there were two sources of information that made this easier but still not painless Waldeks Post – Building Global Navigation in SharePoint 2013 http://blog.mastykarz.nl/building-global-navigation-sharepoint-2013/ (it works) and the WAND Library. Unfortunately, though I have access to the Library the client did not choose to purchase the subscription so we didn’t get to take advantage of the huge library of terms.

WAND has started offering its entire catalog of taxonomies from the cloud, where you have the ability to subscribe monthly and download the parts that your Client needs to either start their taxonomy or fill out their taxonomy.  I have just been through a relatively easy migration 8 Content Dbs and a small 1TB of Content.

Missing Tools for In-Flight Conversion of Site Columns

The largest notable part missing, though metalogix will help you modify Multi-Choice Site Columns to Managed Metadata Site Columns In-Flight, there are NOT ANY migration products that will convert your binary File Format documents to the OpenXML File Format.

The Microsoft tools like Office Migration Planner will not work with a mapped drive using WebDav, but you can still use PowerShell though we found it was actually better to use a staging Farm, Convert all of your Documents using Word Automation Service. then perform a final migration where we modify the columns In-Flight to take advantage of the managed Metadata Site Columns.

This is important, if you want to take advantage of changing the Multi-Choice Site Columns to managed Metadata Site Columns In-Flight. Because if you have not converted all of your RTFs, HTMs, DOCs to DOCX then you will lose the metadata associated with these documents.

I’m not sure why metavis, sharegate, metalogix, tsunami or others do not build document conversion into their products since we need to be moving off the Binary format for many reasons and embracing the OpenXML Format




clip_image002 clip_image004 clip_image006 clip_image007 clip_image009 clip_image010

SharePoint 2013 NOTICE: Microsoft Deactivated SP1 Download

UPDATE: 04-22-2014 Reference: Stefan Goßner

The updated version of Service Pack 1 has been released today!

Refer to the information below to acquire the updated Service Pack for your product:

NOTE The KB articles for the re-released Service Pack is different from the recalled Service Pack.

  • KB 2880551 – SharePoint Foundation 2013 SP1
  • KB 2880552 – SharePoint Server 2013 SP1
  • KB 2880553 – Project Server 2013 SP1
  • KB 2880554 – SharePoint Server Language Pack
  • KB 2880555 – SharePoint Foundation Language Pack
  • KB 2880558 – Office Web Apps Server 2013 SP1

Download links for updated SP1:

Customers with Service Pack 1 Deployed

For customers who have previously deployed Service Pack 1, download the updated Service Pack 1 and install over the existing Service Pack 1 running PSConfig or PSConfigUI immediately following.

Customers without Service Pack 1

For customers without Service Pack 1 deployed, download the updated Service Pack 1 package and deploy as per the KB documentation.


There is no update to the integrated ISO ("slipstream") from MSDN, VLSC and MPN as it was not affected by the issue.

Reference: see official announcement in Bill Baers blog post.


“Notice: We have recently uncovered an issue with this Service Pack 1 package that may prevent customers who have Service Pack 1 from deploying future public or cumulative updates. As a precautionary measure, we have deactivated the download page until a new package is published.” http://support.microsoft.com/kb/2817429


“Notice:We have recently uncovered an issue with this Service Pack 1 package that may prevent customers who have Service Pack 1 from deploying future public or cumulative updates. As a precautionary measure, we have deactivated the download page until a new package is published.

A known issue in SharePoint Foundation 2013 SP1 can affect the functionality of the Search WebPart. We encourage you to limit production installations of SharePoint Foundation 2013 SP1 until a fix is available. SharePoint Server 2013 is not affected by this issue.” http://support.microsoft.com/kb/2817439

I would like to thank Andy Williams the Nikon TAM (Microsoft Technical Account Manager), for bringing this to our attention Thursday. Unfortunately, we are affected since we have deployed SP1 to All DEV and PRD Servers. The only good news (I guess) is that our topology consists of Standalone farms for both WAC and WFM.

You may want to also check out Todd’s post http://bit.ly/OjfHAk as he states that Bill Baer has said that the ISO downloaded from MSDN does not have this issue.




Technorati Tags: SharePoint 2013 SP1,Removed

clip_image001 clip_image002 clip_image003 clip_image004 clip_image006 clip_image008

Stay Competive with Business Intelligence in SharePoint 2013 & O’Reilly

book cover

Stay Competitive

O’Reilly Media spreads the knowledge of innovators through its books, online services, magazines, research, and conferences. Get the information you need from the experts you trust; visit oreilly.com to purchase this book.

Business Intelligence in Microsoft SharePoint 2013

Get 40% off of the print book and 50% off of the ebook version of this book by entering discount code AUTHD.

By Norman P. Warren, Mariano Teixeira Neto, Stacia Misner, Ivan Sanders, Scott A. Helmers

May 2013, ISBN 978-0-7356-7543-8

406 pages, $34.99


© 2014 O’Reilly Media, Inc. O’Reilly logo is a registered trademark of O’Reilly Media

clip_image001 clip_image002 clip_image003 clip_image004 clip_image006 clip_image008


metalogix content matrix resolves errors

I recently posted on my disappointment of metalogix due to the continual system crashes. The crashes have been resolved and occurred in version There were numerous errors removing version

However, all issues have been resolved in version and greater.

metalogix version ROCKS!! Thanks to the folks at metalogix for working with me to get the issues resolved

Creating Managed Metadata Fields in Flight

After resolving the issues I wanted to check out the inflight creation of Managed Metdata Field migrated from SP2007 MultiChoice Field in flight. The new Managed metadata Field was created along with the term set based on the old SP2007 MultiChoice Field.

Screenshot Metalogix Creating the Terms in flight


However, there is an issue that is not handled in Flight if you have any .DOC files (the old Binary format Office Documents) you will lose all of your, metadata.

The workaround for this issue is to first bring over the libraries as they are. Once they are in SharePoint 2013, you can run the following PowerShell Script if you have configured Word Automation Services to Convert the old binary format to the Open File Format DOCX ,

Then create the Managed metadata field and term set use content matrix

$wasp = Get-SPServiceApplicationProxy | where { $_.TypeName -eq "Word Automation Services Proxy" }
$job = New-Object Microsoft.Office.Word.Server.Conversions.ConversionJob($wasp)
 $web = Get-SPWeb http://intranet.contoso.com/
 $inputFolder = $web.GetFolder("Shared Documents")
 $outputFolder = $web.GetFolder("Shared Documents")
 $job.UserToken = $web.CurrentUser.UserToken
 $job.Name = "Convert Docs to Docxs"
 $job.Settings.OutputFormat = [Microsoft.Office.Word.Server.Conversions.SaveFormat]::Document
 $job.Settings.OutputSaveBehavior = [Microsoft.Office.Word.Server.Conversions.SaveBehavior]::AlwaysOverwrite
 $job.AddFolder($inputFolder, $outputFolder, $false)
 $status = New-Object Microsoft.Office.Word.Server.Conversions.ConversionJobStatus($serviceAppProxy.Id, $job.JobId, $null)
 $timerJob = Get-SPTimerJob "Word Automation Services"
 Write-Host $timerJob

.csharpcode, .csharpcode pre
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
background-color: #f4f4f4;
width: 100%;
margin: 0em;
.csharpcode .lnum { color: #606060; }

ScreenShot of SharePoint 2013 Technical Library using Managed Metadata Columns











ScreenShot SharePoint 2007 Content Type using the Choice Column type







Acceleratio SharePoint Documentation Toolkit 3.3

Upgrade to new and improved version!

We have released updated Documentation Toolkit for SharePoint version 3.3 which brings a lot of new stuff:

Checkmark Manually perform Data Retention in case your database reaches critical size.
Checkmark Improved performance of permissions load when working with large AD groups.
Checkmark Best Practices now support Foxit PDF iFilter.
NEW product in the family:
Governance Toolkit for Office 365

Decided to move to cloud? Use Governance Toolkit for Office 365 to gain complete control over your Office 365 environment and check if Office 365 runs according to the governance rules you specified!

Editions and Pricing

Upgrade to v3.3!

Existing customers should navigate to Customers Portal to download new version of SPDocKit.

Still don’t have a license?

Buy Now

Sales and Support

Governance Toolkit Office365

Download 30 days free trial and try all great features that our new product brings.

Download free trial

Pricing starts from $149!
Governance Toolkit for Office 365 is licensed per tenant and number of users. Check pricing page to find Edition that best suits your needs and budget.

Sales and Support

Sales & Support

Feel free to contact us for any question you might have.
Download free trial
1000+ Customers and growing

1000+ Customers and growing

TSL logo Toll Free: US 855 855-5071 – International: +1 (631) 406-4900

E-mail: sales@acceleratio.netwww.acceleratio.net

© 2013. Acceleratio Ltd.

Follow us on Twitter Twitter
Follow us on Facebook Facebook
Follow us on Google + Google+

For those of you who remember Vyapin Software Another of my favorite tools for providing as built documentation to clients…


Happy Holidays

Using Yammer & SharePoint Intranets to Drive Employee Engagement

Using Yammer & SharePoint Intranets
to Drive Employee Engagement 

WEBINAR: Wednesday, December 4, 2013 – 1:00-2:00PM CT

Register Button

Microsoft has gone social in a big way with Yammer – but are yammer you ready for it? A successful social solution must give end users the foundational tools needed to effectively collaborate with coworkers, clients and partners while maintaining control of access, security and content. Each business has a different sweet spot when it comes to creating an engaging social environment that drives collaboration and meaningful dialogue. An enterprise social network’s success is dependent on unearthing your employees’ key motivational drivers, aligning the solution to your company’s culture, your vision for leveraging cloud-based solutions, and tailoring a strategy to fit.

In this session, we will be taking a look at what planning for Yammer success really entails, and the importance of a social maturity assessment, community use case planning and a communication plan. We’ll also discuss the value of a Yammer pilot, or SharePoint social on premises where appropriate.

Presenter Rich Wood is Director of Perficient’s national Microsoft Web & Social Collaboration practice and has been planning, designing and building enterprise solutions for intranets, extranets, and public internet sites since 1997. A veteran of both the SharePoint partner community and Microsoft itself, Rich has deep experience in information architecture, user experience, social collaboration, and enterprise architecture and technology strategy.


View past Perficient webinar slide shows and replays

facebook twitter rss_feed

Perficient, Inc. is a leading information technology consulting firm providing business-driven technology solutions to Global 2000 and other large enterprise clients throughout North America. www.Perficient.com



Technorati Tags: Yammer,Webinar,Perficient

Next Page »