SQL Migration Questions
Happy Boxing Day!
DF 24.0, MSSQL 2022 Dev. edition Migrating from a working embedded DB that was originally in 19.0.
In converting a bunch of tables, I was bitten by the "gap in index #" issue that Ian posted about recently so a half dozen tables did not convert. However, even though I did not check the "Keep new table even if some records could not be copied" checkbox, it created it - but empty - IOW no records were copied. Seems to me it should not have created it - or at least whacked it after it couldn't copy anything.
Next - how should Alias tables be handled? I'm talking old style with a filelist entry & Master/Slave code in the DDs. If I convert both master & alias, since the alias has a higher filelist #, the FD gets created for the alias & overwrites the master FD. What I've been doing is to not convert them, but in this case that means carefully checking a list of 100 tables & unchecking the alias tables & then when the conversion is done, using DBBuilder to edit the filelist entry to include MSSQLDRV: for all the alias tables. Is there a better way?
Thanks!
Garret
My brain just logged me out due to inactivity and now I can't remember my password.