mssql

Hi,

I have Drupal 7 running on Server 2008 R2 with IIS 7.5 and MSSQL 2008.

I am wanting to use drupal to replace a legacy application that runs on an Oracle Database.

I have copied over a specific table from Oracle to another database on the same MSSQL server as Drupal is connected to.

I now want/need to move circa 320,000 articles from that table and create them as nodes within Drupal.

Hi everybody:

Is there a possibility to connect to MSSQL with trusted connection associated with drupal users; maybe using LDAP or something like that?

Otherwise can be set a pool of connections for the drupal users and keep track of who user use some login?

Please light me on this.

PD: I do my best with the English so if there errors sorry for that.

Hejsan
Jag är helt noob när det gäller Drupal och Databaser. Jag ska hämta information från en Mssql server och visa den i en view i Drupal. Jag använder mig av en modul som heter Migrate och Views. Jag ha även laddat ner följande driver.

http://drupal.org/project/sqlsrv.

Jag ändrade kod i filen settings.php som följande

$databases['default']['my_source_db'] = array(
'driver' => 'sqlsrv',
'database' => 'mydb',
'username' => 'myuser',
'password' => 'mypass',
'host' => 'myhost',
'prefix' => '',
)

Jag ändrade kod i database. inc filen som följande

My install is a local install with Windows+IIS+MSSQL, which was mentioned here: http://groups.drupal.org/node/121629.

I downloaded the Commerce Guys Drupal 7 download from http://microsoft.com/web/drupal, and it's working great. But as soon as I downloaded v.7.2 and installed it, I started seeing a "security update" message stating the following:

There is a security update available for your version of Drupal. To ensure the security of your server, you should update immediately! See the available updates page for more information and to install your missing updates.

Has anyone attempted a D7 installation on IIS using MSSQL yet? I have a client with very specific requirements, and was curious to find out others' experiences in this area.

Thanks!

Adams 12 Five Star Schools is very pleased to announce our newly-redesigned, SQL Server-powered Drupal Web site! Our site exemplifies the power and flexibility of Drupal. It is also speaks to the quality of community that helps develop, instruct, and support the Drupal project. Without this exceptional and active community, our site would not have been possible. We're continually working to improve our site and welcome your feedback. (Sorry for the delay, I had promised this write up a while ago but have just now had the time to put it together).

Abstract

Drupal 6.0 is revamped with Schema API, so what's next for Drupal 7.x? PDO for sure! With this powerful data-access abstraction layer, workload will much reduced for DB abstraction layer designers and developers, and finally benefit our contribute developers and end users.

By the way, together with the decision of Drupal 7.x + PDO, there is also some voice about moving PostgreSQL (and so other potential databases support, e.g. Oracle, DB2, MSSQL, etc) support away from core, but contribute; on the other hand, add official SQLite support into Drupal core, together with MySQL.

Is this really a good idea? Or even if it is possible? As an existing Drupal + PostgreSQL users, what will this affect your daily work? As a potential customer of Drupal + Oracle/DB2/MSSQL/etc, is this a good new for you, or just an evil? I would like to provide some brief idea for you within this article.

So, I've had some free time latley, and I've started back on the database API layers (DB2 and SQL Server currently).
However, I have found 2 disturbing issues.

Overview
First, I'm currently exploring the following 3 ways to connect to sql server:
1. FreeTDS
2. php_mssql driver
3. MSFT SQL Driver ( See pcorbetts posting for a link to the driver )

1. PHP 5.2.5 breaks support for SQL Server

So, you want to speed up your large site? Well, start by cleaning up your SQL if you're accessing large tables. We are running Drupal on top of MS-SQL for a client. We have one table that has 7.5 millinon rows in it. Now, I had mentioned what I am about to talk about in another post before, but I know have some hard numbers to base it off of.
So anyway, this table had 7.5+ million rows, and the page was loading mighty slow. Running it 10 times, Devel query showed where I was bleeding...more like gushing time:

<

ol>

Ok, i'll be the one to call the pink elephant in the room.....stored procedures do exisit. There I said it. :). With MySQL 5 starting to support them, Postgres has had them, and the push latley to start using a wider array and more robust DB's (oracle, mssql, DB2), it is time I think to start thinking about a database abstraction layer to handel stored procedures. I'm thinking perhaps something like this:

/**
* @param $proc_name Name of the stored proc.
* @param $args Argements to send to the proc indexed by the variables name. e.g. array('name' => 'Jim Smith');