Also, have to note (the manual and online pages are cryptic on that) the db roles needed to be given to the db user account one will use for MonoX.
db_owner (and public which can't be unchecked) is needed at Security/Logins, right click the user, select Properties, then User Mapping at the dialog that opens up, then select the mono db you created and check the "db_owner" role
must make it clear that selecting all roles there (as a newbe might do) will just fail, since if you give "db_denydatareader" you'll get
"The SELECT permission was denied on the object 'database_principals', database 'mssqlsystemresource', schema 'sys'."
by MonoX installer
anyway, having found my way arround the above, now I'm stuck at:
2012-06-01 19:03:11Z: Installation starting ...
2012-06-01 19:03:11Z: Creating database ...
2012-06-01 19:03:21Z: Database created.
2012-06-01 19:03:21Z: Importing data ...
2012-06-01 19:03:21Z: Importing "aspnet_Applications" ...
2012-06-01 19:03:21Z: Could not find stored procedure 'sp_dboption'.
one thing I found related seems to say that MonoX might not work with SQL Server 2012:
If you are using SQL Server 2012 features with a SharePoint farm, you must apply SharePoint Server2010 Service Pack 1 (SP1) to the farm before adding SQL Server 2012 features. Pre-SP1 version of SharePoint 2010 uses a deprecated feature that was removed in Microsoft SQL Server 2012 . Applying SP1 adds a new methodology for connecting to SQL Server 2012 features.
Evidence that SP1 is required
This section describes the errors that will occur if SP1 is not installed. Errors are most likely to occur when you create a farm or update information in the configuration database. The following list summarizes the more common ways you will encounter this error.
In ULS logs, you will find the following error: Could not find stored procedure 'sp_dboption'.
In the SharePoint Products Configuration wizard, the wizard fails to create the configuration database.
is there a workarround for this issue? I see some discussion at:
the code MonoX uses there should change according to http://msdn.microsoft.com/en-us/library/ms187310(SQL.105).aspx
SQL Server 2008 R2
Displays or changes database options.
Do not use sp_dboption to modify options on either the master database or the tempdb database.
This feature will be removed in the next version of Microsoft SQL Server. Do not use this feature in new development work, and modify applications that currently use this feature as soon as possible. Use ALTER DATABASE instead. To modify database options that are associated with replication (merge publish, published, subscribed), use sp_replicationdboption.