为什么不建议在托管环境中使用 SQL Server Express Edition 提供的用户实例(也称为 RANU)?
不建议在托管环境中使用 SQL Server Express Edition 提供的用户实例(也称为 RANU)。
我有一台运行 Server 2008 R2 Web Edition 的服务器,并安装了 IIS 7.5 和 Sql Server 2008 R2 Express。
我只有 3 个朋友作为我的托管客户。每个服务器上都有一个受限制的本地用户帐户。
在生产环境中使用用户实例有什么缺点?
编辑
让我们只考虑用户实例,而不是考虑我所知道的内存使用和数据库大小的限制,为什么不推荐它?
Quoted from http://blogs.msdn.com:
User Instances (also known as RANU) available with SQL Server Express Edition, are NOT RECOMMENDED for hosting environments.
I have a server running Server 2008 R2 Web Edition with IIS 7.5 and Sql Server 2008 R2 Express installed.
I have only 3 friends as my hosting clients. Each has a restricted Local User Account on the server.
What is the drawback of using user instance in production environment?
Edit
Rather than considering the limitation in memory usage and database size that I know, let us consider the user instance only, why isn't it recommended?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我认为您问题的答案来自 RANU
什么是 RANU
并阅读 http://msdn.microsoft.com/en-us/library/bb264564(SQL.90).aspx
RANU 为每个用户启动一个单独的 SQL Express 实例进程,因此在共享环境中,假设有 30 个需要访问 SQL 的站点,然后 SQL 同时运行 30 个实例,这需要您了解大量资源/内存等。也如文章中所述,第一次为每个用户运行 SQL Express 时会复制所有系统数据库以创建该用户实例。
在一台用户机器上运行一个进程是正常的,但如果 SQL Express 开始运行许多实例,那么你会占用大量资源、内存,这不容易管理、更新等。
在链接上的文章中有有关于此的更多详细信息。
I think that the answer to your question comes with the definition of the RANU
What is RANU
and also read the http://msdn.microsoft.com/en-us/library/bb264564(SQL.90).aspx
The RANU starts a seperate instance Process of SQL Express for every user, so in a share enviroment with let say 30 sites that needs access to SQL, then SQL run 30 instances at the same time, that is takes as you understand a lot of recource/memory etc. Also as say in the article the first time SQL Express run for every user is make copies of all system database to create this user instance.
In a single user machine to run one process is normal, but if SQL Express starts to run many instances then you take a lot of resource, memory, and this is not easy to administrate, update etc.
In the article on the link there are more detail informations about this.