A fish out of water: How to fix Text annotations on Visio Stencils

A fish out of water: How to fix Text annotations on Visio Stencils

I don’t consider myself a master of Visio, although I use it a lot to make my solution diagrams or system architectures and have already been considered Visio MVP for a year for my contributions to this product. As you may know, I create several years ago a Microsoft Integration, Azure, BAPI, Office 365 and much more Stencils Pack for Visio that I maintain until today (the last update was 4 days ago). And one of the tops complain is about text annotations: be able as a standard behavior to add text annotation bellow the shapes rather than on top that is the default of most shapes present in this package.

Well, luckly there is, the only problem is that there are so many items to change in this collection that this will take some time to finish, nevertheless I already start to work on this and the first set is already fixed.

This blog and video will show you how to fix this issue and maybe you can join me and contribute on this GitHub project and help me speed up this process of fixing this issue.

Fix Text annotations on Visio Stencils

Click on the shape that you want and type something. if the text is on top of the shape follow this steps:

Fix Text annotations on Visio Stencils
  1. On the Home tab, in the Tools group, click the Text Block tool Text Block button.
  2. Drag and resize the text block and put it in the desired position, normally bellow the shape.
Fix Text annotations on Visio Stencils
  1. On the Home tab, in the Tools group, click the Pointer Tool Pointer button .

After you switch back to the Pointer Tool Pointer button, the text keeps the same position relative to the shape. If you use the Pointer Tool to drag the text, the shape will also move, even if the text is no longer on the shape.

Tip and tricks – Fix Text annotations on Visio Stencils (video)

The post A fish out of water: How to fix Text annotations on Visio Stencils appeared first on SANDRO PEREIRA BIZTALK BLOG.

Auckland Connected Systems User Group| June 30, 2020 | Logic Apps: Best practices, Tips and Tricks | Slides and Video Available

It was with great pleasure to speak for the first time Auckland Connected Systems User Group (New Zealand), unfortunately, do this COVID-19 pandemic, this was an online event, nevertheless, it was a great experience and something to repeat if they desire. I still plan to visit New Zealand in the future, and maybe it will be a face-to-face event.

From my part I have to say thanks, Will, Alessandro, Wagner, Mark, Mike, Coen, and Craig for inviting me, it was indeed a pleasure!

Today I’m happy to share with you the slides and the video of the session.

Logic Apps: Best practices, tips, and tricks

10 tips you should know for being more productive and building more reliable, effective Logic Apps. In this session, we will do a reflection to your existing Logic Apps processes and when thru a list of must-have best practices, tips, and tricks that will allow you to build more reliable and effective workflows. At the same time, these will allow you to be more productive and document your workflows from the beginning.

Video recording

ACSUG June 2020 – Azure Logic Apps: Best practices, tips and tricks

Slides

I hope you enjoy it!

The post Auckland Connected Systems User Group| June 30, 2020 | Logic Apps: Best practices, Tips and Tricks | Slides and Video Available appeared first on SANDRO PEREIRA BIZTALK BLOG.

Auckland Connected Systems User Group| June 30, 2020 | Logic Apps: Best practices, Tips and Tricks

Auckland Connected Systems User Group| June 30, 2020 | Logic Apps: Best practices, Tips and Tricks

A few months ago, my dear friend Wagner Silveira asked me if I was interested in giving a talk at the Auckland Connected Systems User Group since they were planning to start doing online events in the user group because of COVID-19 and they were planning to invited speakers from overseas, since now this was an online event, and that one of the first names that were dropped was mine.

I usually never say no to these invites, I love doing talks about topics I care and love, especially doing it locally in person, but in this case, and the way the invite was made, I couldn’t refuse… but be aware I still plan to visit New Zealand in the future!

Nevertheless, it will be a challenge. I need to be awake at 6 AM to deliver this session! I can’t say that this will be the first time I will deliver a session with a coffee cup in the hand because I still remember the first time I went to Norway, in the old days of the BizTalk Crew, and because of a problem in Oslo airport, my flight was forced to land in Sweden. So, I had to travel all night without sleeping to be in Stavanger at 9 AM to know that the schedule was changed, and I was delivering the first session! Since that day, I question myself if Tord Nordahl is my friend.

Logic Apps: Best practices, tips and tricks

