使用 SQL Server for WSS 3.0 代替 Windows 内部数据库
实际上有两个相关的问题：
是否可能或建议对 SharePoint Services WSS3.0 使用完整的独立 SQL 服务器，而不是它附带的 Windows 内部数据库？我正在工作的客户要求将他们现有的 SQL 服务器用于所有 WSS 内容数据库，以尽量减少管理工作并提高性能。
此外，您是否建议在一台物理服务器上安装 WSS，在另一台服务器上安装内容数据库？性能上有什么提升吗？实用性？等等。默认为 WSS，其所有数据库都安装在同一台服务器上。我们实际上并不需要 MOSS 场设置，因为 WSS 功能足以满足我们的需求。
谢谢， 瓦尔
There are actually two related questions:
is it possible or advisable to use a full blown stand-alone SQL server for SharePoint Services WSS3.0 instead of the supplied windows internal database it comes with? The client I am working for is asking to utilize their existent SQL server for all WSS content databases to possibly minimize admin effort and improve performance.
As well, would you advise to install WSS on one physical server and the content database on another server? Any gain in performace? Practicality? ect. The default is WSS and all of its databases are installed on the same single server. We don't really need a farm setup of MOSS, because the WSS capabilities are enough for our needs.
Thanks,
Val
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
是的，当您创建站点时，请检查安装是否为“Web 前端”，然后它会提示您选择 SQL 数据库的位置。只需将其指向您想要的服务器即可。
我绝对建议将其放在非 Sql Express 实例上。 Express 版本只能扩展到 4 GB，并限制最大连接数等。如果您的客户要用它做很多事情，您最终将达到该限制。成熟的 SQL Server 还有其他优点，例如帮助备份等。
Yes, when you create the site check the installation to be a "Web Front End" It will then prompt you to select a location for the SQL database. Just point it to which server you want.
I would definitely recommend putting it on a non-Sql Express instance. The express version only scales to 4 gig, limits the maximum number of connections etc. If your client is going to do much with it at all, you will eventually hit that limit. Full blown sql server has other advantages too, like help with backups etc.
是的，是的。
将 SQL 和 WSS 服务器分开可以节省两者的资源，而且也不是轻量级应用程序。它还允许您在使用量增加时轻松启动集群/分布式环境，以及遵循最小权限原则、将产品补丁分开等。
作为附录，您说您不需要 MOSS 场，因为 WSS满足您的需求，但请注意，设置分布式 WSS 环境与 MOSS 一样容易； MOSS 仅向应用程序添加功能。如果只是为了在发生故障时提供冗余，那么在场中至少拥有两个 WFE 通常是一个好主意。
Yes and yes.
Keeping the SQL and WSS servers separate saves resources on both, and neither are light weight applications. It also allows you to easily begin clustered/distributed environment in the event your usage increases, as well as following a least privledge principle, keeping product patches separate, etc.
As an addendum, you say you don't need a MOSS farm because WSS fits your needs, but be aware that it's just as easy to setup a distributed WSS environment as is MOSS; MOSS only adds capabilities to the application. It's usually a good idea to have at least two WFE's in the farm, if for nothing else than redundancy in case of failure.
是的，您可以使用“功能齐全”的 SQL Server，而不是随 Windows SharePoint Services 3.0 (wss 3.0) 提供的免费且受限的 SQL Server Express。
将数据库和实际网站分开甚至更好！更具可扩展性（如果升级到 MOSS）、更易于管理且安全风险更低。
Yes you can use a 'full blown' SQL Server instead of the the free and limited SQL Server Express that is delivered with Windows SharePoint Services 3.0 (wss 3.0)
It's even better to separate the database and the actual website! More scalable (if you upgrade to MOSS), easier to manage and less security risks.