blocks|key|5275251|text|这真的归结于你的are服务器和你的sql服务器做了多少工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5275252|如果没有更多的信息，我怀疑你将得到任何有用的答案。|5275253|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

It really comes down to how much work your webserver and your sql server are doing.

Without more information I doubt you are going to get any helpful answers.

blocks|key|762843|text|这将取决于服务器的预期负载。对于小型站点，这是完全没有问题的(如果配置正确)。对于大型站点，您可能需要考虑将负载分布在不同的服务器上:+web服务器、文件服务器、数据库服务器等。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|762844|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It will depend on the expected load of the server. For small sites, it is no problem at all (if correctly configured). For large sites, you might want to consider distributing the load over different servers: web server, file server, database server, etc.

blocks|key|3019258|text|对于小站点来说，这并没有什么不同。然而，随着负载的增长，这种扩展真的很糟糕，而且比您想象的要快：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3019259|3019260|数据库服务器建立在它们“拥有”服务器的前提之上。它们以内存换取速度，并且很容易将所有可用的内存用于内部缓存。|unordered-list-item|3019261|一旦资源开始匮乏，分析就变得非常困难--很明显，IIS和SQL都受到了影响，不太清楚瓶颈在哪里。IIS需要CPU，SQL+Server需要内存或CPU等等。|3019262|无论你在代码中放了多少层，它都在同一个CPU上运行，因此一个单层的应用程序在这种情况下会运行得更好--开销更小--但它不会scale.|3019263|Security真的很糟糕，通常你会把SQL隔离在防火墙后面！|3019264|3019265|3019266|如果你能负担得起，花几块钱买一台第二台服务器可能更好，也许是使用PostgreSQL。一台IIS服务器和一台PostgreSQL的成本与在IIS+%2B+SQL+server上差不多，因为许可成本……|3019267|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|S|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|W|8|@]|9|@]|A|$]]|$1|L|3|-4|5|E|7|X|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Z|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|Q|$]]

For small sites, it doesn't make a bit of a difference.
As the load grows, though, this scales really badly, and quicker than you think:

<ul>
<li>Database servers are built on the premise they "own" the server. They trade memory for speed and they easily use all available RAM for internal caching.</li>
<li>Once resources start to be scarce, profiling becomes very difficult -- it is clear that IIS and SQL are both suffering, less clear where the bottleneck is. IIS needs CPU, SQL Server needs RAM or CPU etc etc</li>
<li>No matter how many layers you put in your code, it all runs on the same CPU, therefore a single layered application will run better in this context -- less overhead -- but it will not scale.</li>
<li>Security is really bad, usually you isolate SQL behind a firewall!</li>
</ul>

If you can afford it, it's probably better to shell out a few bucks and get a second server, maybe using PostgreSQL. One IIS server and one PostgreSQL cost about as much as on IIS + SQL Server because of licensing costs...

blocks|key|3019393|text|我想说，最好是在同一台服务器上运行它们，直到它成为问题。这样一来，你就可以节省一些钱和时间。一旦网站获得成功，并需要进行一些架构更改，它就应该已经为自己付出了代价。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3019394|请记住备份:)|3019395|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I'd say it was best to run them on the same server until it becomes a problem. That way you'll save yourself some money and time upfront. Once the site becomes a success and requires a some architectural changes it should have already paid for itself.

Remember to back up :)

blocks|key|3019415|text|如果你的web服务器是可以公开访问的，从安全的角度来看，这是一个非常糟糕的想法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3019416|虽然从路由、防火墙、端口、身份验证等角度来看，这会使很多事情变得更加困难，但分离是好的。当您的数据库服务器在web服务器上运行时，如果您的web服务器受到威胁，那么您的sql服务器也会受到影响。|3019417|当你把它们放在不同的盒子里时，你的标准就提高了一点。|3019418|要保护您的web服务器和数据库服务器，还有很多工作要做，但为什么要让它比需要的更容易呢？|3019419|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

If your web server is publicly accessible, this is a VERY bad idea from a security perspective.

