RE: [firebird-support] Migration Guide for Firebird 1.5.3 to 2.5.4
Hello Mike, I remember that i read this : http://www.firebirdsql.org/file/community/ppts/fbcon11/Firebird_Migration_75Gb_IBSurgeon.pdf and this was also interesting if you have to change from dialect 1 to 3 : http://www.ic.unicamp.br/~celio/livrobd/firebird/GetStart.pdf at page 37 (the interbase 6 getstart.pdf documentation). You can also have a look at https://code.google.com/p/fbclone/ which is an interesting tool to migrate from firebird 1.5 to 2.5. Have a good day ! Marianne De : firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com] Envoyé : mercredi 22 juillet 2015 13:43 À : firebird-support@yahoogroups.com Objet : [firebird-support] Migration Guide for Firebird 1.5.3 to 2.5.4 Greetings All, I'm needing to get underway way with preparing my Firebird 1.5.3 database for migration to 2.5.4. Is there any documentation available that discusses what all needs to be looked at before backing up the database in 1.5.3 and restoring to 2.5.4? Possibly a migration guide? Thanks, Mike
Re: [firebird-support] Chararacter set NONE to ISO8859_1
Stefan, thanks for your answer. I think that passing through a temporary field by filling it with a cast to octets of the original field has the same effect that assuming that the original field had been filled with ISO8859_1 character set. See my answer to Raffaele. Regards, Aldo El 22/07/15 a las 15:09, Stefan Heymann li...@stefanheymann.de [firebird-support] escibió: > I wonder what is wrong with simply invoking "ALTER TABLE X ALTER > COLUMN Y TYPE CHAR(N) CHARACTER SET ISO8859_1" This will only change the metadata of that field. It will not check if the data really is ISO8859_1. When *you* are sure about that, it shouldn't be a problem. Regards Stefan
Re: Rif: [firebird-support] Chararacter set NONE to ISO8859_1
Raffaele, thanks for your answer. The question is what prevents data loss in the first procedure ? Suppose the filed in question is FIRST_NAME VARCHAR(60) CHARACTER SET NONE so lets create a temporary field TMP_NAME VARCHAR(60) CHARACATER SET ISO8859_1 and then lets fill it UPDATE TABLE1 SET TMP_NAME = CAST(FIRST_NAME AS VARCHAR(60) CHARACTER SET OCTETS) Whichever character (from 0 to 255) were in FIRST_NAME would be blindly copied to TMP_NAME. This has the same effect as assuming that the characters in FIRST_NAME where loaded as ISO8859_1, so simply changing FIRST_NAME type from NONE to ISO8859_1 would be equivalent. Aldo El 22/07/15 a las 04:57, 'Raffaele Confalone' r.confal...@libero.it [firebird-support] escibió: The first procedure provides you safe from data loss. you can directly execute the change of the charset after doing a complete backup of the database. ---Messaggio originale--- Da: Aldo Caruso aldo.car...@argencasas.com [firebird-support] Data: 21/07/2015 18.38.39 A: firebird-support@yahoogroups.com Oggetto: [firebird-support] Chararacter set NONE to ISO8859_1 Hi, I have some VARCHAR fields whose character set were incorrectly defined as NONE. I would like to use ISO8859_1 instead. I read on "The Firebird Book" that in order to do so you must add a new temporary field, with the right character set, fill it with the data from the original field ( using OCTECT as an intermediat chararacter set ) and finally drop and recreate the original field with the right character set, filling it with the data that was stored in the temporary field. The process ends up dropping the temporary field. I wonder what is wrong with simply invoking "ALTER TABLE X ALTER COLUMN Y TYPE CHAR(N) CHARACTER SET ISO8859_1" Thanks in advance for any help. Aldo Caruso ++ Visit http://www.firebirdsql.org and click the Documentation item on the main (top) menu. Try FAQ and other links from the left-side menu there. Also search the knowledgebases at http://www.ibphoenix com/resources/documents/ ++ Yahoo Groups Links - Nessun virus nel messaggio. Controllato da AVG - www.avg.com Versione: 2015.0.6081 / Database dei virus: 4392/10282 - Data di rilascio: 21/07/2015 [Non-text portions of this message have been removed]
Re: [firebird-support] Chararacter set NONE to ISO8859_1
> I wonder what is wrong with simply invoking "ALTER TABLE X ALTER > COLUMN Y TYPE CHAR(N) CHARACTER SET ISO8859_1" This will only change the metadata of that field. It will not check if the data really is ISO8859_1. When *you* are sure about that, it shouldn't be a problem. Regards Stefan
[firebird-support] Migration Guide for Firebird 1.5.3 to 2.5.4
Greetings All, I'm needing to get underway way with preparing my Firebird 1.5.3 database for migration to 2.5.4. Is there any documentation available that discusses what all needs to be looked at before backing up the database in 1.5.3 and restoring to 2.5.4? Possibly a migration guide? Thanks, Mike
Rif: [firebird-support] Re: Firebird 1.5.3 on Windows 2012 R2 Server
Is possible to run the query manually from the command prompt dos using ISQL ---Messaggio originale--- Da: Aage Johansen aagjo...@online.no [firebird-support] Data: 21/07/2015 22.45.36 A: firebird-support@yahoogroups.com Oggetto: [firebird-support] Re: Firebird 1.5.3 on Windows 2012 R2 Server Mike wrote: >Can anyone tell me if Firebird 1.5.3 will run on Windows 2012 R2 Server? The silence might mean that you are the first (on this list) wanting to run the ancient 1.5.3 on a Windows2012R2 server. Try it, and report back. -- Aage J. [Non-text portions of this message have been removed]
Rif: [firebird-support] Re: Firebird 1.5.3 on Windows 2012 R2 Server
you run the query manually from the command prompt dos using ISQL ---Messaggio originale--- Da: Aage Johansen aagjo...@online.no [firebird-support] Data: 21/07/2015 22.45.36 A: firebird-support@yahoogroups.com Oggetto: [firebird-support] Re: Firebird 1.5.3 on Windows 2012 R2 Server Mike wrote: >Can anyone tell me if Firebird 1.5.3 will run on Windows 2012 R2 Server? The silence might mean that you are the first (on this list) wanting to run the ancient 1.5.3 on a Windows2012R2 server. Try it, and report back. -- Aage J. [Non-text portions of this message have been removed]
Rif: [firebird-support] Chararacter set NONE to ISO8859_1
The first procedure provides you safe from data loss. you can directly execute the change of the charset after doing a complete backup of the database. ---Messaggio originale--- Da: Aldo Caruso aldo.car...@argencasas.com [firebird-support] Data: 21/07/2015 18.38.39 A: firebird-support@yahoogroups.com Oggetto: [firebird-support] Chararacter set NONE to ISO8859_1 Hi, I have some VARCHAR fields whose character set were incorrectly defined as NONE. I would like to use ISO8859_1 instead. I read on "The Firebird Book" that in order to do so you must add a new temporary field, with the right character set, fill it with the data from the original field ( using OCTECT as an intermediat chararacter set ) and finally drop and recreate the original field with the right character set, filling it with the data that was stored in the temporary field. The process ends up dropping the temporary field. I wonder what is wrong with simply invoking "ALTER TABLE X ALTER COLUMN Y TYPE CHAR(N) CHARACTER SET ISO8859_1" Thanks in advance for any help. Aldo Caruso ++ Visit http://www.firebirdsql.org and click the Documentation item on the main (top) menu. Try FAQ and other links from the left-side menu there. Also search the knowledgebases at http://www.ibphoenix com/resources/documents/ ++ Yahoo Groups Links - Nessun virus nel messaggio. Controllato da AVG - www.avg.com Versione: 2015.0.6081 / Database dei virus: 4392/10282 - Data di rilascio: 21/07/2015 [Non-text portions of this message have been removed]
