滑轨和放大器; 2008 MSSQL - 将我们打的障碍？ [英] Rails & MSSQL 2008 - Will We Hit Barriers?

问题描述

我工作的那家公司正在寻求从的ColdFusion 8 / Windows的on Rails的/ Linux的交换机平台和Ruby。我们的数据库解决方案仍将是2008年MSSQL在Windows上。我很可能会跟进一系列分头这种迁移有关的问题，但现在我有一个MSSQL和放大器; Rails的具体问题。

The company I am working for is looking to switch platforms from ColdFusion 8 / Windows to Ruby on Rails / Linux. Our database solution will remain as MSSQL 2008 on Windows. I will likely follow up with a series of questions relating to this migration separately, but for now I have a MSSQL & Rails specific question.

早在2006年，当我用Ruby的工作on Rails的首次，对于MSSQL安装支持是pretty的前途未卜。事情的来龙去脉在大多数情况下，但是ActiveRecord的无法应付来自T-SQL缺少某些功能。首先，我记得自动分页不能正常工作，由于缺乏像一个在MySQL中发现了一个OFFSET关键字。

Back in 2006 when I was working with Ruby on Rails for the first time, support for MSSQL installations was pretty iffy. Things worked for the most part, but ActiveRecord couldn't cope with certain functions lacking from T-SQL. Primarily, I recall auto-paging not working due to a lack of an OFFSET keyword like the one found in MySQL.

我很好奇，如果我们的主数据库服务器上运行MSSQL 2008年将能占据优势的ActiveRecord的的的的最的功能。如果有特别的功能都无法使用，我很好奇他们是什么。

I am curious if our primary DB server running MSSQL 2008 will be able take advantage of most of ActiveRecord's functionality. If there are particular features that are not available, I'd be curious as to what they are.

推荐答案

是的，会有痛感。

我们正在运行的Rails / SQL Server中的生产的时刻。我们所有的发展探析的完成在OS X / Linux操作系统，并部署到Linux的应用服务器。

We're running Rails/SQL Server in production at the moment. All of our develompent is done on OS X / linux, and deployed to linux app servers.

我们去使用JRuby到底是通过JDBC连接，而不是ODBC是更痛苦。 JRuby的本身就是一个很好的平台，但我们已经后患无穷因怪癖与第三方宝石和插件往往JRuby的（特别是如果他们已经得到了原生扩展）。

We went with JRuby in the end as connecting via JDBC rather than ODBC was much less painful. JRuby itself is a good platform, but we've had no end of trouble due to quirks with 3rd party gems and plugins which often don't work under JRuby (especially if they've got native extensions).

有依然在支撑孔 - 分页依然前途未卜，但那种工作了。从内存中大约有单code和字符编码一些怪癖也。

There are still holes in the support - paging is still iffy, but kind of works now. From memory there are some quirks around unicode and character encoding as well.

的唯一原因SQL Server正在使用的，因为那是什么样的IT基础架构团队授权。 MySQL的/ Postgres的是，如果可能的一个更好的解决方案。这一切都只是工作。

The only reason SQL Server is used is because that was what the IT infrastructure team mandated. MySQL/Postgres is a much better solution if possible. It all just works.

这篇关于滑轨和放大器; 2008 MSSQL - 将我们打的障碍？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！