In WCF, web services can be hosted in many processes other than IIS. Can I
write my CLR extension (web service) to the SQL Express? SQL Server
Enterprise edition supports native web service, but it requires IIS.
Thanks.
HaoHello Hao,
> Can I
> write my CLR extension (web service) to the SQL Express?
If you mean, "can I write an CLR-based function or procedure and host that
in an instance of SQL Express?" then the answer is yes.
If you mean, "can I create an HTTP endpoint in an SQL Express instance?"
then the answer is no. You'll get error 7878 for your efforts.
> SQL Server
> Enterprise edition supports native web service, but it requires IIS.
Um, no, that's the point of HTTP endpoints.
Thanks!
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/|||There are two challenges for deploying a full SQL edition as providing web
services.
1. Customers have to buy full SQL.
2. IIS is required.
Please correct me if the above two requirements are wrong.
Therefore it seems that the only work around is to write my own windows
service in WCF to expose web services and have this windows service talk to
SQL Express. Am I on the right track?
Thanks.
Hao
"Kent Tegels" <ktegels@.develop.com> wrote in message
news:18f2bcb184248c93ffc0278bcf5@.news.microsoft.com...
> Hello Hao,
>
> If you mean, "can I write an CLR-based function or procedure and host that
> in an instance of SQL Express?" then the answer is yes.
> If you mean, "can I create an HTTP endpoint in an SQL Express instance?"
> then the answer is no. You'll get error 7878 for your efforts.
>
> Um, no, that's the point of HTTP endpoints.
> Thanks!
> Kent Tegels
> DevelopMentor
> http://staff.develop.com/ktegels/
>|||> There are two challenges for deploying a full SQL edition as providing
> web services.
> 1. Customers have to buy full SQL.
Define full SQL. HTTP endpoints are availble in the fairly cheap workgroup
SKU and higher.
> 2. IIS is required.
HTTP Endpoints DO NOT require IIS on XP, Server 2003 or higher.
> Therefore it seems that the only work around is to write my own windows
service in WCF to expose web services and have this windows service talk
to SQL Express. Am I on the right track?
If you want to use SQLExpress then the basic answer is yes.
Alternatively, you could use Mono to develop an ASMX service and deploy what
ever
HTTP stack you like.
Thanks!
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/
Showing posts with label processes. Show all posts
Showing posts with label processes. Show all posts
Thursday, March 29, 2012
Can I host the web service in SQL Express?
In WCF, web services can be hosted in many processes other than IIS. Can I
write my CLR extension (web service) to the SQL Express? SQL Server
Enterprise edition supports native web service, but it requires IIS.
Thanks.
Hao
Hello Hao,
> Can I
> write my CLR extension (web service) to the SQL Express?
If you mean, "can I write an CLR-based function or procedure and host that
in an instance of SQL Express?" then the answer is yes.
If you mean, "can I create an HTTP endpoint in an SQL Express instance?"
then the answer is no. You'll get error 7878 for your efforts.
> SQL Server
> Enterprise edition supports native web service, but it requires IIS.
Um, no, that's the point of HTTP endpoints.
Thanks!
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/
|||There are two challenges for deploying a full SQL edition as providing web
services.
1. Customers have to buy full SQL.
2. IIS is required.
Please correct me if the above two requirements are wrong.
Therefore it seems that the only work around is to write my own windows
service in WCF to expose web services and have this windows service talk to
SQL Express. Am I on the right track?
Thanks.
Hao
"Kent Tegels" <ktegels@.develop.com> wrote in message
news:18f2bcb184248c93ffc0278bcf5@.news.microsoft.co m...
> Hello Hao,
>
> If you mean, "can I write an CLR-based function or procedure and host that
> in an instance of SQL Express?" then the answer is yes.
> If you mean, "can I create an HTTP endpoint in an SQL Express instance?"
> then the answer is no. You'll get error 7878 for your efforts.
>
> Um, no, that's the point of HTTP endpoints.
> Thanks!
> Kent Tegels
> DevelopMentor
> http://staff.develop.com/ktegels/
>
|||> There are two challenges for deploying a full SQL edition as providing
> web services.
> 1. Customers have to buy full SQL.
Define full SQL. HTTP endpoints are availble in the fairly cheap workgroup
SKU and higher.
> 2. IIS is required.
HTTP Endpoints DO NOT require IIS on XP, Server 2003 or higher.
> Therefore it seems that the only work around is to write my own windows
service in WCF to expose web services and have this windows service talk
to SQL Express. Am I on the right track?
If you want to use SQLExpress then the basic answer is yes.
Alternatively, you could use Mono to develop an ASMX service and deploy whatever
HTTP stack you like.
Thanks!
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/
write my CLR extension (web service) to the SQL Express? SQL Server
Enterprise edition supports native web service, but it requires IIS.
Thanks.
Hao
Hello Hao,
> Can I
> write my CLR extension (web service) to the SQL Express?
If you mean, "can I write an CLR-based function or procedure and host that
in an instance of SQL Express?" then the answer is yes.
If you mean, "can I create an HTTP endpoint in an SQL Express instance?"
then the answer is no. You'll get error 7878 for your efforts.
> SQL Server
> Enterprise edition supports native web service, but it requires IIS.
Um, no, that's the point of HTTP endpoints.
Thanks!
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/
|||There are two challenges for deploying a full SQL edition as providing web
services.
1. Customers have to buy full SQL.
2. IIS is required.
Please correct me if the above two requirements are wrong.
Therefore it seems that the only work around is to write my own windows
service in WCF to expose web services and have this windows service talk to
SQL Express. Am I on the right track?
Thanks.
Hao
"Kent Tegels" <ktegels@.develop.com> wrote in message
news:18f2bcb184248c93ffc0278bcf5@.news.microsoft.co m...
> Hello Hao,
>
> If you mean, "can I write an CLR-based function or procedure and host that
> in an instance of SQL Express?" then the answer is yes.
> If you mean, "can I create an HTTP endpoint in an SQL Express instance?"
> then the answer is no. You'll get error 7878 for your efforts.
>
> Um, no, that's the point of HTTP endpoints.
> Thanks!
> Kent Tegels
> DevelopMentor
> http://staff.develop.com/ktegels/
>
|||> There are two challenges for deploying a full SQL edition as providing
> web services.
> 1. Customers have to buy full SQL.
Define full SQL. HTTP endpoints are availble in the fairly cheap workgroup
SKU and higher.
> 2. IIS is required.
HTTP Endpoints DO NOT require IIS on XP, Server 2003 or higher.
> Therefore it seems that the only work around is to write my own windows
service in WCF to expose web services and have this windows service talk
to SQL Express. Am I on the right track?
If you want to use SQLExpress then the basic answer is yes.
Alternatively, you could use Mono to develop an ASMX service and deploy whatever
HTTP stack you like.
Thanks!
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/
Wednesday, March 7, 2012
Can BCP Handle Leap Day: 2/29/08 ?
I have a production job that is killing BCP... If I change the dates to
2/28/08, the file processes just fine. Here is the error message ... is
this a known issue? Is there a fix for this?
#@. Row 11366, Column 2: Invalid date format @.#
1/21/08 2/29/08 1 0073210002300 0 3.68 12
#@. Row 24909, Column 2: Invalid date format @.#
1/21/08 2/29/08 4 0073210002300 0 3.68 12
#@. Row 38452, Column 2: Invalid date format @.#
1/21/08 2/29/08 7 0073210002300 0 3.68 12
#@. Row 51995, Column 2: Invalid date format @.#
1/21/08 2/29/08 14 0073210002300 0 3.68 12
#@. Row 65538, Column 2: Invalid date format @.#
Thanks!
Greg,
I am sure that bcp is simply using the SQL Server engine, so I would expect
it to 'know'. When I tested the following file all rows worked.
2/29/08
2/28/08
2/29/2008
2/28/2008
If the date was invalid, you would get the message that you show. I get the
errorw when I include a row with:
2/30/2008
So, one possibility is that your format file (or the format of your file) is
the problem. Are you using a format file or are you depending on tabs and
column order? (The latter is fine when it works, of course, but sometimes
you need a format file to control things more. See:
http://support.microsoft.com/kb/67409 and look "format files" in the SQL
Server Book Online for some examples.)
RLF
"greg may" <gregory_may [at] yahoo [dot] com> wrote in message
news:%233wz4JyvHHA.736@.TK2MSFTNGP06.phx.gbl...
>I have a production job that is killing BCP... If I change the dates to
>2/28/08, the file processes just fine. Here is the error message ... is
>this a known issue? Is there a fix for this?
> #@. Row 11366, Column 2: Invalid date format @.#
> 1/21/08 2/29/08 1 0073210002300 0 3.68 12
> #@. Row 24909, Column 2: Invalid date format @.#
> 1/21/08 2/29/08 4 0073210002300 0 3.68 12
> #@. Row 38452, Column 2: Invalid date format @.#
> 1/21/08 2/29/08 7 0073210002300 0 3.68 12
> #@. Row 51995, Column 2: Invalid date format @.#
> 1/21/08 2/29/08 14 0073210002300 0 3.68 12
> #@. Row 65538, Column 2: Invalid date format @.#
>
>
> Thanks!
>
|||Thanks Russell for your feedback. I will have to set up some more tests to
track this down further.
We are not using a format file in this case. Its using an implicid
conversion as the table structure and the field lay outs are an exact match
(Using Pipe delimiters) ... this may be part of what is causing the issue?
In this case, the destination table is using a SmallDateTime.
I will see if I can reproduce the problem with only the above conditions.
g.
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:uUKHnIzvHHA.4244@.TK2MSFTNGP04.phx.gbl...
> Greg,
> I am sure that bcp is simply using the SQL Server engine, so I would
> expect it to 'know'. When I tested the following file all rows worked.
> 2/29/08
> 2/28/08
> 2/29/2008
> 2/28/2008
> If the date was invalid, you would get the message that you show. I get
> the errorw when I include a row with:
> 2/30/2008
> So, one possibility is that your format file (or the format of your file)
> is the problem. Are you using a format file or are you depending on tabs
> and column order? (The latter is fine when it works, of course, but
> sometimes you need a format file to control things more. See:
> http://support.microsoft.com/kb/67409 and look "format files" in the SQL
> Server Book Online for some examples.)
> RLF
> "greg may" <gregory_may [at] yahoo [dot] com> wrote in message
> news:%233wz4JyvHHA.736@.TK2MSFTNGP06.phx.gbl...
>
2/28/08, the file processes just fine. Here is the error message ... is
this a known issue? Is there a fix for this?
#@. Row 11366, Column 2: Invalid date format @.#
1/21/08 2/29/08 1 0073210002300 0 3.68 12
#@. Row 24909, Column 2: Invalid date format @.#
1/21/08 2/29/08 4 0073210002300 0 3.68 12
#@. Row 38452, Column 2: Invalid date format @.#
1/21/08 2/29/08 7 0073210002300 0 3.68 12
#@. Row 51995, Column 2: Invalid date format @.#
1/21/08 2/29/08 14 0073210002300 0 3.68 12
#@. Row 65538, Column 2: Invalid date format @.#
Thanks!
Greg,
I am sure that bcp is simply using the SQL Server engine, so I would expect
it to 'know'. When I tested the following file all rows worked.
2/29/08
2/28/08
2/29/2008
2/28/2008
If the date was invalid, you would get the message that you show. I get the
errorw when I include a row with:
2/30/2008
So, one possibility is that your format file (or the format of your file) is
the problem. Are you using a format file or are you depending on tabs and
column order? (The latter is fine when it works, of course, but sometimes
you need a format file to control things more. See:
http://support.microsoft.com/kb/67409 and look "format files" in the SQL
Server Book Online for some examples.)
RLF
"greg may" <gregory_may [at] yahoo [dot] com> wrote in message
news:%233wz4JyvHHA.736@.TK2MSFTNGP06.phx.gbl...
>I have a production job that is killing BCP... If I change the dates to
>2/28/08, the file processes just fine. Here is the error message ... is
>this a known issue? Is there a fix for this?
> #@. Row 11366, Column 2: Invalid date format @.#
> 1/21/08 2/29/08 1 0073210002300 0 3.68 12
> #@. Row 24909, Column 2: Invalid date format @.#
> 1/21/08 2/29/08 4 0073210002300 0 3.68 12
> #@. Row 38452, Column 2: Invalid date format @.#
> 1/21/08 2/29/08 7 0073210002300 0 3.68 12
> #@. Row 51995, Column 2: Invalid date format @.#
> 1/21/08 2/29/08 14 0073210002300 0 3.68 12
> #@. Row 65538, Column 2: Invalid date format @.#
>
>
> Thanks!
>
|||Thanks Russell for your feedback. I will have to set up some more tests to
track this down further.
We are not using a format file in this case. Its using an implicid
conversion as the table structure and the field lay outs are an exact match
(Using Pipe delimiters) ... this may be part of what is causing the issue?
In this case, the destination table is using a SmallDateTime.
I will see if I can reproduce the problem with only the above conditions.
g.
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:uUKHnIzvHHA.4244@.TK2MSFTNGP04.phx.gbl...
> Greg,
> I am sure that bcp is simply using the SQL Server engine, so I would
> expect it to 'know'. When I tested the following file all rows worked.
> 2/29/08
> 2/28/08
> 2/29/2008
> 2/28/2008
> If the date was invalid, you would get the message that you show. I get
> the errorw when I include a row with:
> 2/30/2008
> So, one possibility is that your format file (or the format of your file)
> is the problem. Are you using a format file or are you depending on tabs
> and column order? (The latter is fine when it works, of course, but
> sometimes you need a format file to control things more. See:
> http://support.microsoft.com/kb/67409 and look "format files" in the SQL
> Server Book Online for some examples.)
> RLF
> "greg may" <gregory_may [at] yahoo [dot] com> wrote in message
> news:%233wz4JyvHHA.736@.TK2MSFTNGP06.phx.gbl...
>
Subscribe to:
Posts (Atom)