|
Home > Archive > BizTalk Server > April 2007 > BTS2006 SQL Adapter Wizard unable to see CLR Stored Procs
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
BTS2006 SQL Adapter Wizard unable to see CLR Stored Procs
|
|
|
| It appears the BizTalk SQL Adapter Wizard is unable to See CLR Stored Procs
(SQL 2005) - Anyone found a remedy for this? Hotfix perhaps?
Thx,
Coz
| |
| Saravana Kumar 2007-04-26, 1:14 pm |
|
It looks like there is a restriction on the SQL Adapter to use CLR
procedures.
There is a blog post about this issue at
http://www.caffedharma.com/tech/arc...ral/000211.html
As suggested in that blog, why don't you write a wrapper stored
procedure(regular), which in turn will call the CLR procedure.
Then you can configure your SQL adapter to call the wrapper procedure
instead of calling CLR procedure directly.
--
Regards,
Saravana Kumar
http://www.biztalk247.com/v1/
http://www.digitaldeposit.net/blog
[Please mark the response as "Answer" if it solves your problem.]
"Coz" wrote:
> It appears the BizTalk SQL Adapter Wizard is unable to See CLR Stored Procs
> (SQL 2005) - Anyone found a remedy for this? Hotfix perhaps?
>
> Thx,
> Coz
>
| |
|
| Thanks for your message...
I had seen the seen the blog you mentioned and considered the solution
mentioned, but I was hoping Microsoft is aware of the limitation and working
on a Hot Fix. Another problem is that of bringing back a record set into
BizTalk that contains a column of the XML data type in addition to other
fields.
Oh well...
Thanks,
Coz
"Saravana Kumar" wrote:
[vbcol=seagreen]
>
> It looks like there is a restriction on the SQL Adapter to use CLR
> procedures.
>
> There is a blog post about this issue at
> http://www.caffedharma.com/tech/arc...ral/000211.html
>
> As suggested in that blog, why don't you write a wrapper stored
> procedure(regular), which in turn will call the CLR procedure.
>
> Then you can configure your SQL adapter to call the wrapper procedure
> instead of calling CLR procedure directly.
>
> --
> Regards,
> Saravana Kumar
> http://www.biztalk247.com/v1/
> http://www.digitaldeposit.net/blog
> [Please mark the response as "Answer" if it solves your problem.]
>
>
> "Coz" wrote:
>
|
|
|
|
|