Flat files (text) are FTP'd to our Biztalk 2004 server. The data on the flat
 files is transformed and inserted into tables on a SQL Server database usin
g stored procedures.  The length of 2 string fields on the flat file has inc
reased and  I updated the d
atabase table defiintions and the stored procedures in SQLServer.    Now, on
ly part of the data on the flat file is actually inserted into the database 
tables.  Is there something that I need to change in BizTalk to make it work
?  It worked until I change
d the stored procedure and database tables.  I found a reference to the stor
ed procedure in SQLSERVICE.XSD.  Thanks in advance.

[ Post a follow-up to this message ]

And we will safely assume that you have altered your flat file schema to mat
ch your table definition......

"BTRookie" wrote:

> Flat files (text) are FTP'd to our Biztalk 2004 server. The data on the flat files
 is transformed and inserted into tables on a SQL Server database using stored proce
dures.  The length of 2 string fields on the flat file has increased and  I updated 
the
database table defiintions and the stored procedures in SQLServer.    Now, o
nly part of the data on the flat file is actually inserted into the database
 tables.  Is there something that I need to change in BizTalk to make it wor
k?  It worked until I chan
ged the stored procedure and database tables.  I found a reference to the st
ored procedure in SQLSERVICE.XSD.  Thanks in advance.

[ Post a follow-up to this message ]

Check your sqlservice.xsd schema and make sure there aren't maximum lengths
or other restrictions on the fields you are updating.  When you say you
updated the stored procedure, I assume you mean you change the parameters to
allow larger values?

Matt


"BTRookie" <BTRookie@discussions.microsoft.com> wrote in message
news:6C13F19F-FF7F-4C9C-8EAF-A81A5559034B@microsoft.com...
> Flat files (text) are FTP'd to our Biztalk 2004 server. The data on the
flat files is transformed and inserted into tables on a SQL Server database
using stored procedures.  The length of 2 string fields on the flat file has
increased and  I updated the database table defiintions and the stored
procedures in SQLServer.    Now, only part of the data on the flat file is
actually inserted into the database tables.  Is there something that I need
to change in BizTalk to make it work?  It worked until I changed the stored
procedure and database tables.  I found a reference to the stored procedure
in SQLSERVICE.XSD.  Thanks in advance.

[ Post a follow-up to this message ]

I checked sqlservice.xsd and there are no maximum
lengths.  The data type is xs:string.  The schema instance
path references the stored procedure that I mentioned.  I
did update the parameters on the stored procedure to allow
for larger values.  Any other ideas of things to check?
I am new to BizTalk.  Thanks in advance.
>-----Original Message-----
>Check your sqlservice.xsd schema and make sure there
aren't maximum lengths
>or other restrictions on the fields you are updating.
When you say you
>updated the stored procedure, I assume you mean you
change the parameters to
>allow larger values?
>
>Matt
>
>
>"BTRookie" <BTRookie@discussions.microsoft.com> wrote in
message
>news:6C13F19F-FF7F-4C9C-8EAF-A81A5559034B@microsoft.com... 
The data on the[vbcol=seagreen]
>flat files is transformed and inserted into tables on a
SQL Server database
>using stored procedures.  The length of 2 string fields
on the flat file has
>increased and  I updated the database table defiintions
and the stored
>procedures in SQLServer.    Now, only part of the data on
the flat file is
>actually inserted into the database tables.  Is there
something that I need
>to change in BizTalk to make it work?  It worked until I
changed the stored
>procedure and database tables.  I found a reference to
the stored procedure
>in SQLSERVICE.XSD.  Thanks in advance.
>
>
>.
>

[ Post a follow-up to this message ]

If you have checked all of your schemas (flat file and sql) and your stored
procedure and table configurations, then I'd say the best thing to do would
be to use the orchestration debugger to watch your files as they go through
the system and see where the truncation happens.  A better first step that
is easier might be to use SQL Profiler to trace the calls to your database
and make sure you know if they are truncated before or after they are sent
to SQL.  You can watch for statement completed events and filter on your
database id so you don't get too much information in the profiler.

matt


<anonymous@discussions.microsoft.com> wrote in message
news:750201c47656$7addae70$a401280a@phx.gbl...[vbcol=seagreen]
> I checked sqlservice.xsd and there are no maximum
> lengths.  The data type is xs:string.  The schema instance
> path references the stored procedure that I mentioned.  I
> did update the parameters on the stored procedure to allow
> for larger values.  Any other ideas of things to check?
> I am new to BizTalk.  Thanks in advance. 
> aren't maximum lengths 
> When you say you 
> change the parameters to 
> message 
> The data on the 
> SQL Server database 
> on the flat file has 
> and the stored 
> the flat file is 
> something that I need 
> changed the stored 
> the stored procedure 

[ Post a follow-up to this message ]