Yes. It should be smooth sail. Please ensure to have good backups for the instance. During the migration all you have to do it Stop and Start the SQL Services.

You may find this post useful.

First of all it is not good that there is no static IP. Atleast there would be a static server name? You may use the server name in the Import/Export...

Did you try the code which I had posted earlier? If that did not work can you please check the value of Resume key in

HKLM\Software\Microsoft\Microsoft SQL Server\MSSQL.1\Setup

MSSQL.1 needs to...

Try to make use of TRY/BEGIN, CATCH in the trigger.

Also XACT_STATE can be used for rolling back.

Add an output file to the job step which should give you the exact output of the job. Also when the job is running forever, did you find any blockings?...

Hi Kemal,

Check if this post helps you.

Again, we see the WMI error "Error 80080005 occured executing request for EnumValues" everywhere.

Can you try if the below code as specified here helps?

%SYSTEMDRIVE%

CD %windir%\system32\wbem

Mofcomp.exe cimwin32.mof

Regsvr32 /s wbemupgd.dll

Regsvr32 /s wbemsvc.dll

wmiprvse...

You may choose your pick from the options available in Replication.

You can use the scripts mentioned in this[/url] article and set up a job which does server side trace.

Did the issue got resolved? Even I faced the same issue today and found that one SPID was blocking the Database Creation SPID. This resulted in the failure of DB...

Refer this article on MSDN

You can make use of the "Import/Export" wizard

Did you use sp_xp_cmdshell_proxy_account as explained here?

Also you may find this article useful.

Read the "Temporary Tables" section in this article.