DTA Purge and Archive Job Failed

Yes! It does not work "by default" when you install fresh BizTalk Server
How to fix it ?!

Open properties of the job and select Steps

Select Archive and Purge the only step and click Edit
change the parameters of the procedure
@nLiveHours tinyint to 1
@nLiveDays tinyint to 0
@nHardDeleteDays tinyint to 0
@nvcFolder nvarchar(1024) to '\\MyServer\backup'
@nvcValidatingServer sysname to null
@fForceBackup int to 0

the edited command should look like
exec dtasp_BackupAndPurgeTrackingDatabase 1, 0, 1, 'c:\backup', null, 0

save it and try to run job one more time

Comments

Post a Comment

Popular posts from this blog

How to poll database using WCF-SQL adapter

Image
1. Create database and tables2. Create stored procedure 3. Create BizTalk project 4. Create orchestration 5. Consume WCF-SQL 6. Write received data to file share


First create TESTWCFSQL database from you SQL Management studio Run the script to create table:
USE TESTWCFSQL GO
IF OBJECT_ID('dbo.MainData', 'U') IS NOT NULL DROP TABLE dbo.MainData GO
CREATE TABLE dbo.MainData ( MainDataID int primary key identity(1,1), FirstName nvarchar(30), LastName nvarchar(30), Amount int ) GO

Run script in SQL management studio to create procedure
IF EXISTS ( SELECT * FROM INFORMATION_SCHEMA.ROUTINES WHERE SPECIFIC_SCHEMA = N'dbo' AND SPECIFIC_NAME = N'PollData' ) DROP PROCEDURE dbo.PollData GO
CREATE PROCEDURE dbo.PollData AS select MainDataID, FirstName, LastName, Amount from dbo.MainData delete from dbo.MainData GO
insert some sample lines executing
use TESTWCFSQL
insert into MainData (FirstName, LastName, Amount) values (N'Patrick', N'Cash', 1000), (N&#…
Read more

SQL query timeout from application but works fast from SSMS

Image
Recently faced very strange problem. Application which was working great during last two years just suddenly had timeout on one particular page. The page was always very fast and was showing just last 12 records from the table.

So I did what always was doing to check slow performing query, started SQL Profiler to trace the query. Query by itself is pretty complex and had a lot of parameters, Profiler is the best tool I think in that cases.

After I easily found long running query in Profiler I copy pasted it into SSMS and what a surprize query just run in 300ms. Meanwhile the query from UI (asp.net) was running almost 2 minutes.

The first to be different is session variables. To get info about sessions you can just select from the sys.dm_exec_sessions table.
more info about table https://docs.microsoft.com/en-us/sql/relational-databases/system-dynamic-management-views/sys-dm-exec-sessions-transact-sql

Easy way to compare between sessions:

SELECT
    session_id,
    [ansi_defaults],
    …
Read more