Hi Lubomir,

The assembly is stored on the server after you run CREATE ASSEMBLY. For
access to it, use the SQL statement "select content from sys.assembly_files
where name = 'your_assembly_name_here' ". Once you run CREATE ASSEMBLY, you
do not need access to the original file. SQL Server will not use it.

You can move assemblies in a few different ways.

1. If you move the .DLL to the remote server, the SQL Server principal
executing CREATE ASSEMBLY must have windows access to the file.
2. Alternately, if you have the assembly already cataloged to a test system,
you can right-click on [your
database]/Programmability/Assemblies/[your_assembly] and select "Script
Assembly as" then "Create to" then "File". You now have a file that contains
the DDL to re-create the assembly on the production system. It catalogs the
assembly from the binary held in the 'content' field in sys.assembly_files.

Each way has its strengths and weaknesses. Moving the file means you need to
keep the location of the file and the DDL that run CREATE ASSEMBLY in sync.
Scripting the assembly is simpler (no assembly .DLL to keep track of), but
corrupting the binary (for example, by sending the Create Script in mail and
introducing a carriage return-line feed in the binary) is possible.

Hope this helps,
Bob Beauchemin
SQLskills