你对MSSQL的看法 [英] Your thoughts on MSSQL
问题描述
嗨
我们有一个当前系统：
Linux / Apache / PHP4.x与Microsoft SQL 2000交谈
考虑去：
Windows 2003 / PHP4.x与同一个Microsoft SQL 2000盒子交谈...
你经历过的任何痛苦？我们将有一些相对较高的
负载，以及通过数据库驱动程序的复杂查询。
一切顺利
Dave。
da ******** @ gmail.com 写道：嗨
我们有一个现行系统：
Linux / Apache / PHP4.x与Microsoft SQL 2000交谈
考虑转到：
Windows 2003 / PHP4.x与同一个Microsoft SQL 2000框交谈。
你经历过的任何痛苦？我们将有一些相对较高的负载，以及通过数据库驱动程序的复杂查询。
这是我运行Apache 2.0和PHP 4的经验Win2K服务器：
*我们的并行测试服务器完全被冲洗一次。我的前任
superior决定在自杀模式下运行PHP是可以的（例如，作为CGI的
）。现在我处于他的位置：-j
*使用自定义流包装器进入4.3.6中的线程安全错误。我相信它已经固定在4.3.9或10中。
*发现Apache 2 SAPI每个字节泄漏一个字节
输出。起初并没有真正注意到它，因为Apache偶尔会重新启动
处理程序进程。在我编写了一个用于生成ISO映像的脚本之后，服务器开始经历了大量的降价。
当我从4.3交换SAPI模块时，事情恢复正常。 9.
*跟踪流氓XSLT脚本的另一个服务器稳定性问题。
因为Web服务器是多线程而不是多进程，所以
XSLT引擎在一个请求处理程序中崩溃，所有其他处理程序也死了。
。
我们也使用MSSQL而且我没有遇到任何问题mssql
函数到目前为止 - 除了255个字符的varchar限制外。
>你经历过的任何痛苦？我们将有一些相对较高的加载，以及通过数据库驱动程序的复杂查询。
如果你知道疼痛在哪里，必须有办法缓解它。
对于复杂的查询，有几个选项：
- 你可以把它们放在存储过程中。这将导致在运行时删除查询的解析
（它是在创建时完成的并且
存储）。
- 如果你习惯于面向对象，你可以为许多查询中的记录实现一些懒惰的
表包装。
最好的问候
2006年4月4日星期二19:10:13 -0700， da *** *****@gmail.com 写道：
嗨
我们有一个现行系统：
Linux / Apache / PHP4.x与Microsoft SQL 2000交谈
考虑转到：
Windows 2003 / PHP4.x与同一个Microsoft SQL 2000框交谈...
你经历过的任何痛苦？我们将有一些相对较高的负载，以及通过数据库驱动程序进行的复杂查询。
最好的
戴夫。
就个人而言，我会更改数据库（postgres或回头看看
大男孩免费：Ingres，DB2？），而不是平台。增加
性能，可靠性和暴跌TCO（事实......正确）。
Steve
Hi
We have a current system:
Linux / Apache / PHP4.x talking to Microsoft SQL 2000
Thinking about going to:
Windows 2003 / PHP4.x talking to the same Microsoft SQL 2000 box...
Any pain that you have gone through? We will have some relatively high
load, and complex queries going through the database driver.
All the best
Dave.
da********@gmail.com wrote:Hi
We have a current system:
Linux / Apache / PHP4.x talking to Microsoft SQL 2000
Thinking about going to:
Windows 2003 / PHP4.x talking to the same Microsoft SQL 2000 box...
Any pain that you have gone through? We will have some relatively high
load, and complex queries going through the database driver.
Here''s my experience running Apache 2.0 and PHP 4 on Win2K Server:
* Our parallel testing server got completely hosed once. My former
superior had decided that it was okay to run PHP in suicidal mode (i.e.
as CGI). Now I''m in his position :-j
* Ran into a thread-safety bug in 4.3.6 using custom stream wrappers. I
believe it''s fixed in 4.3.9 or 10.
* Discovered that the Apache 2 SAPI was leaking one byte for every byte
outputted. Didn''t really notice it at first, since Apache restarts the
handler process occasionally. The server started to experience massive
slow-down though after I wrote a script for generating ISO images.
Things returned to normal when I swapped it the SAPI module from 4.3.9.
* Traced another server stability problem to a rogue XSLT script.
Because the web server is multithreaded rather than multiprocess, when
the XSLT engine crashes in one request handler, all other handlers die
too.
We use MSSQL as well and I haven''t had any problem with the mssql
functions thus far--except for the 255-character varchar limitation.
> Any pain that you have gone through? We will have some relatively highload, and complex queries going through the database driver.
If you know where the pain is, there must be ways to relieve it.
For complex queries, there are a few options:
- You could put them in stored procedures. This will cause the parsing
of the queries to be dropped at runtime (it was done at create time and
stored).
- If you are used to object orientation, you could implement some lazy
table wrappers for records that are part of many queries.
Best regards
On Tue, 04 Apr 2006 19:10:13 -0700, da********@gmail.com wrote:
Hi
We have a current system:
Linux / Apache / PHP4.x talking to Microsoft SQL 2000
Thinking about going to:
Windows 2003 / PHP4.x talking to the same Microsoft SQL 2000 box...
Any pain that you have gone through? We will have some relatively high
load, and complex queries going through the database driver.
All the best
Dave.
Personally, I''d change the database ( postgres or look back at the
big boys going free: Ingres, DB2? ), rather than the platform. Increase in
performance, reliability, and plummeting TCO ( get the facts... right ).
Steve
这篇关于你对MSSQL的看法的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
