Powershell: Create the BDC Service Application for SharePoint 2013

02 Jan 2013
January 2, 2013

Here a small script to provision the Business Data Connectivity Service Application-without ugly GUID in the database name.

Its basically an extended version of my Provision Search Service Application script, just a little cleaned-up. During the creation (some would say copy & paste) I wondered why the proxy is created automatically – at first I had two proxies.


Pictures or it did not happen!


Business Data Connectivity Database with a beautiful name (and you can see my Managed Metadata Service Database is still ugly)


SP2013 BDC Service Application

Provisioned BDC Service Application


Questions / Issues ?

If I missed a thing or if you have questions – go for it!

Max Melcher
Follow me!

Max Melcher

Maximilian Melcher (MCSE, MCPD) is a Principal Consultant working at Alegri International Services in Munich, Germany. Max is a specialist in SharePoint technologies focused on search, social computing, web content management and collaboration. Max has led SharePoint implementations for Dax 30 companies since 2009.
Max’s free time is spent on twitter (@maxmelcher) mostly with a good coffee in his hands.
Max Melcher
Follow me!
Tags: , , ,
5 replies
  1. Kevin says:

    Hey Max, just a note to say this was awesome and worked great for me!

  2. Jake Jacobsen says:

    Thanks for the post, Max. Curious about creating the BCS Proxy through powershell. I don’t see it in your script, but tried this command:
    “New-SPBusinessDataCatalogServiceApplicationProxy -Name $proxy -ServiceApplication $serviceAppName”

    …and got this error:
    Cannot bind parameter ‘ServiceApplication’. Cannot convert value “Business Conne
    ctivity Services Application” to type “Microsoft.SharePoint.PowerShell.SPService
    ApplicationPipeBind”. Error: “Guid should contain 32 digits with 4 dashes (xxxxx

    It appears the command requires the ServiceApplication GUID, rather than the Name.

    • Jake Jacobsen says:

      Figured this out…. The “New-SPBusinessDataCatalogServiceApplication” command returns the SPServiceApplicationPipeBind after it’s created. I just needed to use that and pass it to the new BCS Proxy command. Like this ($serviceApp)…

      $serviceApp = New-SPBusinessDataCatalogServiceApplication -Name $serviceAppName -ApplicationPool $appPool -DatabaseName $dbName -DatabaseServer $dbServer

      $serviceAppProxy = New-SPBusinessDataCatalogServiceApplicationProxy -Name $proxy -ServiceApplication $serviceApp

      Thanks again, Max.


Trackbacks & Pingbacks

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.