Re: Yukon SQLCLR questions

From: Mike Epprecht \(SQL MVP\) (mike_at_epprecht.net)
Date: 07/20/04


Date: Tue, 20 Jul 2004 17:44:21 +0200

As we are talking about beta products, and is solely based on information
that is publicly available, things may be different by the time Yukon ships.

Answers Inline.

-- 
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Suresh" <Suresh@discussions.microsoft.com> wrote in message
news:67A3EEAE-5944-4EC0-B2B5-DD1B3D32D453@microsoft.com...
> Hi,
> I was going through some teched presentations on SQLCLR and i was really
excited. But i have a few questions regarding them and i hope this forum can
answer my queries.
>
> 1) Does the SQL server share the CLR with the other applications that run
on the machine or does it have a dedicated CLR?
Yes, dedicated instance of the CLR. See point 3.
> 2) How to get back the .dll file that gets into the database when we
deploy it?
The deployment is intedned to be a one way copy. You need to store you
origianl code in some form of source control.
> 3) Can two different versions of CLR run on the same machine? one for
other applications and one for Yukon? In that case what happens to GAC?
.NET CLR is truly side by side. You can have a v1.0, 1.1, 2.0, x.x on the
box and the binary file and CLR can determine which CLR the binary is
compatible with (1.0 and 1.1 are compatible, whilest 2.0 will not run a 1.0
and 1.1 binary). SQL will get shipped with verion 2.0 of the CLR and it will
always use that, even if e.g. a 2.1 is installed. Yukon does not use the GAC
at all for it's CLR operations.
> 4) How can we apply CLR policies from out side Yukon? Are there any config
files like machine.config available?
No. SQL has interfaces to help it control the CLR for it's operations and
there may be a few tweaks that you make be able to configure.
> 5) Limitations of static access modifier? Since all the manaegd methods
have to be public static, does it have any restrictions?
There is a long list of restrictions that Visual Studio 2005 will enforce
when you create a CLR object, and it gets verified again when it gets
imported into SQL. The list is changing based on security and perfoprmence
requirmenets so you will have to wait till Beta 2 for the lst.
> 6) Can someone tell me how i can calling a stored procedure and get back
the return value which is returned via SqlPipe from outside SQL? can someone
point me to some sample code that calls a stored proc from outside?
Not tried that yet.
>
> Thanks in Advance.
>
>  - Suresh


Relevant Pages

  • Re: Spatial data
    ... indexing schemes etc. for an CLR UDF. ... "Liam" wrote in message ... I don't suppose you know if the Yukon SQL Server ...
    (microsoft.public.sqlserver.server)
  • Re: D8 may be 32 bit only
    ... applications move to Win64 in the WOW64 sandbox, ... Given that scenario it means that the CLR _IS_ ... I suspected that the the Delphi IDE might run as a 32-bit app on WoW64, ... As for Yukon, the 64bit Yukon will use the native 64bit CLR for managed ...
    (borland.public.delphi.non-technical)
  • Re: Break thread sleep
    ... CLR", and calls out specifically SQL Server "Yukon". ... admonishments I've seen about not generally assuming that a managed ...
    (microsoft.public.dotnet.languages.csharp)
  • Yukon SQLCLR questions
    ... Does the SQL server share the CLR with the other applications that run on the machine or does it have a dedicated CLR? ... How can we apply CLR policies from out side Yukon? ... Limitations of static access modifier? ... Can someone tell me how i can calling a stored procedure and get back the return value which is returned via SqlPipe from outside SQL? ...
    (microsoft.public.sqlserver.server)
  • Re: Performance is slow when calling web services in SQL CLR
    ... I have done async before, but not with sql clr sp. ... We have SQL CLR stored procedures that call web services. ...
    (microsoft.public.sqlserver.programming)