community-content

Forum Replies Created

Viewing 15 posts - 4,336 through 4,350 (of 9,648 total)
  • Author
    Posts
  • in reply to: SQL Adaptor question #20000

     HI,

     

        I am having the same issue as posted origanally. I have a simple query in SP “Select Cols from Table XML AUTO,XMLDATA”. I create schema and deploy the project succesfully. But problem occurs when i try to create a receive location for SAL adapter. It thorws message of “Invalid schema” for every schema generated within the project. I am wondering what could be the problem?

    Thank you in advance.

    Many thanks for the quick replies and inputs.

    I agree, MSMQ need not be there and I am considering WCF or even a simple FTP based process.

    Coming to SSIS I have mixed opinions about its performance for doing Data Loads and ETL kind of stuff. I got feedback that SSIS is very slow.

    One of the Reasons for using BizTalk is there will be various other External Systems(like ERP, CRM, other CSV feeds) which will have to communicate in a similar way to upload data. Hence I have proposed a EAI/Middleware system rather than a SSIS kind if solution.

    Also as the other technologies in the Portal application area around Microsoft .NET I thought BizTalk will be a good Fit as an EAI tool which can do the Data Upload now and also help them Integrate will other external entities later in the Road.

    LINQ is pretty much new and I have not explored it much but certainly will consider before I go forward with BizTalk.
    Any further inputs on LINQ which can sole my kind of problem is appreciated.

    Very much appreciate your Inputs and thanks once again.

    Nagin.

     

     

     I agree.  SSIS is stronger than BizTalk for high volume ETL.  It is a very powerful tool when it comes to bulk loading data to and from database tables and flat files.  However, BizTalk is better for working with different data formats and for transforming data.  Also, BizTalk is better for continuous, event-driven integration.  SSIS does not really support event-driven integration.  You can do continuous integration with SSIS, but you need to schedule a package to run frequently. 

    Since we are considering different platforms here, I would consider WCF/WF/LINQ.  I tend to lean toward this type of solution over SSIS or BizTalk to build data driven applications.  Complex insert/update logic can become cumbersome in BizTalk, especially if you are making multiple database roundtrips.  Also, the BizTalk SQL adapter has been known to deadlock under high transaction volumes.  I like to use BizTalk as a tool to integrate applications rather than a tool to write applications.  That said, you might want to encapsulate the database insert/update logic behind a WCF service, and front the service with BizTalk in an ESB style deployment.

    Also, do you really need to use MSMQ?  I believe it has a low message size limit ( somewhere in the < 5Mb range).  You can accept the XML through a load balanced WCF service over http or tcp and still get high availability, probably better performance, and no size limit.

    Hope this helps!

    This might be heresy on this forum, but Biztalk might not be the best solution to this problem.
    Biztalk is not really designed for high volume ETL processes, you might be better using SQL Integration Services, SSIS.

     

    in reply to: Replacing the Biztalk SQL nodes #19994

    Never done an in-place SQL Server swap before, but  it should work. Are the new servers going to be exact copies of the originals, OS, SQL Server – same service packs, and hotfixes?

    Be sure to turn off the Biztalk Servers (either power down or stop the host instances and IIS), and SQL Agent before you backup the databases.

    The last time I moved Biztalk SQL databases, we installed a new server with a new name/IP. Stopped Biztalk, IIS  and SQL agent, backed up the databases, copied and restored on new server and ran the 2 scripts in C:\Program Files\Microsoft BizTalk Server 2006\Schema\Restore http://technet.microsoft.com/en-us/library/aa559835.aspx
    In your case you shouldn’t need to jump thru these hoops.

     

    in reply to: FTP connection failure #19989

     All I can think of is using an external service to monitor Suspended messages and then taking action.

    http://martijnh.blogspot.com/2004/07/biztalk-2004-suspended-queue-listener.html

    in reply to: Using SQL Adapter in Orchestration #19988

     Here are some things to check:

    • Did you restart the host instance?
    • In the BizTalk Server administation console, open the orchestration properties and view the bindings.  Does the stored procedure send port show up?  If not, then the latest version is not deployed.
    • Is the stored proc SQL send port 1 way or 2 way?  If it is 1 way, you can easily change the adapter to FILE as a test to see if BizTalk delivers a file to the port.
    • Add trace statements to your orchestration around the stored proc send port and watch them in DebugView when the orch executes. (http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx)
    in reply to: BAM GUI, a GUI for bm.exe #19986

    Great idea!

    I had to run it from my C drive. When I initially tired to run from a network share, it crashed.  Copied it to C: and now it runs.

    Update:

    Works beautifully. The GUI concept makes the understanding for the commands a bit more intuitive.

     

     You need to put the entire Xml as a string into the 4th parameter.

    There are two ways I have found of doing this.
    1. In an orchestration:

    xmlDocVariable = inputMessage;
    SQLMessage.FourthParameter = xmlDocVariable.OuterXml; (assumes FourthParameter is a distinguished field)
    or
    xpath(SQLMessage, “4th parameter xpath”) = xmlDocVariable.OuterXml;

    2. In map – requires custom code

    in reply to: FTP connection failure #19982

     Hi Greg,

     

    I really thank for your replies. Please tell me if i can do anything out of box to solve this issue in BTS 2004. This is critical issue in our app.

     

    Thanks and Regards

     

    Vijaykishan S

    in reply to: FTP connection failure #19981

    On the dynamic Send port under Transport Advanced Options in Biztalk Admin Console you can set “Enable routing on failed messages” 

    Failed messages are changed to Error messages and published to the Messagebox. You can subscribe to these messages and take what action you require.

    in reply to: FTP connection failure #19980

    In BTS 2006 how will catch the ftp connection error when it is configured dynamically. Please shed some light to overcome this issue.

    in reply to: Dynamic Send Ports – Naming #19979

     I have searched for a way to do this and been unable to find anyway of doing it.

    What I tend to do is to create a dynamic send port (with a sensible name) within a binding file which is added as a resource and imported when the msi is imported. Then have a post processing script that deletes the verbose send port

    in reply to: FTP connection failure #19978

    Not sure there is much you can do with Biztalk 2004.

    With Biztalk 2006 you would have the option of enabling routing on failed messages to handle this issue.

Viewing 15 posts - 4,336 through 4,350 (of 9,648 total)