Sorry to be the bearer of bad news, but your best bet is probably:

很抱歉成为坏消息的承担者,但你最好的选择可能是:

1. Maintain copies of your data outside of the database (I don't know the details of your setup, so this may defeat the purpose of what you're trying to do). Basically, keep a file cache of the content you want to stream and write an application to keep the file cache synchronized with the database.

在数据库之外维护数据的副本(我不知道您的设置的详细信息,因此这可能会破坏您尝试执行的操作的目的)。基本上,保留要流式传输的内容的文件缓存并编写应用程序以使文件缓存与数据库保持同步。

2. Switch to Windows Server 2008. The Web Server and Standard editions for 2008 support custom plugins and should be much more affordable than the Enterprise editions (I believe the Web Server edition is under $500).

切换到Windows Server 2008. 2008的Web服务器和标准版支持自定义插件,应该比企业版更实惠(我相信Web服务器版本低于500美元)。

Maybe someone else has some clever solution, but these are the only options I'm aware of.

也许其他人有一些聪明的解决方案,但这些是我所知道的唯一选择。

There is nothing that ships out of the box but WMS does support additional custom plug-ins. From a performance perspective you might want to consider why you need to do so. The easiest way in my mind would be to write an HTTP wrapper around the database and use the built-in HTTP streaming data source. The knowledge and skills required to write the HTTP wrapper is more plentiful than writing WMS plugins. If you do have a use case for this consider SQL Server 2008's filestream feature as it is designed for giving you the relational power with file system performance.

没有任何东西可以开箱即用,但WMS确实支持其他自定义插件。从性能角度来看,您可能需要考虑为什么需要这样做。在我看来,最简单的方法是在数据库周围编写HTTP包装器并使用内置的HTTP流数据源。编写HTTP包装器所需的知识和技能比编写WMS插件更丰富。如果您确实有一个用例,请考虑SQL Server 2008的文件流功能,因为它旨在为您提供文件系统性能的关系功能。