When you move the code to your ISP / host, things may become a little more difficult.
First of all, your ISP needs to support SQL Server, preferably SQL Server 2005. Many hosts do, these days, but you'll have to pay extra (often, not always).
Once you know your ISP (and your account) supports SQL Server, you usually get an account for the SQL Server Enterprise Manager (2000) or SQL Server Management Studio (2005). From there, you can create a new database and manage users, rights and so on.
Once your database is OK, you need to modify your app's web.config to work with the new database. Incidentally, I wrote an extensive article about it some time ago that you can find here: http://imar.spaanjaars.com/QuickDocId.aspx?quickdoc=395
It covers a lot of ground and introduces many concepts that might be new for you, so don't give up when you fail the first time while trying... ;)
Or better yet: if you have a support contract with your host, let them do the dirty work....
Please note that all applications were written against SQL Server 2005. So, you won't be able to attach these database to an instance of SQL Server 2000. In some cases, you may be able to script the contents of the database and create a new 2000 database from that. In other scenarios, like the Customer Support Site, SQL Server 2005 specific features are used so you can't upgrade. In those cases, you need to find a host that has SQL Server 2005.
Hope this helps, and didn't confuse you even more.... ;)
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results
and Beginning Dreamweaver MX / MX 2004
While typing this post, I was listening to: Love Is A Stranger
(Track 1 from the album: Greatest Hits
) What's This?