I think it doesn't really matter where you put the dll. What I mean is....
CREATE ASSEMBLY DistanceCalculations FROM 'C:\YourDLLName.dll'
When you create the assembly, you need to identify where the dll is. That statement, I believe, will take the binary code of the dll, and copy it to the database. So, once the assembly is created, you don't need the DLL anymore.
I'm not as familiar with this stuff as I would like to be, but a friend of mine told me that you can create the assembly in one database, detach it, attach it to another server, and the CLR will still be there. I haven't tested this for myself.
-George
"The great things about standards is that there are so many to choose from." - Fortune Cookie Wisdom
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.