Revo 2.1 RC help with MS Sql

I’m curious on how the Revo 2.1 RC and MSSql are working out.

Would it be a large percentage of extras that would not work then as of now with MSsql.
Just wanting some general insights on when going with MS Sql would be greenlighted for production sites.
Of if running a test install would help out.

I’m not any more an MS developer than a PHP dev’er unfortunately.

Would the MSsql give me problems, for example to go ahead and install and work through Mary’s coding pad tuts, etc. ?

Thanks,
T-man

Hey I jumped on the bus, sort of...
Happened to catch the new RC 4 release, and am trying to get my install to connect to the database, on a plesk shared hosting account and using the MS Sql (or sqlsrv option from the drop down).
Pretty sure I have everything correct but no connection.

Could it be I need to use something for Database Host other than localhost.
I’ve tried, localhost and the domain & sub-domain names and also now the IP address, still nothing when I click...
[Test database server connection and view collations.]
I can’t tell if it’s firing anything when I click that, the red text message:
Connecting to database server: is the only showing now since the first click.

Any suggestions?
Thanks, guess this is a support topic now, nothing urgent though. thanks.

OK tried installing the revo 2.01 rc4 just using mySql and it appears my host may not have PDO installed.
Checking with them on this, hope they get it sorted for me.
that could of created any MS Sql issues for me then also, even though MS sql install never got to the error message, so guessing something else is amiss for MS sql.
I’ll just keep it simple and go with MySql for now then.
Waiting to hear from my host support.
I’ll give a shout back when I have a good install live in the world.
-t

Hey again, my host set up PDO suppport for me, and I stepped through the install (almost).
I went with just using MySQL no the MS Sql setup, saving MS Sql for later when it works a treat !!
I got down to the install, and what sounds like the white screen of limbo.

I double checked everything from the docs here, all looked ok, I made the entire contents of the core folder writeable, seemed to be best solution there for me at least:
----------------
If you get a blank screen or cannot proceed after clicking ’Install’, verify these steps:
Make sure the directories "/core/packages","/core/cache", "/core/import", and "/core/export" are writable.
Make sure your php.ini setting sets memory_limit to 128M, and max_execution_time to 120
Create a blank file "/core/config/config.inc.php" and make it writable. DO NOT COPY config.inc.tpl! Just make it a blank file!
Post a message in the Revolution forum regarding your issue. State your server setup and installation info, and we’ll try and help you find a solution.
----------------
UPDATE: The max_execution_time is set to 30 so that could be a problem, how would I change that ask the host?
Maybe if I just backed up and tried to run it again it would be a success, not likely tried?

My server details, maybe some upgrades have taken place since these but here goes:
Operating System - Windows 2003 - IIS 6 me thinks (checking).
PHP Version - 5.2.3
MySQL Version - 5.0.37

----------
thanks, hoping for a response since this isn’t in the support category, and it’s a support post of sorts now.
The install was today Revolution 2.1 rc4.

Quote from: Crssp at May 02, 2011, 12:09 PM

I’m curious on how the Revo 2.1 RC and MSSql are working out.

Would it be a large percentage of extras that would not work then as of now with MSsql.
Just wanting some general insights on when going with MS Sql would be greenlighted for production sites.
Of if running a test install would help out.

I’m not any more an MS developer than a PHP dev’er unfortunately.

Would the MSsql give me problems, for example to go ahead and install and work through Mary’s coding pad tuts, etc. ?

Thanks,
T-man

Most of the Revo add-ons use xPDO, so they should work fine since xPDO is handling the database access for you. The only ones that wouldn’t work are ones that contain actual MySQL code. I don’t know of any, but there may be a few.

All add-ons created by OpenGeek or splittingred should work fine. I haven’t tested mine, but AFAIK, they should work as well.
I don’t have access to an MS SQL server so I can’t test them, but I’m sure someone will let me know if there are problems.

Its not really the MSSQL bit that will cause the extra to fail in 2.1 if as BobRay says it uses xPDO(although I did find a packaging bug in Frontpage using MSSQL that doesn’t appear in MYSQL) its mainly the removal of deprecated API functions in MODX, such as $modx->documentIdentifier and the like that have to be converted for use in 2.1 where the work is.

Quote from: shamblett at May 03, 2011, 11:01 PM

(although I did find a packaging bug in Frontpage using MSSQL that doesn’t appear in MYSQL)

Now you’re making me nervous.

This the thread http://modxcms.com/forums/index.php/topic,62863.msg356905.html, the packaging script was wrong, MYSQL didn’t complain, MSSQL did.