DB Migration 1.02d -> 1.00L -> 00.99.62T: Success Story

1st of all - if you dont know how to use SQL Enterprise Manager then RTFM.
2nd - this guide is applicable for any other version and any direction.

you have to restore DB's to these names:
New DB: MuOnline
Old DB: MuOnline_old
Tables to rename in MuOnline_old: MEMB_INFO, AccountCharacter, Character, MEMB_STAT, warehouse, VI_CURR_INFO.
Rename they to MEMB_INFO2, AccountCharacter2, Character2, MEMB_STAT2, warehouse2, VI_CURR_INFO2.
Use the following menu in Enterprise Manager when you open tables in MuOnline_old: All tasks -> Export data.
Press Next twice, select New DB - MuOnline, Next twice, Select tables "MEMB_INFO, AccountCharacter, Character, MEMB_STAT, warehouse, VI_CURR_INFO", Next twice, Finish.
When your old tables has been copied into new DB you have to execute queries below.

Below is the main tables which we have to use for migration from 1.02d -> 1.00L
For migration to 0.99.62T you dont need to use string with VI_CURR_INFO, coz they arent exist.

Code:

---

Insert Into MEMB_INFO ( memb___id, memb__pwd, memb_name, sno__numb, post_code, addr_info, addr_deta, tel__numb, phon_numb, mail_addr, fpas_ques, fpas_answ, job__code, appl_days, modi_days, out__days, true_days, mail_chek, bloc_code, ctl1_code) Select MEMB_INFO2.memb___id, MEMB_INFO2.memb__pwd, MEMB_INFO2.memb_name, MEMB_INFO2.sno__numb, MEMB_INFO2.post_code, MEMB_INFO2.addr_info, MEMB_INFO2.addr_deta, MEMB_INFO2.tel__numb, MEMB_INFO2.phon_numb, MEMB_INFO2.mail_addr, MEMB_INFO2.fpas_ques, MEMB_INFO2.fpas_answ, MEMB_INFO2.job__code, MEMB_INFO2.appl_days, MEMB_INFO2.modi_days, MEMB_INFO2.out__days, MEMB_INFO2.true_days, MEMB_INFO2.mail_chek, MEMB_INFO2.bloc_code, MEMB_INFO2.ctl1_code from MEMB_INFO2
Insert Into AccountCharacter (Id, GameID1, GameID2, GameID3, GameID4, GameID5, GameIDC) Select AccountCharacter2.Id, AccountCharacter2.GameID1, AccountCharacter2.GameID2, AccountCharacter2.GameID3, AccountCharacter2.GameID4, AccountCharacter2.GameID5, AccountCharacter2.GameIDC from AccountCharacter2
Insert Into Character (AccountID, Name, cLevel, LevelUpPoint, Class, Experience, Strength, Dexterity,Vitality, Energy, Inventory, MagicList, Money, Life, MaxLife, Mana, MaxMana, MapNumber, MapPosX, MapPosY, MapDir, PkCount, PkLevel, PkTime, MDate, LDate, CtlCode, DbVersion, Quest) Select Character2.AccountID, Character2.Name, Character2.cLevel, Character2.LevelUpPoint, Character2.Class, Character2.Experience, Character2.Strength, Character2.Dexterity,Character2.Vitality, Character2.Energy, Character2.Inventory, Character2.MagicList, Character2.Money, Character2.Life, Character2.MaxLife, Character2.Mana, Character2.MaxMana, Character2.MapNumber, Character2.MapPosX, Character2.MapPosY, Character2.MapDir, Character2.PkCount, Character2.PkLevel, Character2.PkTime, Character2.MDate, Character2.LDate, Character2.CtlCode, Character2.DbVersion, Character2.Quest from Character2
Insert Into MEMB_STAT ( memb___id, ConnectStat, ServerName, IP, ConnectTM, DisConnectTM) Select MEMB_STAT2.memb___id, MEMB_STAT2.ConnectStat, MEMB_STAT2.ServerName, MEMB_STAT2.IP, MEMB_STAT2.ConnectTM, MEMB_STAT2.DisConnectTM from MEMB_STAT2
Insert Into warehouse ( AccountID, Items, Money, EndUseDate, DbVersion, pw) Select warehouse2.AccountID, warehouse2.Items, warehouse2.Money, warehouse2.EndUseDate, warehouse2.DbVersion, warehouse2.pw from warehouse2
Insert Into VI_CURR_INFO ( ends_days, chek_code, used_time, memb___id, memb_name, memb_guid, sno__numb, Bill_Section, Bill_Value, Bill_Hour,Surplus_Point, Surplus_Minute, Increase_Days) Select VI_CURR_INFO2.ends_days, VI_CURR_INFO2.chek_code, VI_CURR_INFO2.used_time, VI_CURR_INFO2.memb___id, VI_CURR_INFO2.memb_name, VI_CURR_INFO2.memb_guid, VI_CURR_INFO2.sno__numb, VI_CURR_INFO2.Bill_Section, VI_CURR_INFO2.Bill_Value, VI_CURR_INFO2.Bill_Hour, VI_CURR_INFO2.Surplus_Point, VI_CURR_INFO2.Surplus_Minute, VI_CURR_INFO2.Increase_Days from VI_CURR_INFO2

