David Burton started series of articles about migration from MS SQL to Firebird.
There is also "MS SQL to Firebird Migration Guide" at firebirdsql.org documentation page.
Wednesday, September 20, 2006
Monday, September 18, 2006
Names identity
I found that Google Alerts is sometimes useless. During 3 weeks I tried to monitor news & web about Delphi, Firebird and Interbase, and the only news I've got were about Delphi Corp. (auto-parts company), Firebird tale and Stravinsky's music, and some protocol named "interbase".
This is interesting at least because those keywords in their wanted meaning (IDE, RDBMS) can easily be found by Google search right on first results page. If you have some positive experience about Google Alert, please tell me :-)
p.s. Oh, right now got the first real alert - http://www.irishdev.com/EventDetails.aspx?id=567
This is interesting at least because those keywords in their wanted meaning (IDE, RDBMS) can easily be found by Google search right on first results page. If you have some positive experience about Google Alert, please tell me :-)
p.s. Oh, right now got the first real alert - http://www.irishdev.com/EventDetails.aspx?id=567
Friday, September 01, 2006
Overloaded by transactions
Do you remember old InterBase 5.6 bug when maximum number of transactions in database is depending on page size ?
Strange, but early InterBase 6.0 versions have the same, sure. Yesterday we got database with the same sympthoms, but this is ODS 10.0 database with dialect 3, created with InterBase 6.0. Let's look at statistics from IBAnalyst:
Sorry about numbers format, if it is hard to read - there are 534 million transactions in database. Since January 2005. And, if this database was put into production right after creation (or restore), there are 880 thousands transactions each day.
Why I was so impressed? This works on WinXP.
While database exists 607 days (more than 1.5 years), transaction inventory page became very big - 130 megabytes (Next transaction div 4 bytes). Database size is 160 megabytes, with the only 13 megabytes data in it.
Strange, but early InterBase 6.0 versions have the same, sure. Yesterday we got database with the same sympthoms, but this is ODS 10.0 database with dialect 3, created with InterBase 6.0. Let's look at statistics from IBAnalyst:
Sorry about numbers format, if it is hard to read - there are 534 million transactions in database. Since January 2005. And, if this database was put into production right after creation (or restore), there are 880 thousands transactions each day.
Why I was so impressed? This works on WinXP.
While database exists 607 days (more than 1.5 years), transaction inventory page became very big - 130 megabytes (Next transaction div 4 bytes). Database size is 160 megabytes, with the only 13 megabytes data in it.
Friday, August 18, 2006
New DataDirect ODBC driver
Borland released new DataDirect ODBC driver for InterBase customers (thanks Craig for the info). Also separate ADO .Net driver for InterBase (BDP 2.5.0) available.
Both drivers are free for InterBase users, but there is another OLE DB driver that is very useful, especially for Visual Studio - IBProvider. It uses all existing and possible OLE DB features, like many transactions per one connect and others, and can provide nearly the same special InterBase functionality accessible in native components like FIBPlus and IBX.
Both drivers are free for InterBase users, but there is another OLE DB driver that is very useful, especially for Visual Studio - IBProvider. It uses all existing and possible OLE DB features, like many transactions per one connect and others, and can provide nearly the same special InterBase functionality accessible in native components like FIBPlus and IBX.
Repair issue
Yesterday we got broken database from some popular (in tight range) commercial system. It is built on InterBase 4.1, and still being sold by developers for wide range of shops. But, sometimes in these shops server power failure happens. In this case damage was increased by old InterBase 4 bug when data in header page is being shiffled. Hopefully, information was not broken, just mixed.
Repair process was a bit tricky, and took about 3 hours. First, database needed to be repaired to work with Firebird 1.5. Second, it was repaired again. And then, it was moved back to InterBase 4 format.
Everything went fine, except 7 records in one table were completely lost. Anyway, it was a small data loss, so database now works fine.
Repair process was a bit tricky, and took about 3 hours. First, database needed to be repaired to work with Firebird 1.5. Second, it was repaired again. And then, it was moved back to InterBase 4 format.
Everything went fine, except 7 records in one table were completely lost. Anyway, it was a small data loss, so database now works fine.
Unbroken database
In May our support got a customer alert that his InterBase 7.5 database is broken right after restore. We found that really, even after only metadata restore gfix reports about broken indices on rdb$dependencies and other system tables. Borland responded very quickly, telling that this is gfix error - it does not understand correctly new index structure introduced in ODS 11.2 databases. Hopefuly, gfix does not "fix" these "errors", so database stays correct. This issue have number 240075 in internal Borland's bugtracking system, and will be fixed only in next InterBase version.
Stay tuned.
Stay tuned.
Subscribe to:
Posts (Atom)