I would like you to invite you to join us at the Auckland Connected Systems User Group meeting that will happen on June 30, 2020. This will be the first time I will be delivering a session in the user group but I hope it will be the first of many.

AbstractLogic Apps: Best practices, tips and tricks

Azure Logic Apps helps you build powerful integration solutions by automating your workflows without writing a single line of code. In this session, I will be highlighting 10 tips you should know for being more productive and building more reliable, effective Logic Apps. We will also do a reflection to your existing Logic Apps processes and will go through a list of must-have best practices, tips, and tricks that will allow you to build more reliable and effective workflows. At the same time, these will allow you to be more productive and document your workflows from the beginning

Join us and reserve your presence at the Auckland Connected Systems User Group meeting it is free!

The post Auckland Connected Systems User Group| June 30, 2020 | Logic Apps: Best practices, Tips and Tricks appeared first on SANDRO PEREIRA BIZTALK BLOG.

Logic Apps: Best practices, Tips, and Tricks video and slides are available at Integration Monday

Logic Apps: Best practices, Tips, and Tricks video and slides are available at Integration Monday

It was with great pleasure that I presented, last May, 25 another session in the Integration Monday series this time about Logic Apps: Best practices, Tips, and Tricks, this was my eleventh talk in this community in 4 years of existence. I can say that I am one of the most regular speakers at the Integration User Group only behind Michael Stephenson that has 13 talks.

Logic Apps: Best practices, tips, and tricks

Azure Logic Apps helps you build powerful integration solutions by automating your workflows without writing a single line of code. In this session, I will be highlighting 10 tips you should know for being more productive and building more reliable, effective Logic Apps. We will also do a reflection to your existing Logic Apps processes and will go through a list of must-have best practices, tips, and tricks that will allow you to build more reliable and effective workflows. At the same time, these will allow you to be more productive and document your workflows from the beginning.

I hope you enjoy and find it an interesting session. Also, I advise you to visit and view the history of sessions that have taken place every Monday in the Integration User Group – Integration Monday series.

My other talks at Integration Monday – Integration User Group

The post Logic Apps: Best practices, Tips, and Tricks video and slides are available at Integration Monday appeared first on SANDRO PEREIRA BIZTALK BLOG.

Virtual Global Azure 2020 | Lisbon | April 25, 2020 | Logic Apps: Best practices, Tips, and Tricks | Slides and Video

Virtual Global Azure 2020 | Lisbon | April 25, 2020 | Logic Apps: Best practices, Tips, and Tricks | Slides and Video

Due to the world COVID-19 pandemic, last Saturday, April 25, was held the first Virtual Global Azure Bootcamp, an event that normally happens in several cities across the world in simultaneous. The restrictions we are facing dictated that this year the format would have to be different. If, on one hand, the social aspect of the event was missing, on the other hand, it opened the door to a wider universe of people to be able to attend. Nevertheless, for me, this event was an amazing success and it was a great pleasure to be once again presenting on this event that I have a special affection for.

I think I’ve been present since the first edition of this event.

Today I’m happy to share with you the slides and the video of the session.

Logic Apps: Best practices, tips, and tricks

10 tips you should know for being more productive and building more reliable, effective Logic Apps. In this session, we will do a reflection to your existing Logic Apps processes and when thru a list of must-have best practices, tips, and tricks that will allow you to build more reliable and effective workflows. At the same time, these will allow you to be more productive and document your workflows from the beginning.

Video recording

Slides

I hope you enjoy it!

The post Virtual Global Azure 2020 | Lisbon | April 25, 2020 | Logic Apps: Best practices, Tips, and Tricks | Slides and Video appeared first on SANDRO PEREIRA BIZTALK BLOG.

Logic Apps: How to send a well-formatted HTML Email notification with Office 365 Outlook connector

Logic Apps: How to send a well-formatted HTML Email notification with Office 365 Outlook connector

Microsoft has been discontinuing some actions for some time or at least
running side by side different versions, don’t get me wrong. But they were never
extremely good at providing proper documentation, even in the old days that we
had software releases every two or three years, now imagine in this crazy fast
delivery world that we are leaving! What you see is:

  • A big gap between the documentation and the features that we have available or not properly documented in terms of how they work;
  • There is nothing that tells you what was change or how certain task that was possible to do in previous versions of action can now be done.
Microsoft Office 365 Outlook connector documentation

