2. Upgrade your existing InstantKB.NET 1.3 database---------------------------------------------------------Important: Before running the upgrade script please ensure you have a backup of your existing InstantKB.NET 1.3 database. Our upgrade script should execute successfully however if you have a network or power failure whilst executing this script it could potentially corrupt your database. We cannot be held responsible for any loss of data if you experience any problems during the update. We would strongly recommend you backup your existing InstantKB.NET 1.3 database first.---------------------------------------------------------Once you've successfully installed a fresh instance of InstantKB.NET 2.0 the next step is to migrate your existing InstantKB.NET 1.3 database to the latest InstantKB.NET 2.0 schema. To upgrade your existing InstantKB.NET 1.3 database you'll need to connect to your InstantKB.NET 1.3 database within SQL Server 2000 Enterprise Manager or SQL Server 2006 Management Studio. Once connected to your InstantKB.NET 1.3 database you should execute the "InstantKB20\DatabaseScripts\UpgradeScripts\1.3_to_2.0.sql" file as shown below.You can also find the 1.3_to_2.0.sql script attached at the bottom of this article.Ensure your InstantKB.NET 1.3 database is selected as shown above and click the "Execute" button to update your database....The warning messages within the results pane are perfectly normal and can safely be ignored. Once you've executed the upgrade script if you refresh your existing InstantKB.NET 1.3 database you should see a number of new database tables as shown below...That's it. Your database is now updated. The next step is to update the connection string used within your fresh InstantKB.NET 2.0 installation to point towards your updated 1.3 database.3. Update the InstantKB.NET 2.0 connection stringNow your InstantKb.NET 1.3 database has been updated to the 2.0 schema you can update the database connection string within the InstantKB.NET 2.0 web.config file to point towards your updated database.To update the connection string open the "InstantKB20\web.config" file within NotePad or similar ASCII editor. Locate the InstantASP_ConnectionString setting. The default setting is shown below...<add key="InstantASP_ConnectionString" value="server=localhost;trusted_connection=true;database=InstantKB20;"/>You should update this connection string to point towards your updated InstantKB.NET 1.3 database. For more information on connection string please see "InstantKB.NET connection string & key application settings".Note: If you connect to SQL using SQL Server authentication you'll need to update the connection string to include the username and password for the SQL Server user account you used when connecting to run the update script. You can modify the connection string to use a SQL Server username & password as shown below...add key="InstantASP_ConnectionString" value="SERVER=localhost;UID=username;PWD=password;DATABASE=InstantKB20;"/>4. Copy over the "Attachments" folder from InstantKB.NET 1.3 to 2.0To ensure all your attachments and image uploads from InstantKB.NET 1.3 continue to work correctly within InstantKB.NET 2.0 simply copy the "Attachments" folder & all it's contents from the root of your existing InstantKB.NET 1.3 installation into the root of your fresh InstantKB.NET 2.0 installation. This is shown below...That's It!The update should now be complete. You should now attempt to connect to your fresh InstantKB.NET 2.0 installation via a web browser. If everything was successful you should see a skelaton InstantKB.NET 2.0 installation with all your exiting InstantKB.NET 1.3 articles, categories, users etc. You can login using your existing email address & password. To access the administrator & staff control panels you'll need to login using your existing InstantKB.NET 1.3 login credentials.For further information on to help you get started with InstantKB.NET 2.0 please see "Getting started with InstantKB.NET 2.0" or "Testing your InstantKB.NET 2.0 installation". If you have any questions with regard to upgrading please hesitate to leave a comment below, post within our community forums, open a support ticket or contact us.