Here is what someone posted back from the SQL 2005 newsgroup,
SQL Server only allows referencing a list of supported framework assemblies
like system.dll, system.data.dll etc. (complete information in SQL Server
Books Online). These are the assemblies you can add reference to by default
in your Visual Studio SQL Server projects. You would see them in SQL Server
tab when you click add reference.
Apart from these, all other assemblies that you wish to reference in your VS
SQL Server project must be registered in the database you have specified for
your project. You can do this using the CREATE ASSEMBLY statement from SQL
Server Management Studio.
Once you register an assembly in the database, it would show up in the SQL
Server tab in add references.
Microsoft SQL Server
"Andy" <[email protected]> wrote in message
> Yes I am familar with how web services work, but just to keep the web
> servers clean the idea was to have the .Net 1.1 apps call to the SQL box
> for the API's that were wrapped as a web service. Since I have not been
> able to get SQL to register and assembly that I can expose as a UDF, which
> then could be exposed as an endpoint, we for now are resorting to
> installing IIS that will be the webservice. I really don't want to have to
> register the assembly in the GAC, but that seems like another way to get
> things done.
> We are trying to get our prototype up and going before the .Net 2.0 is
> release as gold code. We have a limited number of develop boxes, so we
> don't want to install beta software everywhere that may cause a complete
> rebuild when gold code is available. Once the gold code is available, then
> the web servers will have the NS API installed and they will make the
> calls that way. Our system will be physically separated, so the idea was
> to just have a WS on the NS box which is remote. Otherwise the API is
> making a remote call over firewalls etc, so we would probably be better
> served to use WS.
> This is all more than you really were looking for, but just thought I
> would lay it on the line. I guess we should pose some of this discussion
> to our TAP channels.
> "kate" <[email protected]> wrote in message
> news:[email protected]
>> >From our experience and what Shyam is saying you certainly dont need
>> IIS on the SQL box. If you create a webservice round the API elements
>> that you want and install that on your webserver, you can then call
>> than from the SQL 2005 assembly via a SOAP call without any need for
>> the NS or IIS elements to be present on the SQL box. This is how the
>> Reporting Services SOAP interface works and is very effective.
>> We have implented a similar strategy for SQL2000 and that works very
>> well with no need for the SQL box to have even heard of NS.
>> Kate MBCS
>> Alert Technologies
>> Get your notification services implementation going in minutes not
>> weeks ......