Prev: Function or insert/into temp table
Next: what is the boot record of the database file? & TDE
From: Plamen Ratchev on 22 Mar 2010 22:13
I am really not sure what you are trying to do. Are you comparing a single call to a stored procedure to multiple calls
via WCF? Also, what is the stored procedure doing, why do you reference loops?

The easiest way to find out is to test both approaches in your environment. I do not think anyone can provide clear
answer without seeing the code details and some test data.

--
Plamen Ratchev
http://www.SQLStudio.com
From: Tibor Karaszi on 23 Mar 2010 03:30
SQLCLR was introduced in 2005.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi



"RG" <nobody(a)nowhere.com> wrote in message
news:3A33EE78-9583-4CC3-B73A-2E3CEF46F338(a)microsoft.com...
> Stored Procedures written in c#, is that in sql 2005 or 2008?
>
> "Erland Sommarskog" <esquel(a)sommarskog.se> wrote in message
> news:Xns9D43F1749F720Yazorman(a)127.0.0.1...
>> RG (RG(a)discussions.microsoft.com) writes:
>>> Performancewise, is there a difference between your cursor loop/update
>>> stored procedure and c# program, residing where sql server is, that does
>>> the same?
>>
>> Not sure exactly what you have in mind, but I suppose the answer is
>> "it depends".
>>
>> Even if the C# program run on the SQL Server machine, there may be a lot
>> of data that will be passed between different processing. On the other
>> hand, if there is complex processing done to each row, this is likely to
>> run faster in C#.
>>
>> Yet an alternative is to do the processing in a stored procedure written
>> in C#. That is the same thing as the application, but inside SQL Server.
>> Again, whther this is a good idea or not, depends.
>>
>>
>> --
>> Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se
>>
>> Links for SQL Server Books Online:
>> SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
>> SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
>> SQL 2000:
>> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>>
>
From: RG on 23 Mar 2010 05:46
What would the downside in using sqlclr?

"Erland Sommarskog" <esquel(a)sommarskog.se> wrote in message
news:Xns9D43F1749F720Yazorman(a)127.0.0.1...
> RG (RG(a)discussions.microsoft.com) writes:
>> Performancewise, is there a difference between your cursor loop/update
>> stored procedure and c# program, residing where sql server is, that does
>> the same?
>
> Not sure exactly what you have in mind, but I suppose the answer is
> "it depends".
>
> Even if the C# program run on the SQL Server machine, there may be a lot
> of data that will be passed between different processing. On the other
> hand, if there is complex processing done to each row, this is likely to
> run faster in C#.
>
> Yet an alternative is to do the processing in a stored procedure written
> in C#. That is the same thing as the application, but inside SQL Server.
> Again, whther this is a good idea or not, depends.
>
>
> --
> Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se
>
> Links for SQL Server Books Online:
> SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
> SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
> SQL 2000:
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>

From: RG on 23 Mar 2010 10:47
what is the downside of using sqlcr?

"Erland Sommarskog" wrote:

> RG (RG(a)discussions.microsoft.com) writes:
> > Performancewise, is there a difference between your cursor loop/update
> > stored procedure and c# program, residing where sql server is, that does
> > the same?
>
> Not sure exactly what you have in mind, but I suppose the answer is
> "it depends".
>
> Even if the C# program run on the SQL Server machine, there may be a lot
> of data that will be passed between different processing. On the other
> hand, if there is complex processing done to each row, this is likely to
> run faster in C#.
>
> Yet an alternative is to do the processing in a stored procedure written
> in C#. That is the same thing as the application, but inside SQL Server.
> Again, whther this is a good idea or not, depends.
>
>
> --
> Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se
>
> Links for SQL Server Books Online:
> SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
> SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
> SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>
> .
>
From: Gert-Jan Strik on 23 Mar 2010 14:24
Does your DBA know all of your sqlclr programming languages? Does he
know any? If not, then support / knowledge management is definitely a
major issue.

--
Gert-Jan


RG wrote:
>
> What would the downside in using sqlclr?
>
> "Erland Sommarskog" <esquel(a)sommarskog.se> wrote in message
> news:Xns9D43F1749F720Yazorman(a)127.0.0.1...
> > RG (RG(a)discussions.microsoft.com) writes:
> >> Performancewise, is there a difference between your cursor loop/update
> >> stored procedure and c# program, residing where sql server is, that does
> >> the same?
> >
> > Not sure exactly what you have in mind, but I suppose the answer is
> > "it depends".
> >
> > Even if the C# program run on the SQL Server machine, there may be a lot
> > of data that will be passed between different processing. On the other
> > hand, if there is complex processing done to each row, this is likely to
> > run faster in C#.
> >
> > Yet an alternative is to do the processing in a stored procedure written
> > in C#. That is the same thing as the application, but inside SQL Server.
> > Again, whther this is a good idea or not, depends.
> >
> >
> > --
> > Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se
> >
> > Links for SQL Server Books Online:
> > SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
> > SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
> > SQL 2000:
> > http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
> >
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Function or insert/into temp table
Next: what is the boot record of the database file? & TDE