|SQL Server and Table partitionning|
Have you ever had a table that kep growing, while the performaces kept degrading, the first nice idea would be to define indexes, fair enough, but as the table continues to grow so does the indexes, and still the indexes might not be sufficient. So what do you do? buy a more powerful server?
Well this is an extreme solution, before just try to partition your huge table (well what is huge? above 10Gb is already huge in my case)
Partitionning is equivalent to create as many smaller objects as your partition boundaries
Hits: 14173 | Lire la suite...
|SAP BizTalk Adapter|
I am trying to configure Microsoft SAP Adapter 2.0.
I created send and receive ports as for documentation, RFC programs
I have to generate Idoc XSD from SAP Adapter.
The Microsoft SAP Adapter V2 works with the SAP .NET Connector V1.0.3.
If you have V2 of the .NET Connector then you get the error you have seen. Try removing the V2 .NET connector and replacing with 1.0.3.The results you get seem to vary with the installations that have beeninstalled. Some folks report success with the .NET Connector V2
Hits: 10297 | Lire la suite...
|Routing Failed Messages|
I'm trying to use enable routing for failed messages, I specify my send port with a filter on the existence of a failure code (everything is ok till here, the failed messages are correctly routed)
Then I add a filter on errors that come specifically from a receive port. And here nothing, the message is not routed and this acts as if no routing existed, when I see the context of the failed message the receive port is a promoted property !
If you look closely at your suspended Error Message (The non-resumable instance), you will see that the regular ReceivePortName (BTS.) is marked "Not Promoted", whereas the ErrorReport.ReceivePortName is. So you need to change your subscription to:
Hits: 16505 | Lire la suite...
|Validating FlatFile Schema (Positional) Date & space characters|
Some weeks ago I was faced with a problem, as entry, I had a flatfile schema with positional fields. Before processing this file I needed to validate that every field is ok.
I had a problem with dates, since if I received let's say 10 space characters (representing and empty date) then the schema was not valid. So how the hell could we have resolved the problem? How could we say to BizTalk that for space characters on the Date it is ok, and it should go forward?
Here we needed BizTalk Server to stop processing any wrong file, we did not want BizTalk to continue any further.
Every solution must be on the schema, solutions in other parts of BizTalk (mapping, custom pipeline, orchestration, ...etc.) was not a state of the art solution.
So What I did was simple :
These two actions were enough and solved my problem
Hits: 18800 | Lire la suite...