When I say that for the first time that Microsoft deprecated connection
actions, I mean actual remove from the list of actions on the Logic App design,
taking from the example the two connectors mention above you can’t see
the deprecated action on the Logic App designer anymore:

Office 365 Outlook connector action on Logic App designer
SQL Server Connector on Logic App designer

But don’t be alarmed, your existing logic apps that still use these
deprecated actions continue to work properly.

In this article, we will address the Office 365 Outlook connector and especially the Send an Email V2 action because Send an Email action is now deprecated. So the question here is:

How to send a well-formatted custom HTML Email using Send an Email V2 action available on the Office 365 Outlook connector?

I personally liked the Send
an Email
action because we were able to directly put HTML code on the body
property and define that the email body format would be HTML bt setting the
property Is HTML to true.

Office 365 Outlook connector Send an email action shape

Quite simple to use and
efficient.

However, Send an email (V2) action has totally different
behavior. First of all, it owns fewer properties:

  • Is HTM property was removed from this action;
Office 365 Outlook connector Send an email comparetion between versions

And a completely new look
and feel of the Body property as you see in the picture below:

  • With a powerful editor similar to what we have in our office tools (Word, Outlook, …)
Office 365 Outlook connector Send an email V2 action shape

That also means that we no longer have the possibility to directly insert HTML code into the body property of the message as we did earlier with the previous version. Well, we can write HTML code on the body of this action:

Office 365 Outlook connector Send an email V2 action shape

But the end result will not be what you expect:

Email result from the Office 365 Outlook connector Send an email V2 action

Unluckily Power Automate designer, we don’t have a Code View button (</>) on the Body property editor, I will be blogging about this feature soon on Serveless360 blog. So, who we are able to send a proper well-formatted HTML Email using Send an email V2 action?

The answer is: unfortunately, at least in my opinion, we need to build the HTML in an action beforehand in a composite action or in a variable. And then put the compose output or variable as the send mail body property, and the action will render correctly the output as an HTML.

To do that we need:

  • On
    the Logic App designer, add the next step by clicking the +New step
    button
  • On
    the Choose an action window, enter Variables and select the
    action Initialize variable
  • On
    the Variable action configuration:

    • On
      the Name property, type “EmailBody”
    • On
      the Type property, specify the type as “String”
    • On
      the Value property leave it blank
Initialize variable action on Logic App designer
  • On
    the Logic App designer, add the next step by clicking the +New step
    button
  • On
    the Choose an action window, enter Variables and select the
    action Set variable
  • On
    the Variable action configuration:

    • On
      the Name property, select “EmailBody” variable
    • On
      the Value property, type your custom HTML
Set variable action on Logic App designer

Note: you can take as example this fancy HTML Template that I created specifically for this article here: HTML Notification Template to use Logic App or Power Automate Outlook connector and not this basic HTML that you are seeing on the picture.

  • And then define directly on the Body editor (without switching to Code View) that the body will be the content of the variable we created earlier:
set body property variable on Office 365 Outlook connector Send an email V2 action

And you will see that you
will be receiving also a well-formatted HTML email on your mailbox:

Correct Email output from the Office 365 Outlook connector Send an email V2 action

Thanks Thiago Almeida for the help and credits to Pedro Rosa that helped me creating this HTML Template and most important to be compatible with Outlook because not all the stylesheets that we can apply aren’t compatible.

Hope this helps!

The post Logic Apps: How to send a well-formatted HTML Email notification with Office 365 Outlook connector appeared first on SANDRO PEREIRA BIZTALK BLOG.

BizTalk Server Tips and Tricks: Take control of your environment: Tracking Data

BizTalk Server Tips and Tricks: Take control of your environment: Tracking Data

Welcome back to another entry on my blog post series about “BizTalk Server Tips and Tricks” for developers, administrators or business users and I couldn’t resist on speaking about a topic that normally divides BizTalk developers and BizTalk administrators: Tracking Data!

Problem

Normally Developers have in their environments Full tracking Enabled, why? Because it’s easier to debug, troubleshoot, analyze or validate and see if everything is running well or simply, what is happening with their new applications.

The important question is: Do Developers remember to disable tracking before they put the resources in production?

No! And actually… they don’t care about that! Is not their task to do it or control it. And if you ask them, you should always have them enabled! Sometimes, to be fair, they don’t know the right configurations that should be applied to production.