---

Feel free to ask any questions.

just right about time.

Good,
!!! thx.
Just waiting to 1.00 support the new sets and maps

For migration accounts 1.02D to 0.99.62T requires to convert in md5 (memb__pwd). Knows is code sql?
Thx.
1.02d = memb__pwd (nvarchar) length 10
99.62 = memb__pwd (varbinary) length 16

Google Translator. xD

what about 1.02d to 1.02i? can you also give help?

why didnt you just add the new items to 99.6x and transfer from 1.02d -> 00.99.62T

then it would be 00.99.62T + 1.02d.... just makes more sence to me...

what about 1.02d to 1.02i? can you help?

i have this message:

Server: Msg 260, Level 16, State 1, Lines 1 implicit Conversion not authorized by the type of data nvarchar in varbinary type, banks ' MuOnline.dbo. MEMB_INFO ', column ' memb __ pwd '. Use the function(office) CONVERT to execute this request.


Please help me ... :(

i have this message:

Server: Msg 260, Level 16, State 1, Lines 1 implicit Conversion not authorized by the type of data nvarchar in varbinary type, banks ' MuOnline.dbo. MEMB_INFO ', column ' memb __ pwd '. Use the function(office) CONVERT to execute this request.

please help me ... :(

i have this message:

Server: Msg 260, Level 16, State 1, Lines 1 implicit Conversion not authorized by the type of data nvarchar in varbinary type, banks ' MuOnline.dbo. MEMB_INFO ', column ' memb __ pwd '. Use the function(office) CONVERT to execute this request.

plz help me

ohh yes this guides is good

now i have fenrir :) ?

:batman: Cool men tks

ill try that later, as soon as i find a good launcher for my server >.<

You are in Error: u say to change names of MuOnline_old but it is not true! Think man if u insert ''Character2'' into ur MuOnline db tehre is no point...
The names have to be changed in db MuOnline(character to character2..etc) And then Export data from MuOnline_Old
And when u are doing that make shure ur Easy PHP not runing
Guilde 100% works:) with my ''fix''

is it possible migration from 0.99.6xt to 1.02d?

can keep all the items of the characters if i migrate from 1.02d to 0.99.62t

Quote:

---

Originally Posted by archmage2

can keep all the items of the characters if i migrate from 1.02d to 0.99.62t

---

except last sets and weapons =)

For migration accounts 1.02D to 0.99.62T requires to convert in md5 (memb__pwd). Knows is code sql?
Thx.
1.02d = memb__pwd (nvarchar) length 10
99.62 = memb__pwd (varbinary) length 16

plzzz Knows is code sql?:construct

how to restore from 2 DB to 6 DB ??

Thanks

Put this en query analyzer
UPDATE memb_info2
SET memb_info2.memb__pwd2 = (SELECT dbo.fn_md5(memb__pwd))

how about md5? i cant transfer passwords it tells me to convert them
but no idea how to do that

how about md5?

how about md5? how change varchar to binary?
do u know the query?

okay i need to go from 99 to 1.02 this is from 1.02 to 99 as i read. is there a way to migrate forward. I need to go to 1.02f from 99

I see your guide is to go from 1.02 to 00 is there a way to go from 99 to 1.02f?

does this worke for 97J => 1.0L if yes please explain a litle about the renameing tables coz i dont really understand them

and how to transfer 97 items to 1.02n? from warehouse and invetory with no problems? any solution for that?

Quote:

---

Originally Posted by Tribalmu

Put this en query analyzer
UPDATE memb_info2
SET memb_info2.memb__pwd2 = (SELECT dbo.fn_md5(memb__pwd))

---

it's doesn't work Tribalmu, can you check it again plz. i really need it, thx so much

Really useful guide, i used it to migrate from LucianoAibar's 0.99.6X to 1.00.16 ;)
now i have a problem with md5, cause newer DBs dont use md5, any ideas for this?

Good,
!!! thx.
Just waiting to 1.03support the new sets and maps

DB migration is easy, nowadays you don't even have to replace your DB.

can i use the same codes to transfer acc,char,items,guild? from 99.88T (1.02n client) to 1.00.16 ( 1.04h) ?


and what command do i need to use for guilds transfer?

Can You Giv Me A Clint 1.0l