> If you're trying to build a server-side crypto solution in SQL 2000 you
> can't use .NET (SQL 2000 can't host .NET CLR without causing major
> problems). It would have to be in native C/C++ using the CryptoAPI and
> the extended stored proc API:
> http://www.sqlservercentral.com/articles/Security/sql2000dbatoolkitpart1/2361/
You can run .NET server-side on a server with SQL Server 2000 installed. You
can't host it within SQL Server of course but you can still use the
database.

Signature
David Portas
Mike C# - 08 Mar 2008 02:17 GMT
>> If you're trying to build a server-side crypto solution in SQL 2000 you
>> can't use .NET (SQL 2000 can't host .NET CLR without causing major
[quoted text clipped - 5 lines]
> You can't host it within SQL Server of course but you can still use the
> database.
Yes, I was just pointing out that you can't use the .NET solution inside SQL
2000. If you wanted to build a layer that sits between the client
application and SQL Server that uses .NET to encrypt your data, that's
always possible. When I mentioned building a "server-side crypto solution"
I was talking about encryption tools that run inside SQL Server, not ones
that logically sit between the client and server and run external to both.
After all, if the OP is looking for a middleware encryption solution there's
always file system encryption which requires no programming.