tonyair/silverstripe-mssql
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-mssql synced 2024-10-22 08:05:53 +02:00
Code Issues Projects Releases Wiki Activity
268 Commits 6 Branches 14 Tags 664 KiB
PHP 100%
9ae0cecc36
Go to file
Sean Harvey 9ae0cecc36 Revert fc3df54eab
2013-04-25 11:33:54 +12:00
code Revert fc3df54eab 2013-04-25 11:33:54 +12:00
tests Use more robust Format() in test instead of strtotime() 2012-09-07 16:23:59 +12:00
_config.php MINOR Removed whitespace from _config 2010-05-13 12:26:07 +00:00
composer.json Added composer file 2012-11-03 14:14:17 +13:00
README.md Adding location of known issues to README.md 2012-12-19 20:56:41 +13:00

README.md

SQL Server Database Module

Allows SilverStripe to use SQL Server 2008 or SQL Server 2008 R2 database servers.

More information can be found on the extension page at silverstripe.org.

A list of known issues is available on open.silverstripe.org

Maintainer Contact

  • Sean Harvey (Nickname: halkyon) <sean (at) silverstripe (dot) com>

Requirements

Note: SQL Server 2008 R2 Express can also be used which is provided free by Microsoft. However, it has limitations such as 10GB maximum database storage.

Installation

The easiest way to get up and running with SQL Server on SilverStripe is using the installer:

Troubleshooting

Q: SQL Server resides on a remote host (a different machine) and I can't connect to it from mine.

A: Please ensure you have enabled TCP access using SQL Server Configuration Manager and opened firewall ports.

Q: I just installed SQL Server, but it says that it cannot connect

A: Sometimes SQL Server will be installed as a non-default instance name, e.g. "SQLExpress" instead of "MSSQLSERVER" (the default.) If this is the case, you'll need to declare the instance name when setting the server in your PHP database configuration. For example: (local)\SQLExpress. The first part before the slash indicates the server host, or IP address. In this case, (local) indicates localhost, which is the same server PHP is running on. The second part is the SQL Server instance name to connect to.

Q: I'm getting unicode SQL Server errors connecting to SQL Server database (e.g. Unicode data in a Unicode-only collation or ntext data cannot be sent to clients using DB-Library (such as ISQL) or ODBC version 3.7 or earlier)

A: If you are using FreeTDS make sure you're using TDS version 8.0 in freetds.conf. If on Windows, ensure you use the SQL Server Driver for PHP and NOT the mssql drivers provided by PHP.

Q: Using FreeTDS I can't connect to my SQL Server database. An error in PHP says the server doesn't exist

A: Make sure you've got an entry in /etc/freetds/freetds.conf that points to your server. For example:

[myserver]
	host = myserver.mydomain.com
	port = 1433
	tds version = 8.0

Then you can use "myserver" (the bit in square brackets above) as the server name when connecting to the database. Note that if you're running Macports, the file is located in /opt/local/etc/freetds/freetds.conf.

Alternatively, if you don't want to keep adding more entries to the freetds.conf to nominate more SQL Server locations, you can instead use the full the host/ip and port combination, such as "myserver:1433" (1433 being the default SQL Server port.) and ensure the "tds version = 8.0" is set globally in the freetds.conf file.

Note: Use tabs not spaces when editing freetds.conf, otherwise it will not load the configuration you have specified!

Note: Certain distributions of Linux use SELinux which could block access to your SQL Server database. A rule may need to be added to allow this traffic through.