at first I never done that before but in general for other applications' migration I do the safe approach by creating a new SQL 2008 on a different hardware (leaving the current SQL 2005 instance intact) and do database-attach upgrade. - backup and restore the DB on the new SQL instance - move the security settings (users credentials) - move sql agent jobs related to back-end DBs if exist (such as backup jobs ... ) - change the connection configuration for the application, to connect to the new SQL instance and test the application. to move security settings between SQL 2005 and SQL 2008: http://support.microsoft.com/kb/918992/ It's never too late in life ... to start living

To add to Amer's post, the supported method to move the SQL back-end for ILM is to do a reinstall or reactivation (miisactivate.exe) on top of the database and reuse it after putting it on the new server. Remember to export your encryption key set before making any changes. You use the .bin file when doing the reinstall or reactivation and that should keep you from having to re-enter your MA service account passwords and any other data encrypted in the database that you are re-using. Chris

hi, ILM 2007 is supported on SQL 2008...so what should we be aware of if we are running ILM & SQL 2005, and simply want to upgrade to SQL 2008, but leave ILM 2007 in place? regards

at first I never done that before but in general for other applications' migration I do the safe approach by creating a new SQL 2008 on a different hardware (leaving the current SQL 2005 instance intact) and do database-attach upgrade. - backup and restore the DB on the new SQL instance - move the security settings (users credentials) - move sql agent jobs related to back-end DBs if exist (such as backup jobs ... ) - change the connection configuration for the application, to connect to the new SQL instance and test the application. to move security settings between SQL 2005 and SQL 2008: http://support.microsoft.com/kb/918992/ It's never too late in life ... to start living