I would always do a fresh install and then restore the databases. If you do an in place upgrade there is always the chance that something could go wrong during...

Developer edition is a full version of SQL Server so it would be equivalent to Enterprise edition in live. You will need to be aware of this whilst testing as...

The best way to do this is to restore the user databases, generate scripts for the SQL Agent jobs and use sp_help_revlogin for the users and passwords. Don't try and...

Yes the transaction log backups will still run during a full backup and will give you a recovery point if the server crashes during the full backup. Obviously you would...

Try this:
alter database [ENR Access DB]
modify file (name='ENR Access DB_log',filename='F:\Database Logs\ENR Access DB_log.LDF')
go

Thanks

So you say that all other commands work, which alter statements work and which don't?

Thanks

Can you post the error you are getting?

Thanks

Yes that's right, there needs to be a full backup before the log can be backed up.

Thanks

I forgot to add that you can also right click on your database in SSMS --> Tasks --> Generate Scripts and script out all your logins.

Thanks

You can use sp_help_revlogin. Take a look at the following link for details:
https://support.microsoft.com/en-gb/help/918992/how-to-transfer-logins-and-passwords-between-instances-of-sql-server

Thanks

It's straightforward to apply a service pack but as Beatrix has said do it on a test environment first. It's very unlikely that a service pack will cause any problems...