This can be an annoying and time-consuming operation. It will be the same as asking developers to change their way of being, and for them to remember each time they export an application to disable the Tracking data properties can be a big challenge… or even impossible!

Solution (or possible solutions)

My advice is, if you are a BizTalk Administrator, let them be happy thinking they are annoying you and take back the control of your environment by yourself.

These tasks can be easily automated and configured by easily creating or using PowerShell.

You should disable all Tracking or enable just the important settings at the application level. You may lose 1 day developing these scripts, but then you do not need to worry anymore about it.

As an example, with this script: BizTalk DevOps: How to Disable Tracking Settings in BizTalk Server Environment, you can easily disable all tracking settings for all the artefacts (orchestrations, schemas, send ports, receive ports, pipelines) in your BizTalk Server Environment


# Disable tracking settings in orchestrations     
$Application.orchestrations |  
%{ $_.Tracking = [Microsoft.BizTalk.ExplorerOM.OrchestrationTrackingTypes]::None } 
 
# Disable tracking settings in Send ports        
$disablePortsTracking = New-Object Microsoft.BizTalk.ExplorerOM.TrackingTypes 
$Application.SendPorts |  
%{ $_.Tracking = $disablePortsTracking } 
 
# Disable tracking settings in Receive ports 
$Application.ReceivePorts |  
%{ $_.Tracking = $disablePortsTracking } 
 
# Disable tracking settings in pipelines         
$Application.Pipelines |  
%{ $_.Tracking = [Microsoft.BizTalk.ExplorerOM.PipelineTrackingTypes]::None } 
 
# Disable tracking settings in Schemas 
$Application.schemas |  
    ?{ $_ -ne $null } | 
    ?{ $_.type -eq "document" } | 
    %{ $_.AlwaysTrackAllProperties = $false }


This can easily be edited by you to disable only one application or you can configure the right tracking setting that you want for your applications and environment.

If you are working with BizTalk Server 2016…



In previous versions of BizTalk Server, tracking settings were automatically imported with the rest of the application bindings. However, if you are working with BizTalk Server 2016, you have a new feature that allows you to have a better control while importing your BizTalk Applications: Import Tracking Settings.
If you are importing an MSI file, on the “Application Settings” tab, you will have a checkbox “Import Tracking Settings” that allows you to say: I don’t want to import the tracking from DEV or another environment in which the MSI was generated from.
BizTalk Server Import MSI Not Importing racking Data
If you are importing a Binding file you will also have this same option:
BizTalk Server Import Bindings Not Importing racking Data
Of course, if you want to properly define the correct or minimum tracking settings of your application, you need to do it manually or, once again, using a PowerShell script to accomplish that.
Quick, simple and practical.
Stay tuned for new tips and tricks!
Author: Sandro Pereira

Sandro Pereira is an Azure MVP and works as an Integration consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. View all posts by Sandro Pereira


        
BizTalk Server Tips and Tricks: Automatically Generate Schemas from a DTD instance

BizTalk Server Tips and Tricks: Automatically Generate Schemas from a DTD instance

I recently published a new BizTalk Server Tips and Tricks article: “Automatically Generate Schemas from a Well-Formed XML instance” on my blog post series about “BizTalk Server Tips and Tricks” for developers, administrators or business users and I couldn’t resist on asking what about DTD?

Definition of DTD schemas

For who doesn’t know what DTD is, a DTD is a Document Type Definition that defines the structure and the legal elements and attributes of an XML document… So basically, it is the equivalent of what BizTalk Server uses to define how an XML document can be structured: XSD Schema. Nevertheless, there are many differences between DTD (Document Type Definition) and XSD (XML Schema Definition). In short, DTD provides less control on XML structure whereas XSD (XML schema) provides more control.

Some of you may wonder, who cares? No one uses DTD anymore, so why bother?

Yes, indeed DTD is not used very regularly nowadays, and it is very probable that you will never use it… unless… for example, you are working with RosettaNet or in the future, you will have the need to work with RosettaNet. Why? Because most of the RosettaNet Standards – PIP messages – are defined in the format of DTD format!

As I mentioned in my previous blog, there are several ways we can create an XML Schemas in BizTalk Server:

  • Manually from the scratch
  • From XDR Schema instance
  • From a DTD instance
  • From a well-formed XML instance
  • Import them from a WCF Service or Web Service
  • Or automatically generated them from LOB systems (from the adapters)

