Thursday, April 20, 2006

Looking for some feedback...

Looking for some feedback.

The Oracle Database XE Product Marketing Team would like to hear from you if you are using XE. If you are trying out Oracle Database XE or have some real applications running on it and would like to share your experiences – I’d encourage you to post them to the online forum (see this link for details on getting to the forum and downloading the software).


Anonymous Anonymous said....

I'd like to join the XE forum but can't because I no longer have access to the email I had when I originally registered on OTN. And OTN, for some unknown reason, doesn't support email address changes in user profiles. (I know I could create another user).

Fri Apr 21, 02:51:00 AM EDT  

Blogger Thomas Presslie said....

OK will do. We're use XE on laptops to record audit info around Scotland. It's a great alternative to Personal Oracle. Fortunately the application was already developed with HTMLDB.

Fri Apr 21, 03:48:00 AM EDT  

Anonymous Michelle Lowman said....

I'm taking Oracle classes, and I use it with SQL Developer on my laptop to test the designs and scripts for my projects. It is very helpful.

Sat Apr 22, 04:13:00 PM EDT  

Anonymous J. Laurindo Chiappa said....

No, XE is NOT a valid, real, alternative to Personal in courses and training : XE is so much "feature-removed" , you can´t "get your feet wet" in partitioning and in oh so many goodies. because XE derives from Standard db edition...
In my humble opinion, XE could be derived from Personal, so we could at least "get a better start" - of course, Oracle will restrict the use (example, the size and/or the number of partitions and alike, to restrict use in production), but NOT simply cut off the features.

Tue Apr 25, 07:52:00 AM EDT  

Anonymous Anonymous said....

We're looking at it for a few things: first as a 'cache' database in front of the production databases as emergency failover (even a cluster can crash, so we have a very limited set of features we support). It is an internet based application so saying 'go away we're down' isn't an option. We'll pull some amount of data into an XE database hourly and on failure point the app servers to it. We'll have about 5% functionality, but it is important functionality to 90% of the clients. Having lost the RAC a few times, this is a nice emergency solution.

Second place is to remove the mySql/SQLServer/Postges/Access ... databases the business units have created over the years. With ODBC/JDBC and PHP/Perl interfaces, we don't change the applications, just the database underneath them.

Then we can leverage the production DBA and engineering resources to help manage them until we can replace each one into a RAC. (Funny how the business units want our help in managing and tuning until we try to take them into our control.)

Wed Apr 26, 01:19:00 PM EDT  


<< Home