Setup Kentico 8.1 website locally at the development server

Are you trying to bring database copy from production to your local environment? If this is your case, without knowing more details, I can suggest only making backup of production database and restoring it at the local server.

If it is not your case, please provide more details on your issue.

You will need to have at the very least sql server or sql server express installed on the local machine. Then connect to the production server database via SQL Server Management Studio, and create a backup of the production database. .bak file (which may also be zipped). Then copy it to your development server and connect to the SQL Server instance by using SQL Server Management Studio again and then restore the database, by selecting the database that you copied. Open up Kentico and adjust the connection in the web.config.

This is assuming you have a basic install of the system and you aren't using replication, or azure, etc. etc.

I have followed the following steps.

1) I have copied production database and restored it locally. 2) Made a source code copy from production and created IIS application locally pointed to the restored database by Updating ConnectionString in the web.config. 3) It show me screen to select "Database Instance" and run some script and then give error.

This is the screen what i get. http://www.megafileupload.com/4Vuf/KenticoDatabase.png

Unfortunately I cannot see your image it wants me to sign up.

If you have visual studio installed, open up the website in visual studio, then modify the connection string and press Ctrl F5 and it should start up after a bit.

Hi Charles, Can you please try this link.

      [Snapshot](http://1drv.ms/1TgoD4n)

Your Kentico installation is not seeing the database. I would assume either it either named pipes or tcp not configured or a bad user name and password.

This is due to the SQL user you have doesn't have the correct permission to that database. Normally, the SQL user account for the CMS DB should be the DBO of that DB and also should have read and write permission to that DB as well.

i am using High Privileged account "sa" but still the same message.