Generating schemas based on a DTD instance

Today we will be talking about automatically generating XML Schemas from a DTD instance.

To accomplish this we need to:

  • In Solution Explorer, right-click a BizTalk project, point to Add, and then click Add Generated Items…

01-BizTalk-Server-Generate-Schemas-from-DTD

  • In the Add Generated Items – <BizTalk ProjectName> dialog box, in the Templates section, click Generate Schemas, and then click Add

02-BizTalk-Server-Generate-Schemas-from-DTD

  • In the Generate Schemas dialog box, in the Document type drop-down list, select DTD

03-BizTalk-Server-Generate-Schemas-from-DTD

  • One of the problems, especially in brand new installations, is that sometimes this feature was not installed, and you will see DTD (Not Loaded) in the drop-down list. To install and use this feature you need to:
    • Navigate to the “SDKUtilitiesSchema Generator” folder present in the BizTalk Server installation folder. Normally this will be “C:Program Files (x86)Microsoft BizTalk Server <version>SDKUtilitiesSchema Generator”
    • And execute the InstallDTD.vbs script by double-clicking. This will install the “Microsoft.BizTalk.DTDToXSDGenerator.dll” DLL on the correct place. This basically means that it will copy this DLL to the “Developer ToolsSchema Editor Extensions” folder present in the BizTalk Server installation folder
    • Or manually “Microsoft.BizTalk.DTDToXSDGenerator.dll” DLL to the “Developer ToolsSchema Editor Extensions” folder present in the BizTalk Server installation folder. Normally this will be “C:Program Files (x86)Microsoft BizTalk Server <version>Developer ToolsSchema Editor Extensions
  • Close the Generate Schemas dialog box and do the previous steps again. Now you will be able to see that you can use the option DTD in the drop-down list

04-BizTalk-Server-Generate-Schemas-from-DTD

  • In the Generate Schemas dialog box, click Browse, locate the file you want to import, click Open and then click OK
  • A new schema, or sometimes at least two schemas are generated from the specified file, using the same name as that file with the .xsd extension, and opened in BizTalk Editor

Quick, simple and practical.

Stay tuned for new Tips and Tricks!

Author: Sandro Pereira

Sandro Pereira is an Azure MVP and works as an Integration consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. View all posts by Sandro Pereira

BizTalk Server Tips and Tricks: How to properly configure the connection string inside the Database Lookup functoid

BizTalk Server Tips and Tricks: How to properly configure the connection string inside the Database Lookup functoid

It’s fair to say that we all know the default Database Lookup functoid. It allows you to connect and extract information from a database. This functoid requires four input parameters in the following order:

  • A lookup value – value for which to search in the specified database, table, and column (next parameters);
  • A database connection string – The full connection string for the database with a provider, machine name, database and authentication (an ActiveX Data Objects .NET (ADO.NET) connection string);
  • A table name – name of the table in the database in which to search
  • A column name for the lookup value – name of the column in the table in which to search – the first parameter

The functoid is quite simple to use, however, the main problem that developers face when they use it, refers to the second parameter: the connection string.

How to know the correct value of the connection string to be set in the Database Lookup Functoid

Is hard to remember the correct syntax/value to specify in the connection string to be used inside the Database Lookup Functoid.

For you to be sure that you don’t make any mistakes, which could  lead to future waste of time by diagnosing and rectifying the connection string, the simple and easy way to guarantee that we are using the correct connection string value – but also for not having to remember this by head – is to:

  • Create a simple Universal Data Link (.udl) File
  • Set the OLE DB provider connection parameters
  • And finally, test the connection to check if everything is correct

To accomplish this, we need to:

  • Create a text file and name it “ODBCConnectionTest.udl” on your file system
    • Preferably on the BizTalk Server machine
    • The name of the file is not important, the important part is the extension, it must be “.udl”
  • Double-click the Universal Data Link file that you just created
  • On the Provider Tab, select the appropriate OLE DB provider for the type of data you want to access and then Next
    • In my case, it is “Microsoft OLE DB Provider for SQL Server”

Database Lookup functoid: Universal Data Link

  • In the Connection tab, specify:
    • The SQL Server instance that hosts the database
    • The authentication method: Use Windows NT integrated security or Use a specific user name and password
    • And finally, the database name to which you want to connect

