Persistence Store Changes on Beta 2.2?

Persistence Store Changes on Beta 2.2?

• Acumen

  Hi Sebastian,

  We have full migration notes from WF Beta 2 to WF Beta 2.2 and this is expected to be published early next week. Here is the migration note regarding the tracking database which you have encountered. The build number for WF Beta 2.2 is 3.0.3807.7. After installing WF B2.2 the location for the scripts is: C:\WINDOWS\WinFX\v3.0\Windows Workflow Foundation\SQL\EN.

  1.1 Changes to tracking SQL scripts and stored procedures

  Several stored procedures for the out-of-box durable tracking services have been updated. The related logic scripts have also been updated accordingly. Re-running the updated logic scripts will recreate the stored procedures.

  The following tracking stored procedures have been updated:

  • GetTypeId: Added a bit parameter @IsInstanceType to indicate whether the workflow type you want to retrieve is xoml-based or compiled
  • InsertWorkflow: Added a bit parameter @IsInstanceType to indicate whether the workflow type you want to insert is xoml-based or compiled
  • GetWorkflowInstanceInternalId: Changed the int parameter ContextId to uniqueidentifier ContextGuid
  • GetActivityInstanceId: Changed the int parameters ContextId, ParentContextId to uniqueidentifiers ContextGuid and ParentContextGuid respectively
  • InsertActivityExecutionStatusEvent: Changed the int parameters ContextId, ParentContextId, WorkflowInstanceContext to uniqueidentifiers ContextGuid and ParentContextGuid and WorkflowInstanceContextGuid respectively, added a ActivityExecutionStatusEventId as a big int output parameter
  • InsertWorkflowInstance: Changed the int parameters Context, CallerContext, CallerParentContext to uniqueidentifiers ContextGuid and CallerContextGuid and CallerParentContextGuid respectively
  • InsertUserEvent: Changed the int parameters Context, ParentContext to uniqueidentifiers ContextGuid and ParentContextGuid respectively, added a UserEventId as a big int output parameter
  • InsertTrackingDataItem: Removed EventOrder parameter and added a bigint EventId and a char(1) EventTypeId
  • InsertEventAnnotation: Removed EventOrder parameter and added a bigint EventId and a char(1) EventTypeId
  • Added Stored Proc: GetWorkflowChangeEventArgs

  1.1.1 Migration Notes

  Migration impact from the updates of the stored procedures should be minimal, since the stored procedures are called from the Windows Workflow Foundation runtime, and should not be called directly from host code.

  1.1.1.1 SQL/Schema

  The tracking stored procedures need to be updated as per above. It is recommended to re-run the logic scripts to re-create the stored procedures.

  1.1.1.2 Host and Services Migration and Code Changes

  If the host code calls the tracking stored procedures directly, calls to tracking stored procedures from the host code would need to be updated as per the list of changes above.

  Regards,
  Paul

  
  
  

• Arrgh

  Sorry I didn't mention that earlier. I am using the Feb CTP of WinFX and WWF Beta 2 - whichever one came out with the Feb CTPs. If there's something newer, I'm not going to wreck my whole installation of WinFX to poke around with it given how fragile that whole situation is to begin with :)

   I just checked. The version of the WWF that I'm using was released on 3/17/2006, and its only the 22nd - so I'm guessing I'm still on the newest drop :)

  
  
  

• H a t e m

  SW2005 wrote:

  Hi there Are there any changes to the Tracking/Persistence Store Scripts within Beta 2.2 I installed Beta 2.2 yesterday and now I get the following exception when creating a workflow instance: System.Data.SqlClient.SqlException was unhandled Message="Procedure or function InsertWorkflow has too many arguments specified." Source=".Net SqlClient Data Provider" ErrorCode=-2146232060 Class=16 LineNumber=0 Number=8144 Procedure="InsertWorkflow" Server="localhost\\SQLExpress" State=2 ... My Application is based on the Jan CTP. Could anyone tell me where to get updated scripts for creating the persistence/tracking store Thanks and regards Sebastian

  I found those scripts in C:\Windows\WinFx\v3.0\Windows Workflow Foundation\SQL\(language, e.g. EN)

  Make sure you run the 'schema' script before you run the 'logic' script. This directory contains the scripts for persistence as well as tracking.

  
  
  

• spgomathi

  Hi again

  I still have the same problem: It seems that the InsertWorkflow and InsertWorkflowInstance Stored Procs (and others I think) are not compatible with the WWF Runtime Components delivered within the VS Extensions for WWF Beta 2.2.

  My Tracking Store DB was created by using the sql scripts you can find at
  C:\Windows\WinFx\v3.0\Windows Workflow Foundation\SQL\EN

  I first executed both Schema Scripts and then the Logic scripts.

  My WWF Runtime Components were part of the VSEXFWWF Beta 2.2 as mentioned above - their Build Number is 3.0.3807.7 (taken from GAC).

  Could please anyone tell me where to get updated scripts for the Persistence/Tracking Service or help me finding out what I've done wrong !

  Thanks,
  Sebastian

  
  

• Pradnya

  Hi Kevin

  Since the installinstructions told me to uninstall the WinFX CTP February or older 'cause of incompatibilities between WWF Beta 2.2 and those CTP's I can't execute these scripts.
  Think I've got to install the Feb CTP to get the scripts.

  Are you using Beta 2.2 and if so: are you still using Jan/Feb CTP of WinFX

  Thanks and regards
  Sebastian

  
  

• Mike00000001

  Thanks!

  
  

• somebodynobody

  Hallo Paul

  Thanks for your answer! I was sure I took a look at C:\WINDOWS\WinFX\v3.0\Windows Workflow Foundation\SQL\EN before re-asking for those skripts - my fault.

  Works fine now...

  Thanks again,
  Sebastian

  
  
• Persistence Store Changes on Beta 2.2?