OK, let's get this resolved without all the yelling (no CAPS LOCK please), and the down votes.... :) ...
You are basically on the right track, you just need to pull the trigger. Yes, you need to
1) Backup your existing database
- options:
a) use a tool like SSMS (SQL server management studio)
However, if you have your SQL Server DB hosted, then it's likely a FULL version and not EXPRESS. I do not think you can use SSMS Express to manage it.
b) use the host's control panel to backup the database. Most host control panels have a Database > Maintenance > Backup feature, that will create the backup (usually in .zip format), and save it on the host drive. You can further FTP a copy to your local PC.
c) ask the host to do the backup for you.
If you are really concerned about loss of uptime, or loss of data, then it would be best to
set up a new database on the host (either yourself, or ask them for assist). Setting up a new DB is my recommendation.
Then "restore" the backup there (again, either yourself or ask host). Then, later, when you get this new copy upgraded, all you need to do is change the db connection string in the web site \AppData\Settings.txt
2) Upgrade the database.
Yes, you must run every upgrade.sql in sequence - e.g. 2.30-2.40, 2.40-2.50, 2.50-2.60, etc.
Yes, you need a tool like SSMS. But, as per above, the free SQLEXPRESS may not work against host db.
Use this instead
http://www.albahari.com/queryexpress.aspxJust download it to your desktop. No extract is required. (if using Win 7, then after download, right-click the exe file, and click Unblock button)
a) run QueryExpress
b) fill out connect dialog. Use SQL Server authentication.
c) when query window opens, type
USE mydbname
(where mydbname is your database name :)
e) click the green arrow (run) button, or press F5
f) on menu click File / Open, and open one of the upgrade.sql files in the upgradescripts subfolder
(verify the your db name is selected in the dropdown on the left nav pane)
g) click the green arrow (run) button, or press F5
h) repeat f & g for each upgrade.sql
3) Backup your existing web site
- options
a) use FTP and make local copy
b) use host control panel File Manager, and make copy on host.
c) ask host to back it up.
Similar to above, and my recommendation, is to instead
create a new web site to run your tests first. Most hosting plans allow for creating more than one web site even for basic plan. The host control panel can do this, or ask them:
a) in host file manager or FTP, create a new folder in your host root - e.g.
test.mydomain.com
b) in host web manager, create a subdomain - e.g.
test.mydomain.com
point the subdomain to your new folder
c) Upload the new no source version of nopC to the new folder
d) Copy the \AppData\Settings.txt from your old web site (overwrite the one in test folder)
e) Edit the \AppData\Settings.txt to point to your new DB (and new user / pwd if needed, though you should have granted prev user access to new db)
You can typically edit files in the host control panel. Or FTP the file, modify local, and upload. Or, get FileZilla FTP program, and you can edit files, and it handles the download/upload for you.
f) Copy the \AppData\InstalledPlugins.txt from your old web site (overwrite the one in test folder)
4) Test
a) Use a browser to navigate to your new web site - e.g. test.mydomain.com
5) Make it live
a) Use FTP program, or host file manager
i. rename your live folder to backup.mydomain.com
ii. rename your test folder to whatver the name of your live folder was
6) Smile :)