The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Would be good if this were documented a bit better on the project page. The README is a good start.
The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Would be good if this were documented a bit better on the project page. The README is a good start.
Comments
Comment #1
artusamakWhat are you missing specifically? You have the release note page for indications: http://drupal.org/node/1207972
Comment #2
mgiffordWe're LAMP developers but have a client who is dead set on launching a Drupal site in Windows. I think that is probably the case for most who are looking at this module.
We ran into an error with another module that directed us here for the solution. We installed the module as per usual in Drupal, but it didn't seem to act as usual.
Putting the install instructions with the release notes is good, but better to have them highlighted on the main project description page so that it's clear right from the beginning.
Is there a way of knowing if http://www.iis.net/download/URLRewrite is installed on the server if all we've got is FTP access?
We've got a version of D7 running, so I assume that http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=20098
Can we add in this module after Drupal's already been installed? We've installed this module enough at this time and the Windows server seems to take forever to implement it. We don't know enough about what is normal in Windows and what might just be a really slow server.
Also not clear if we can disable this module after it's been disabled. I'd expected that you could (as with most other modules) enable & evaluate without worrying about re-installing. Is it possible to uninstall it like any other module?
Comment #3
artusamakThis "module" is just a way to store the code base of the SQL Server database driver. It's not a module such as Views, meaning that you are not going to enable it, disable it nor reinstall it. If you read the instructions you have to copy the content of the sqlsrv folder into /includes/database/sqlsrv before installing your site. This way you will be able to install your drupal site on a SQL Server database.
Comment #4
mgiffordOk.. This is good to know.. Sorry we didn't RTFM, but we're hoping to make that more obvious by starting this tread..
We are dealing with an SQL Server that is already running Drupal. We're being brought in a bit late to the process.
Sounds like you are strongly recommending we re-install the system after moving the database to /includes/database/sqlsrv
Comment #5
artusamakI do. ;)
Comment #6
hobo commentedLooks like the /includes/database/sqlsrv is already there (version 7.x 1-1) When I installed originally I didn't have the actual module in sites/all/modules but the .inc files were in the /includes/databasess/sqlsrv .. Looking at the module i don't think it actually does anything except get registered for updates.
Did i mention we are trying to connect to Microsoft SQL Server 2005??
I saw some issues with rc-1 and ms sql server 2005 but don't see anyone posting about issues with 2005 in the issue queue with 1.1
Though the module page does mention this:
It supports both SQL Server (version 2008 and later)
Anyone know if this will work with MS SQL 2005?
Also should i re-install the site if I didn't have the actual module files in sites/all/modules/sqlsrv but I did have all the .inc files in /includes/databasess/sqlsrv ?
Comment #7
artusamakYou couldn't have installed your website on SQL Server (even 2005) if the driver wasn't in the includes/databases folder. So yes you can remove the sqlsrv module and you don't have to reinstall.