altquark
Legendary Poster
...there isn't any.
Thats the official line from Oracle now.
After moving from Microsoft Access files for a local database type to MSDE and finally a choice between Microsoft SQL Server Express and Oracle Express, Oracle has been steadily phasing out SQL Server Express support in favor for Oracle Express Edition.
We questioned Oracle on the fact that SQL Server Express 2005 was the only MTR for EnterpriseOne 8.98.4.3 - yet SSE 2005 requires .NET 2.x, which has been phased out of support in favor of .Net 3 and 3.5. In a specific VDI environment - the use of SSE 2005 causes issues with the .NET setup. When we asked Oracle about SSE 2008 support, of course we got the "it'll never be supported. ever" line.
Yup - according to GSS, the next tools release will not even have SSE support in it :
[ QUOTE ]
Regarding SQL Server 2008 Express, it is NOT supported for Client and Deployment machines, as it is not in Client/Deployment server MTRs document.
You can also take a look at the Statement of Direction document (Note 749393.1), which contains the software supported by current releases of E1 and also indicates Oracle's plans for adopting platform components in future releases.
[/ QUOTE ]
when you look at the document 749393.1, you will see the following note under "Planned Withdrawals" :
[ QUOTE ]
Microsoft SQL Server 2005 Express as the local
database for deployment server and development
client. Future releases will use only Oracle
Database for the local database.
[/ QUOTE ]
So, start moving to Oracle Express Edition as soon as possible. Given the fact that the latest E1 Standalone uses Oracle Universal Installer to install everything (you install the Oracle Express database first, then the E1 client) - it makes perfect sense that theres no room for SSE anymore. But its probably a rude awakening for a lot of installs out there
I for one am quite glad that Oracle is standardizing on a single "local" database platform.
This has, of course, no affect on the Database Server support direction (SQL Server 2008 is and will continue to be supported).
But it does show that Oracle is continuing to push THEIR tools wherever possible.
Thats the official line from Oracle now.
After moving from Microsoft Access files for a local database type to MSDE and finally a choice between Microsoft SQL Server Express and Oracle Express, Oracle has been steadily phasing out SQL Server Express support in favor for Oracle Express Edition.
We questioned Oracle on the fact that SQL Server Express 2005 was the only MTR for EnterpriseOne 8.98.4.3 - yet SSE 2005 requires .NET 2.x, which has been phased out of support in favor of .Net 3 and 3.5. In a specific VDI environment - the use of SSE 2005 causes issues with the .NET setup. When we asked Oracle about SSE 2008 support, of course we got the "it'll never be supported. ever" line.
Yup - according to GSS, the next tools release will not even have SSE support in it :
[ QUOTE ]
Regarding SQL Server 2008 Express, it is NOT supported for Client and Deployment machines, as it is not in Client/Deployment server MTRs document.
You can also take a look at the Statement of Direction document (Note 749393.1), which contains the software supported by current releases of E1 and also indicates Oracle's plans for adopting platform components in future releases.
[/ QUOTE ]
when you look at the document 749393.1, you will see the following note under "Planned Withdrawals" :
[ QUOTE ]
Microsoft SQL Server 2005 Express as the local
database for deployment server and development
client. Future releases will use only Oracle
Database for the local database.
[/ QUOTE ]
So, start moving to Oracle Express Edition as soon as possible. Given the fact that the latest E1 Standalone uses Oracle Universal Installer to install everything (you install the Oracle Express database first, then the E1 client) - it makes perfect sense that theres no room for SSE anymore. But its probably a rude awakening for a lot of installs out there
I for one am quite glad that Oracle is standardizing on a single "local" database platform.
This has, of course, no affect on the Database Server support direction (SQL Server 2008 is and will continue to be supported).
But it does show that Oracle is continuing to push THEIR tools wherever possible.