CLR integration & clustering....question

If I've got a small CLR procedure that I'm now using thanks to 2005,
and I'm running on a failover cluster....do I need to have the DLL
available on both nodes of the cluster at the same path? So when I
fail over, the SQL Assembly knows where to go find it?"Corey Bunch" <unc27932@.yahoo.com> wrote in message
news:1137791687.994902.215830@.f14g2000cwb.googlegroups.com...
> If I've got a small CLR procedure that I'm now using thanks to 2005,
> and I'm running on a failover cluster....do I need to have the DLL
> available on both nodes of the cluster at the same path? So when I
> fail over, the SQL Assembly knows where to go find it?
>
CLR Assemblies are stored in the databse, not the filesystem.
So they are shared by both nodes.
David|||I see - so once you load them using Create Assembly, their put in a
system table somewhere and loaded & accessed from there & not the
filesystem?|||"Corey Bunch" <unc27932@.yahoo.com> wrote in message
news:1137792522.275215.162630@.g14g2000cwa.googlegroups.com...
>I see - so once you load them using Create Assembly, their put in a
> system table somewhere and loaded & accessed from there & not the
> filesystem?
>
Correct. Also this keeps assemblies in different databses from stepping on
each other.
David|||You can see them in the sys.assemblies catalog view (and the actual content
in binary format in the content column of sys.assembly_files). For a list of
the functions/procedures etc they export you can have a look at
sys.assembly_modules
--
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Corey Bunch" <unc27932@.yahoo.com> wrote in message
news:1137792522.275215.162630@.g14g2000cwa.googlegroups.com...
>I see - so once you load them using Create Assembly, their put in a
> system table somewhere and loaded & accessed from there & not the
> filesystem?
>|||Thanks - this is great info...
Jasper Smith wrote:
> You can see them in the sys.assemblies catalog view (and the actual content
> in binary format in the content column of sys.assembly_files). For a list of
> the functions/procedures etc they export you can have a look at
> sys.assembly_modules
> --
> HTH,
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
>
> "Corey Bunch" <unc27932@.yahoo.com> wrote in message
> news:1137792522.275215.162630@.g14g2000cwa.googlegroups.com...
> >I see - so once you load them using Create Assembly, their put in a
> > system table somewhere and loaded & accessed from there & not the
> > filesystem?
> >