Database Lookup functoid: Universal Data Link Connection

  • After specifying these properties, you then should click on “Test Connection…” button to attempt a connection to the specified data source. If no connection is made, review the settings. Otherwise, click “Ok”

Now that we have our Universal Data Link file created and properly configured, you can open the UDL file in Notepad and you will have access to the connection string value that you should use inside the Database Lookup Functoid. You just need to copy and paste it inside the second parameter of the Functoid.

Note: you should paste the connection string statically inside the Database Lookup Functoid but that is a different topic that we will address in another BizTalk Server Tips and Tricks.

I hope this small trick will the useful, enjoy and stay tuned for new BizTalk Server Tips and Tricks!

Author: Sandro Pereira

Sandro Pereira is an Azure MVP and works as an Integration consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. View all posts by Sandro Pereira

BizTalk Server Tips and Tricks: How to Backup (other) BizTalk Custom Databases

BizTalk Server Tips and Tricks: How to Backup (other) BizTalk Custom Databases

During my sessions about BizTalk Server Tips and Tricks, I normally ask: What RosettaNet, ESB or UDDI have in common? And the answer is: they all are BizTalk optional features that are not part of the primary installation process, you need to execute “secondary” installation processes to add theses features. These installation processes will create BizTalk custom databases for supporting all of these new optional features. But the big questions here are: do you think that these databases are being backed up? And if not, how to backup (other) BizTalk Custom Databases?

Do you think that these databases are being backed up?

To respond this first question, the answer is: No!

Because these BizTalk custom databases (we are calling “custom databases” because they are supporting optional features that are not part of the primary installation process) are not installed by default with BizTalk Server, they are not included in the default list of databases to be marked and backed up by the Backup BizTalk Server job. The default list of databases that are, normally, being backed up by the Backup BizTalk Server job are:

  • BAMAlertsApplication
  • BAMPrimaryImport
  • BizTalkDTADb
  • BizTalkMgmtDb
  • BizTalkMsgBoxDb
  • BizTalkRuleEngineDb
  • SSODB

How to Backup (other) BizTalk Custom Databases?

If you want the Backup BizTalk Server job to back up these additional BizTalk custom databases, you must manually add the databases to the Backup BizTalk Server job.

You can achieve this by:

  • Taking Windows Explorer and browse to the “Schema” directory on the BizTalk installation folder, normally:
    • C:Program Files (x86)Microsoft BizTalk Server <version>Schema
  • Run “Backup_Setup_All_Tables.sql” and next “Backup_Setup_All_Procs.sql” against all your BizTalk custom databases that you want to back up. This creates the necessary table, procedures,  roles and assigns permissions to the stored procedures.
  • After that you need need to modify the adm_OtherBackupDatabases table, in the BizTalk Management (BizTalkMgmtDb) database, to include a row for each of the new BizTalk custom databases
    • Type the new server and database names in the corresponding columns, as shown in the following tab
      • DefaultDatabaseName: The friendly name of your custom database.
      • DatabaseName: The name of your custom database.
      • ServerName: The name of the computer running SQL Server.
      • BTSServerName: The name of the BizTalk Server. This value is not used, but it must contain a value nonetheless.

To complete the process, you, mandatory, need to force Backup BizTalk Server (BizTalkMgmtDb) job to perform a full backup of the databases, otherwise you will receive the following error:

  • BACKUP LOG cannot be performed because there is no current database backup. [SQLSTATE 42000] (Error 4214) BACKUP LOG is terminating abnormally. [SQLSTATE 42000] (Error 3013)

To do that you need:

  • Execute the “sp_ForceFullBackup” stored procedure present in the BizTalkMgmtDb database.

The next time you run the Backup BizTalk Server job, it will back up all your BizTalk custom databases.

Note: I will not recommend you to add any of your application support custom databases to the Backup BizTalk Server job since they may interfere with the execution times of this job. If the Backup BizTalk Server job starts to take a long time to execute, it may also affect the overall performance of the BizTalk platform.

Stay tuned for new BizTalk Server Tips and Tricks!

Check out the first blog of the series BizTalk Server Tips and Tricks: Enabling BAM Add-In for Excel 2016.

Author: Sandro Pereira

Sandro Pereira is an Azure MVP and works as an Integration consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. View all posts by Sandro Pereira