What do I have to pay attention when upgrading from Firebird 1.5.6 to 2.5 - firebird

I have problem with my Delphi + Firebird application that works on two Windows 7 machines.
Firebird database used is 1.5.6. and is placed on server machine and the client application is on the other.
From time to time application is freezeing itself for random time from 30 sec to 2 min.
Maybe upgradeing to the new version it will stop making problems to me.

You can first take a look at this which was a presentation during firebird conference 2011

Few things I ran into while I was upgrading were:
reserved word "type" was used as a column name in a table. I had to change it to something esle in database and application code.
my database used my own UDF, which was compiled in a manner, that made it impossible to use with Firebid 2.5 server. I had to recompile it, and since it was written in C, and I am not experienced C programmer, that was kinda challenge.

Related

Oracle Report 2.5 ordering rows and columns with Oracle 10g

I work in a company that was working on an Oracle 8i Database along with Oracle Developer 2000 (Forms 4.5 & Reports 2.5). Recently, We are trying to update the Database to 10g. Everything seems to be working smoothly, but in the report the order of the rows are not ordered correctly. Also, the columns keeps switching places each time a report is requested. They work perfectly fine on the old database. Forgot to mention that we upgraded using the dump tool. We dumped the entire database from the old to the new database.
Anyone have an idea how to solve this problem.
Note: We don't have the source of either the forms or the reports. We only have the compiled modules.
Any help would really be appreciated

How can I differentiate odoo databases according to odoo version?

In my system I have all those databases which falls under openerp version 7, 8 and 9. I want to differentiate them and take only those databases which falls under odoo version 8. I have checked in postgres files as well as in .openerp-server file. But I didn't get any thing which can help me. How to differentiate the databases?
AFAIK there is no obvious place in the database to look for that.
It would be possible to write a script that would inspect the data model looking for known differences between versions to detect the corresponding one.
But no such tool exists at the moment.
Personally, I solve this by always including the version number in the database name, such as dev-v8 or dev-v9.
Here is an answer..
You can execute following query :
SELECT * FROM ir_module_module WHERE name='base' AND latest_version like '9.%'

PostgreSql or SQL Server 2008 R2 should be use with .Net application using entity framework?

I have a database in PostgreSQL with millions of records and I have to develop a website that will use this database using Entity Framework (using dotnetConnect for PostgreSQL driver in case of PostgreSQL database).
Since SQL Server and .Net are both native to the Windows platform, should I migrate the database from PostgreSQL to SQL Server 2008 R2 for performance reasons?
I have read some blogs comparing the two RDBMS' but I am still confused about which system I should use.
There is no clear answer here, as its subjective, however this is what I would consider:
The overhead of learning a new DBMS and its tools.
The SQL dialects each RDBMS uses and if you are using that dialect currently.
The cost (monetary and time) required to migrate from PostgreSQL to another RDBMS
Do you or your client have an ongoing budget for the new RDBMS? If not, don't make the mistake of developing an application to use a RDBMS that will never see the light of day.
Personally if your current database is working well I wouldn't change. Why fix what isn't broke?
You need to find out if there is actually a problem, and if moving to SQL Server will fix it before doing any application changes.
Start by ignoring the fact you've got .net and using entity framework. Look at the queries that your web application is going to make, and try them directly against the database. See if its returning the information quick enough.
Only if, after you've tuned indexes etc. you can't make the answers come back in a time you're happy with should you decide the database is a problem. At that point it makes sense to try the same tests against a SQL Server database, but don't just assume SQL Server is going to be faster. You might find out that neither can do what you need, and you need to use faster disks or more memory etc.
The mechanism you're using to talk to a database (DotConnect or Microsoft drivers) will likely be a very minor performance consideration, considering the amount of information flowing (SQL statements in one direction and result sets in the other) is going to be almost identical for both technologies.

What options are there for migrating sqlite databases when upgrading OS apps?

Essentially I want to migrate sqlite schemata, and data accordingly, as I upgrade iPhone applications. I've heard of migrations frameworks becoming more popular in the Ruby, Java and .NET spaces, but is there something to help me in the iOS space?
CoreData isn't an option for me at the moment. (Please don't ask why, it just isn't.)
If a migrations library isn't available what approaches do you take?
In my past I usually kept a version info using a PRAGMA command in the database. Whenever my app starts up, I check which version the database is currently in, and call any needed update routines to alter the structure.
For most cases having a whole framework to do that is overkill; especially if you have less than 10 or 20 tables in the database.
Some pseudocode:
currentVersion = getCurrentDbVersion()
if currentVersion < 2 then
upgradeToVersion2();
end if
if currentVersion < 3 then
upgradeToVersion3();
end if
if currentVersion < 4 then
upgradeToVersion4();
end if
Here is some more information about that PRAGMA command:
http://www.sqlite.org/pragma.html#pragma_user_version
Hope that helps. :)

PostgreSQL vs Postgres Plus

Does anyone know what substantial differences there are between the regular PostgreSQL and Postgres Plus?
The database is the same, meaning that the SQL is fully compatible to any other PostgreSQL installation around (save for the GIS data formats).
The main difference is that there is a bunch of modules and tools bundled with Postgres Plus that you would have to collect and install separately and by yourself otherwise. Thus the main advantage is easy and speedy installation.
Most of the bundled stuff looks like it's freely available from other sources. That Postgres Studio application looks suspiciously close to pgAdmin III.
One important difference is the licence:
Postgres Plus is only free for "non-production" use.
you can find detailed purchasing options here:
http://www.enterprisedb.com/products/purchase.do
Postgres PLUS is proprietary, PostgreSQL is Open source under permissive license (and that's why Postgres PLUS is proprietary).
Postgres PLUS has support for Oracle PL/SQL, while PostgreSQL does not, at least not officially.
Those are two most obvious differences.
I used 8.2 and when was the time to switch to 8.3 I tried PostGresPlus.
The Speed was a lot faster. LOT I mean queries that took 30 secs, takes now less than 2 seconds. I am not sure if it's 8.3 that is faster or the Enterprise Plus but I can tell you that I was impressed.
Other thing that I like is that I can debug proc stored. It cames with more tools.