Each time I re-transfer my 2.1 database over to my testing machine, I run
the 2.5 update script from within Emerald Admin. After that, I have to run
a couple scripts that fix some database problems. One of them fixes the
problem that you mentioned; another fixex all of the balances; the last
changes some null values to 0.00. Before running it, you might want to do a
"select *" from each of the tables referenced just to see what you've got.
This puts all of the data back where it belongs. There are differences in
keys and/or constraints between the "old" tables and the "new" ones (before
running this script), but I don't know which one is supposed to be correct.
So far, I haven't run into any problems running the following:
delete from radatconfigs
go
insert into radatconfigs
(accounttype, radattributeid, radvendorid, radvendortype, data, value,
radcheck)
select accounttype, radattributeid, radvendorid, radvendortype, data,
value, radcheck
from radatconfigs_old
go
delete from radconfigs
go
insert into radconfigs
(AccountID, RadAttributeID, RadVendorID, RadVendorType, Data, Value,
RadCheck)
select AccountID, RadAttributeID, RadVendorID, RadVendorType, Data, Value,
RadCheck
from radconfigs_old
go
Josh