I need to move my database from SQL Server 2008R2 to SQL Server 2008,  because I can not make a backup and restore it on the new server due to downgrade version compatibility problems.

I decided to use the sql server export tool,  the export process generated no errors

Then create a user with the same name and credentials that  I had in the old server, so the  only  change i have to do in the web file was change server IP  address.

My problem is that when I browse to the site, instead of showing me my site, I get the window to start a new installation ... the instalation whizard.

Why is that...if  the DNN database was migrated?

So  I reversed the ip address in the web.config file and the site in OK again.

Dear  SUNIL KUMAR

 Thanks for your suggestion ...
Indeed, I think generating the script  is better that the export procedure, because  ensures that all objects in the database as well as users and their permissions are created in the destination server, not only the tables and data.
But even after generating and running the script, the problem persists ...
After modify  the web.config  in order to point to the new server ´s DNN database, and try to browse  my site… there again the installation’s Wizard  appears just  like a new installation is about to be done…
 I wonder ... What determines that installation’s Wizard is needed?
Maybe understanding this I would be able to solve it!!
What could cause DNN application failed to identify that a populate database already exists in environment? 
Any other recommendation?

after reviewing the connection to the database, I changed the IP address and use  the  FQDN  Address, and  DNN site is working ..

thanks a lot for your help!!!