There are a few things you will need to know if you are wanting to get Community Server 2.1 up and running on GoDaddy.
The second of these is good for the info on how to create the initial database, get the Community Server files FTP'd up there and repointing the database.
For the database setup itself you should use the SQL scripts that came in the Web Install.
The biggest problem as it turns out is that GoDaddy's "Query Analyzer" (the tool they use to perform DDL operations on the database) barfs on any remotely complex SQL, including the CS 2.1 SQL scripts.
I wasn't going to let that slow me down, so I wrote a mydb.aspx page that let me set up the database myself using the same .sql files.
To use this tool, first make sure you have all of supaleets FTP and database re-pointing instructions done (by repointing I mean ensure that your web.config has all the database connection strings pointing to the database that GoDaddy made for you).
Before you can run the Community Server creation script you will need to run the aspnet_regsqlOn tool to build the ASP.NET 2.0 SQL setup script. To do this, go to a command prompt and type:
CD /D %systemroot%\Microsoft.Net\Framework\v2.0.50727
ASPNET_REGSQL -A all -d db_##### -sqlexportonly aspnet.sql
The ##### should be replaced with the number GoDaddy gave you when the database was created. You will also see this number of the connection string from following supaleet's instructions.
Once you have this, FTP the mydb.aspx script together with the aspnet.sql script to the root of your Community Server web site at GoDaddy.
You should also upload the cs_2.1_createfulldatabase.sql file to the same location. I renamed mine to create.sql to make it easy to remember later.
Next you should rename the web.config and global.asax files at your GoDaddy site. I put a "_" at the end of mine. You will want to create a copy of the web.config on your local PC and edit it to not include any of the httpmodule or httphandler information, nor any of the setup for profiles, roles or membership. Upload this modified web.config into your FTP site. We do this to prevent ASP.NET from trying to use any Community Server or ASP.NET database features before we have the new databases set up.
You're now ready to create the database. In the browser run the following:
http://www.yoursite.com/mydb.aspx?sql=aspnet
You should see a bunch of records saying "# records changed".
If all goes well, run the following:
http://www.yoursite.com/mydb.aspx?sql=create.sql
(remember this is the CS 2.1 createfulldatabase script which I renamed to make it easier to remember at this stage).
Again, it should all work well.
Now to clean up. Delete the mydb.aspx, the two .sql files and the reduced web.config from your server via your FTP client. Once that is done, rename the global.asax_ and web.config_ files back to their original names without the trailing underscore.
The last step is to exec the stored procedure to set up your CS site, per the instructions in the web install, which you can do via GoDaddy's Query Analyzer.
Best of luck!