Although it makes a lot of things more difficult from a routing, firewall, ports, authentication, etc. perspective, separation is good. When you have your database server running on the web server, if your web server is compromised, then your sql server is, too.

When you have them on separate boxes, you've raised the bar a little.

There's still a lot more work to be done to secure your web server AND your database server, but why make it easier than it needs to be?

blocks|key|3864073|text|较大的商店可能不会认为这是最佳实践...但是，如果您不是每秒处理数百个请求，则可以将它们放在一个盒子中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3864074|事实上，对于小型应用程序，您将在后端看到更好的性能，因为数据不必通过网络传输。这一切都与规模有关。|3864075|请记住，数据库服务器会消耗内存。这里有一个重要的经验教训：如果您决定在web服务器所在的同一台计算机上运行SQL+Server2005(这就是您在问题中提到的设置)，请确保进入Sql+Server+Management+Studio并执行此|offset|length|style|BOLD|3864076|3864077|右键单击服务器实例，然后从左侧列表中单击properties|ordered-list-item|3864078|Select+'memory‘。|3864079|将'maximum+|3864080|+memory’更改为您的服务器可以承受的内存。|3864081|3864082|如果您不这样做，SQL+Server最终将占用服务器的所有RAM并无限期地挂起它。这将导致您的服务器或多或少地停滞不前。如果您没有意识到这一点，故障排除可能会非常令人沮丧。|3864083|我已经这样做过好几次了。如果你拥有一家大公司的基础设施，而且它没有规模，你不会这么做，但它适用于很多事情。|3864084|entityMap^0|0|0|T|2J|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|12|8|@$F|13|G|14|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|16|8|@]|9|@]|A|$]]|$1|N|3|O|5|M|7|17|8|@]|9|@]|A|$]]|$1|P|3|Q|5|M|7|18|8|@]|9|@]|A|$]]|$1|R|3|S|5|M|7|19|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1B|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|Z|$]]

Larger shops would probably not consider this a best practice... However, if you aren't dealing with hundreds of requests per second, you're fine putting them both on one box. 

In fact, for small apps, you will see better performance on the back-end because data does not have to go across the wire. It's all about scale.

Keep in mind that database servers eat memory. Here's one important lesson from the school of hard knocks: if you decide to run SQL Server 2005 on the same machine as your web server (and that is the setup you mentioned in your question), make sure you go into Sql Server Management Studio and do this:

<ol>
<li>Right click on the server instance and click properties</li>
<li>Select 'memory' from the list on the left </li>
<li>Change 'maximum server memory' to something your server can sustain.</li>
</ol>

If you don't do that, SQL Server will eventually take up all of your server's RAM and hang onto it indefinitely. This will cause your server to more or less sputter and die. If you are not aware of this, it can be very frustrating to troubleshoot.

I've done this quite a few times. It's not something you would do if you had the infrastructure of a large corporation and it does not scale, but it's fine for a lot of things.

blocks|key|3864137|text|我一次又一次地看到这个问题。正确的答案是将SQL+Server放在一台计算机上，将IIS+(web服务器)放在另一台计算机上。您的钱将投入SQL+Server机器，因为必须购买合适的驱动器系统和RAM才能支持高效的服务器，但web服务器可以是一台规模小得多且价格较低的机器，只需一个镜像驱动器集。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3864138|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I've seen this issue over and over again. The right answer is to put SQL Server on one machine and IIS (web server) on the other. Your money will go into the SQL Server machine because the right drive system and RAM must be purchased to support a efficient server but the web server can be a much scaled down &amp; less expensive machine with just a mirrored drive set.

Is it good, bad, or indifferent to run SQL Server on your webserver? 

I'm using Server 2008 and SQL Server 2005, but I don't think that matters to this question.

Running SQL Server on the Web Server

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在您的bad服务器上运行SQL Server是好是坏，还是无关紧要？我使用的是Server2008和SQL Server2005，但我认为这对这个问题并不重要。

问在Web服务器上运行SQL Server
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Web服务器上运行SQL ServerEN