At microsoft’s recomendations we changed the code to update BOTH the fields for an MMS field as shown below :-

batchElement.InnerXml = “<Method ID=’1′ Cmd=’Update’>”

+ “<Field Name=’ID’>3</Field>”

+ “<Field Name=’Title’>Modified through lists.asmx web service 1</Field>”

+ “<Field Name=’Country’>3;#Germany</Field>”

+ “<Field Name=’Continent’>2</Field>”

+ “<Field Name=’ContinentTaxHTField0′>0;#Northamerica|d511f3c7-377f-480f-aff6-beebecd3c675</Field>”

+ “</Method>”;

I also found that the pointer “<Field Name=’Continent’>2</Field>” could be set to 0 if the term was not already in the hidden list. ie “<Field Name=’Continent’>0</Field>”

SQL Server Agent and proxy accounts.

Conspicuous by its absence is the Transact-SQL script (T-SQL) subsystem. T-SQL jobsteps always run in the security context of the job owner, and there’s no override in SSMS to change that. You can manually configure the job step, using the sp_add_jobstep system stored procedure, passing the database_user_name parameter to impersonate a database user for a jobstep, but of course you’ll need security rights to impersonate a database user to do so.

In order for a proxy account to work correctly, the account must have the “Log on as a batch job” (seBatchLogonRight) assigned to it by a Windows administrator (for example, in the Local Security Policy MMC snap-in, under Local Policies -> User Rights Assignment). Without that privilege the SQL Server Agent service will not be able to impersonate the account to run the job step. Also it is important to note that proxy accounts do not automatically have access to your SQL Server. If, for example, you want to use a CmdExec or PowerShell job step to log back in to SQL Server, the proxy account must explicitly be granted a login back to your SQL Server (or otherwise inherit access from a Windows group, etc.).

http://blogs.msdn.com/b/uksharepoint/archive/2009/12/18/configuring-business-connectivity-services-bcs-search-in-sharepoint-2010.aspx

http://blogs.msdn.com/b/sharepointdev/archive/2011/07/26/rapid-application-development-using-infopath-and-bcs-part-2-anweshi-deverasetty.aspx

http://blogs.msdn.com/b/sharepointdev/archive/2011/07/28/rapid-application-development-using-infopath-and-bcs-part-3-anweshi-deverasetty.aspx

Create the XML for a BDC model.

http://msdn.microsoft.com/en-us/library/ee559278.aspx

BDC XML snippets to use when editing a file.

http://msdn.microsoft.com/en-us/library/gg607166.aspx#AdvancedAssociationsInBCS_ImplicitForeignKey

ALTER AdventureWorks database and edit the Exported XML for the model to create an association without a declarative FK.

http://msdn.microsoft.com/en-us/library/ee558413(office.14).aspx

Business Connectivity Services Schema Reference

Save as Template and then edit to obtain a feature.

1. Install the AdventureWorks Sample DW BI Database

First, you need to install the AdventureWorks Sample DW BI database.  You can download it from CodePlex.

I downloaded the full version for 2008 with the msi installer, which is nice because it installs the database and attaches it for you. Running the installation is pretty straight-forward, but if you have any trouble, you can refer to an earlier post on my blog here.

2. Install the Office SharePoint Server 2007 SDK (1.3)

Download and install the Office SharePoint Server 2007 SDK.  I’m working against the 1.3 version of the SDK.  The SDK contains a BDC application definition that were created for the SQL Server 2005 AdventureWorksDW  database.

NOTE can download the SharePointPlatformSDK.exe for 2010.

Chart of objects and permissions and effect of permission.

http://msdn.microsoft.com/en-us/library/ie/hh144965.aspx

MSDN on permissions.

Install client addin.

http://msdn.microsoft.com/en-us/library/ee210708.aspx

PowerPivot for SharePoint.

Create a store procedure in your DW database (datawarehouse).

Code Snippet

Execute it with your parameters (span of dates that your data lies between or greater. Or, put two dates for span directly into stored procedure as parameters’ defaults in case you prefer that way (I made defaults for year 2008).