Currently our Ebase installation stores the repository database within SQL Server 2008.
I am considering moving our repository database back to Derby so that the only point of failure is the server running Ebase.
Are there any benefits in using SQL server for the repository database?
repository database choice
Moderators: Jon, Steve, Ian, Dave
-
- Ebase User
- Posts: 201
- Joined: Fri Dec 20, 2013 1:29 pm
- Location: Dartford Borough Council
- Contact:
- dvanhussel
- Ebase User
- Posts: 161
- Joined: Fri Oct 19, 2007 12:45 pm
- Location: Haarlem, the Netherlands
Benefits that I can think of are:
- backup and restore (of specific tables) is easier with SQL Server
- 'browsing' the contents of the repository (when developing/maintaining forms) is easier
I think that when you have an error connecting to SQL server for the repository (network problems or the database is down), you probably can expect other problems when your forms try to call/write to other backoffice systems. So I think that this 'single point of failure' is not really an issue.
Having said that, there is of course nothing wrong with using Derby. But I probably would not start a migration only to fix this 'problem'.
I 'm not sure if Derby has performance benefits. But my guess would be that it will not be in (big) favour of MSSQQL or Oracle. Maybe Ebase staff has some info on this?
- backup and restore (of specific tables) is easier with SQL Server
- 'browsing' the contents of the repository (when developing/maintaining forms) is easier
I think that when you have an error connecting to SQL server for the repository (network problems or the database is down), you probably can expect other problems when your forms try to call/write to other backoffice systems. So I think that this 'single point of failure' is not really an issue.
Having said that, there is of course nothing wrong with using Derby. But I probably would not start a migration only to fix this 'problem'.
I 'm not sure if Derby has performance benefits. But my guess would be that it will not be in (big) favour of MSSQQL or Oracle. Maybe Ebase staff has some info on this?
0 x
-
- Moderator
- Posts: 1342
- Joined: Wed Sep 12, 2007 12:49 pm
Most customers have additional databases configured as well as the Ebase repository, and these use external database systems i.e. not Derby. If these external databases are Mysql, SQL Server or Oracle, you might as well use these for the Ebase repository as well. But if you don't have additional databases configured, it's not so clear. I agree with David that in general, if you pay for a database system, you generally get better tools and they're easier to work with, but it's not an enormous benefit.
0 x
-
- Ebase User
- Posts: 201
- Joined: Fri Dec 20, 2013 1:29 pm
- Location: Dartford Borough Council
- Contact:
Who is online
Users browsing this forum: No registered users and 9 guests